https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535
m...@janh.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |m...@janh.de
--- Comment #9 from m...@janh.de ---
I have hit this problem, too.
For me, it is different than previous problems with kernel modules from ports
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="YES" in /boot/loader.conf and I could not immediately 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 userland.
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, since
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 similar
places.
Besides emulators/virtualbox-ose-kmod, I also had to rebuild x11/nvidia-driver,
but it was nicer: There was no crash, xorg simply would not start.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
