Bug 229428 - emulators/virtualbox-ose-kmod kernel panic on boot in 11.2-RELEASE
Summary: emulators/virtualbox-ose-kmod kernel panic on boot in 11.2-RELEASE
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Some People
Assignee: vbox
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-30 13:39 UTC by A.Rymkus
Modified: 2018-07-09 01:36 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (vbox)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description A.Rymkus 2018-06-30 13:39:59 UTC
I upgraded my instance using `freebsd-update upgrade -r 11.2-RELEASE` and did first reboot after new kernel was installed.

Kernel panic while loading package's driver caused reboot loop.

I had to enter the single-user mode and deinstall this package and virtuabox-ose (both version 5.2.12).

I didn't caught the exception, but have results of savecore, should I attach them here?
Comment 1 A.Rymkus 2018-06-30 13:56:32 UTC
My hardware:
HPE ProLiant ML10 Gen9
E3-1225v5 NHP Tower(4U)/Xeon4C 3.3GHz(8MB)/8GB UD_2133/IntelRST(ZM/RAID 0/1/10/5)/1TB 7.2k SATA 6G(up4/6)LFF/noDVD/Intel AMT 11.0/1NHPFan/1GBEth/300W(NHP)

With an additional Intel NIC (Intel EXPI9301CTBLK)
Comment 2 rkoberman 2018-06-30 16:07:07 UTC
This was a KBI breakage. You need to re-install virtualbox-ose-kmod from ports. Since you have deleted virtualbox-ose, you will also need to reinstall it but this may be done either from ports or packages.
Comment 3 Jason W. Bacon freebsd_committer 2018-07-08 02:27:57 UTC
Seeing the same issue on a Thinkpad I just upgraded.

Workaround:

1. Boot from a USB stick or DVD
2. Select Live CD
3. Log in as root
4. mount /dev/ada0p2 /mnt
5. vi /mnt/boot/loader.conf
Comment out vboxdrv_load="YES"
6. vi /mnt/etc/rc.conf
Comment out vboxnet_enable="YES"
7. reboot
Comment 4 rkoberman 2018-07-08 03:18:12 UTC
(In reply to Jason W. Bacon from comment #3)
And then re-install the virtualbox-ose-kmod port. Re-installing the package won't help. If virtuwlbox-ose is the same version as your current port version of the kmod, that should do the trick. You may need to pull the port down from svn or git repo.
Comment 5 Jason W. Bacon freebsd_committer 2018-07-08 12:57:03 UTC
So is the current package for 11.2 built on 11.1?  Any guess on when the package for 11.2 will be fixed?  Or is this a matter of fixing the kernel? Thanks...
Comment 6 rkoberman 2018-07-08 14:41:38 UTC
(In reply to Jason W. Bacon from comment #5)
It is my understanding that pacages are built on the oldest supported release of each major version, so packages will not be built on 11.2 for a very long time.

There needs to be a solution for this, but it's not obvious to me.

I could build an 11.2 package and place it on my server, but you really should not trust it. Perhaps a spcial build of this and the nvidia modules could be arranged.
Comment 7 Jason W. Bacon freebsd_committer 2018-07-08 21:58:36 UTC
I wouldn't bother building special packages.  The only real solution is one that prevents "pkg upgrade" from rendering systems unbootable by installing an incompatible module.

I'll hold off on upgrading any other systems that run VirtualBox until the official package works on 11.2.
Comment 8 rkoberman 2018-07-09 01:36:03 UTC
(In reply to Jason W. Bacon from comment #7)
We still need a solution for both VB and nvidia. There won't be an 11.2 build until October, when 11.1 is EOL.