Date: Wed, 26 May 2010 11:45:20 -0500 (CDT) From: "Sean C. Farley" <scf@FreeBSD.org> To: Beat Gaetzi <beat@FreeBSD.org> Cc: freebsd-emulation@FreeBSD.org Subject: Re: VirtualBox 3.2.0-beta-1 fails to compile on -current Message-ID: <alpine.BSF.2.00.1005261135100.94894@thor.farley.org> In-Reply-To: <4BFD27CD.2090202@FreeBSD.org> References: <4BD9FBA3.1050707@protected-networks.net> <201004291923.19471.jkim@FreeBSD.org> <4BDA2C3A.80506@protected-networks.net> <201004301405.24206.jkim@FreeBSD.org> <AANLkTilh3UPH6J3mMFJmmqSChfUsSqFZXlwitfgtXyPz@mail.gmail.com> <4BFCC397.2030504@FreeBSD.org> <AANLkTilWkXP4oEN11CyfuTvplCBssecbuV2NPXvCtSC5@mail.gmail.com> <4BFD27CD.2090202@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 26 May 2010, Beat Gaetzi wrote: > We received a few reports from users that 3.2.0 panics the host when > loading the kernel module. This is the reason why we haven't announced > a CFT for 3.2.0 yet. On those hosts, did /boot/modules/linker.hints get generated correctly/completely? I have seen, at least from the subversion tree, a very small linker.hints file where I need to rerun kldxref on /boot/modules else a panic may occur. I personally get panics on my FreeBSD 8 amd64 host running the Nvidia driver (currently v195.36.24 but occurred with earlier drivers too). This is with a non-X FreeBSD 8 amd64 guest and using ssh to the guest. I think it is panic'ing when transferring some files to it from the host. Unfortunately, the system locks up completely, so there is no core saved. I would have reported both earlier but life has been very busy. Sean -- scf@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1005261135100.94894>