From nobody Mon Oct 25 07:35:01 2021 X-Original-To: emulation@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 710AE181E993 for ; Mon, 25 Oct 2021 07:35:11 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hd6Db27pKz3tM1 for ; Mon, 25 Oct 2021 07:35:11 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail (mail [192.168.254.3]) by mail.madpilot.net (Postfix) with ESMTP id 4Hd6DS30q3z6gCx; Mon, 25 Oct 2021 09:35:04 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :from:from:references:content-language:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1635147302; x= 1636961703; bh=oJmUMl8VvMlxJao+TOlopaOoUrhuiCSWKcj6ST39kN0=; b=A +Tg822zjkLWCDQKGkHQWL5ZnFtA9ErzSEdWGADi9Sep9hxvu/3RO2KRBaNu97DbK F5gCe1JXP3uX5Z3fWC9aEn+tRyIHQAF6mz4GY16JzbNcRosRat+6uPNyM70K6xg6 VF49PzGGutupS8DUu/YV0ZXWS/MqarBR6XJ+lBigbej4ytXoMsVtuGBXawjHTBjz Gf8KaX7M/KZOpYfLl6eNYCaaYtU+gjKMbCSybCBmjQUaUCdqINJuTTh6Gi2xM27k j6nCUk1GU/7FylzbHYP4OPmQnlU48e/B87kVO/r3ZFbH0BMf1uXwhAJnQCnPVJqm QgxoXL2WpgQf53bHVijGA== Received: from mail.madpilot.net ([192.168.254.3]) by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10026) with ESMTP id iZJrvbH1Wy4L; Mon, 25 Oct 2021 09:35:02 +0200 (CEST) Message-ID: <584ba151-97fa-5507-59c8-08c081798ef8@madpilot.net> Date: Mon, 25 Oct 2021 09:35:01 +0200 Subject: Re: Kernel error reports from VirtualBax Content-Language: en-US To: Kevin Oberman , "freebsd-emulation@freebsd.org" References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Hd6Db27pKz3tM1 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] Reply-To: mad@madpilot.net From: Guido Falsi via emulation X-Original-From: Guido Falsi X-ThisMailContainsUnwantedMimeParts: N List-Id: Development of Emulators of other operating systems List-Archive: https://lists.freebsd.org/archives/freebsd-emulation List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-emulation@freebsd.org On 25/10/21 08:23, Kevin Oberman wrote: > Since the update to virtualbox-ose-kmod-6.1.28, I have been seeing a very > large number of the error: > vboxdrv: Bad CPU context error at line 373 in SUPDrv-freebsd.c: > ulCmd=0x2000568a: 0x282->0x287! > hundreds of times a day. > > I have seen no actual issues with my VMs. They run fine as far as I can > tell. Any idea if I need to worry about these messages? Any explanation of > what they might mean? I have no idea of what this means, but a quick look at the port shows this is a wasrning we are adding in out patches, from patch-src_VBox_HostDrivers_Support_freebsd_SUPDrv-freebsd.c: +#ifdef VBOX_WITH_EFLAGS_AC_SET_IN_VBOXDRV + /* + * Before we restore AC and the rest of EFLAGS, check if the IOCtl handler code + * accidentially modified it or some other important flag. + */ + if (RT_UNLIKELY( (ASMGetFlags() & (X86_EFL_AC | X86_EFL_IF | X86_EFL_DF | X86_EFL_IOPL)) + != ((fSavedEfl & (X86_EFL_AC | X86_EFL_IF | X86_EFL_DF | X86_EFL_IOPL)) | X86_EFL_AC) )) + { + char szTmp[48]; + RTStrPrintf(szTmp, sizeof(szTmp), "ulCmd=%#x: %#x->%#x!", ulCmd, (uint32_t)fSavedEfl, (uint32_t)ASMGetFlags()); + supdrvBadContext(&g_VBoxDrvFreeBSDDevExt, "SUPDrv-freebsd.c", __LINE__, szTmp); + } +#endif Maybe someone with bettern kernel/architecture knowledge can make something out from this piece of code. -- Guido Falsi