Date: Tue, 26 Jun 2018 09:25:28 +0000 From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic Message-ID: <bug-228535-1689-xlo80M1ooD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-228535-1689@https.bugs.freebsd.org/bugzilla/> References: <bug-228535-1689@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228535 me@janh.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |me@janh.de --- Comment #9 from me@janh.de --- I have hit this problem, too. For me, it is different than previous problems with kernel modules from por= ts after minor FreeBSD version updates: There were modules that would not load, but very rarely an old module would lead to a panic. I have vboxdrv_load=3D"YES" in /boot/loader.conf and I could not immediatel= y tell what caused the panic. Obviously, single user mode would not work, either, = but loading the old kernel did. Having freebsd-update print a warning in the end to update ports with kernel modules would not help in this case, either: The panic already happens after installing the kernel and rebooting and you cannot even install the userlan= d. If there was such a warning, it would have to be with the first prompt for a reboot. Rebuilding ports at that time would not be the best idea, either, s= ince the userland is still old. The message would have to tell you to disable everything from ports in /boot/loader.conf, /etc/rc.conf|kld_list, and simi= lar places. Besides emulators/virtualbox-ose-kmod, I also had to rebuild x11/nvidia-dri= ver, but it was nicer: There was no crash, xorg simply would not start. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-228535-1689-xlo80M1ooD>