Date: Mon, 25 Oct 2021 13:01:20 +0200 From: Guido Falsi via emulation <emulation@freebsd.org> To: Kevin Oberman <rkoberman@gmail.com>, "freebsd-emulation@freebsd.org" <emulation@freebsd.org> Subject: Re: Kernel error reports from VirtualBax Message-ID: <129b5d70-f4e4-9fbe-c884-b4b68f5aeed1@madpilot.net> In-Reply-To: <584ba151-97fa-5507-59c8-08c081798ef8@madpilot.net> References: <CAN6yY1vfLD1iAuCu0DFxtoqVH-DzeeCwGxBu=0gDmtm8xq0j=g@mail.gmail.com> <584ba151-97fa-5507-59c8-08c081798ef8@madpilot.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25/10/21 09:35, Guido Falsi via emulation wrote: > 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: After this message I took a better look and discovered I made a one line mistake when updating the port. This very patch did not apply cleanly, so I replayed it by hand, and in doing that I skipped removing one line of code, that was causing your issue. I have just pushed a commit fixing this error: https://cgit.freebsd.org/ports/commit/?id=32c43c505242463fb127845d0208ecf345124d13 Luckily the error looks actually unharmful apart fro the warnings being logged. Thanks for pointing the issue here, would have not noticed otherwise. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?129b5d70-f4e4-9fbe-c884-b4b68f5aeed1>