Date: Mon, 18 Oct 2010 00:18:34 +0200 From: Tomek CEDRO <tomek.cedro@gmail.com> To: Bernhard Froehlich <decke@freebsd.org> Cc: freebsd-ports-bugs@freebsd.org, vbox@freebsd.org Subject: Re: VirtualBox kernel modules and kernel panic Message-ID: <AANLkTikXvP=2dqUftKM2jHKCC-2ba_h9bx_x8Sqm9RFe@mail.gmail.com> In-Reply-To: <f9bb4b53d0eff021a077c6ac90c56e82@bluelife.at> References: <AANLkTi=3VVVv5JTR=E7XBYDW5HELpQ6eUAQuhy7cfrR6@mail.gmail.com> <f9bb4b53d0eff021a077c6ac90c56e82@bluelife.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 17, 2010 at 4:27 PM, Bernhard Froehlich <decke@freebsd.org> wrote: > (..) > This problem is well known and documented. Please only put > vboxdrv_load="YES" in loaders.conf and load the network modules per rc > startscript. > http://wiki.freebsd.org/VirtualBox Ah, figured out myself already that vboxdrv does not cause crash, only the network driver. Thank you for hint and good luck with fixing that nasty bug! :-) Best regards, Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikXvP=2dqUftKM2jHKCC-2ba_h9bx_x8Sqm9RFe>