Bug 249326 - emulators/virtualbox-ose-kmod panic in 13-CURRENT r365718 and in 12-STABLE r365830
Summary: emulators/virtualbox-ose-kmod panic in 13-CURRENT r365718 and in 12-STABLE r3...
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Konstantin Belousov
URL:
Keywords:
: 249407 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-09-14 22:22 UTC by Adriaan de Groot
Modified: 2020-09-18 20:37 UTC (History)
6 users (show)

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


Attachments
Crash trace (9.67 KB, application/octet-stream)
2020-09-15 14:31 UTC, Adriaan de Groot
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adriaan de Groot freebsd_committer 2020-09-14 22:22:05 UTC
- in 13-CURRENT, r365036, with virtualbox-ose-kmod 5.2.44_1, `kldload vboxdrv` is ok
- in 13-CURRENT, r365718, with same virtualbox-ose-kmod port, `kldload vboxdrv` panics with a page fault in kernel mode

I don't think I use bridged mode in anything, but I do have nvidia graphics, which might connect to PR 248339. I'd need to re-tool some bits to get an actual crash dump or to bisect this.
Comment 1 Adriaan de Groot freebsd_committer 2020-09-15 13:25:04 UTC
world / kernel bisecting

365036 ok
365718 bad
365360 ok (loaded vboxdrv built agains 365036)
365500 bad (when loading vboxdrv built against 365036)
365430 ok (")
365465 ok (")
365480 ok (")
365484 ok (")
365485 ok (")
365488 bad (")
Comment 2 Adriaan de Groot freebsd_committer 2020-09-15 14:31:27 UTC
Created attachment 217970 [details]
Crash trace

r365487 is ok
r365488 is bad (with vboxdrv built against known-good r365036)

Crash trace from that bad r after `kldload vboxdrv`
Comment 3 Adriaan de Groot freebsd_committer 2020-09-15 18:49:31 UTC
Assigning to kib@ who isn't a ports committer and isn't involved with VBox anyway, but with r365488 triggering panics from the vbox driver, I suspect there's edge cases (or external drivers) that need work.
Comment 4 Graham Perrin 2020-09-16 03:50:05 UTC
I began encountering this bug after upgrading -CURRENT from r365364 to r365727. 

At the time of writing: 

root@momh167-gjp4-8570p:~ # date ; uname -v
Wed Sep 16 04:46:59 BST 2020
FreeBSD 13.0-CURRENT #67 r365756: Tue Sep 15 23:25:46 BST 2020     root@momh167-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG 
root@momh167-gjp4-8570p:~ # grep vbox /boot/loader.conf
# vboxdrv_load="YES"
root@momh167-gjp4-8570p:~ # grep vbox /etc/rc.conf
# r365756a panics when vboxnet starts
# vboxnet_enable="YES"
root@momh167-gjp4-8570p:~ # 

– if I do not load vboxdrv (loader.conf) and if I do not enable vboxnet (rc.conf) then the kernel panics on: 

vboxnet onestart

– and continue does _not_ lead to a dump. 

----

HP EliteBook 8570p.
Comment 5 Graham Perrin 2020-09-16 03:59:04 UTC
root@momh167-gjp4-8570p:~ # pciconf -lv
hostb0@pci0:0:0:0:      class=0x060000 rev=0x09 hdr=0x00 vendor=0x8086 device=0x0154 subvendor=0x103c subdevice=0x17a7
    vendor     = 'Intel Corporation'
    device     = '3rd Gen Core processor DRAM Controller'
    class      = bridge
    subclass   = HOST-PCI
pcib1@pci0:0:1:0:       class=0x060400 rev=0x09 hdr=0x01 vendor=0x8086 device=0x0151 subvendor=0x8086 subdevice=0x2010
    vendor     = 'Intel Corporation'
    device     = 'Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port'
    class      = bridge
    subclass   = PCI-PCI
xhci0@pci0:0:20:0:      class=0x0c0330 rev=0x04 hdr=0x00 vendor=0x8086 device=0x1e31 subvendor=0x103c subdevice=0x17a7
    vendor     = 'Intel Corporation'
    device     = '7 Series/C210 Series Chipset Family USB xHCI Host Controller'
    class      = serial bus
    subclass   = USB
none0@pci0:0:22:0:      class=0x078000 rev=0x04 hdr=0x00 vendor=0x8086 device=0x1e3a subvendor=0x103c subdevice=0x17a7
    vendor     = 'Intel Corporation'
    device     = '7 Series/C216 Chipset Family MEI Controller'
    class      = simple comms
uart2@pci0:0:22:3:      class=0x070002 rev=0x04 hdr=0x00 vendor=0x8086 device=0x1e3d subvendor=0x103c subdevice=0x17a7
    vendor     = 'Intel Corporation'
    device     = '7 Series/C210 Series Chipset Family KT Controller'
    class      = simple comms
    subclass   = UART
em0@pci0:0:25:0:        class=0x020000 rev=0x04 hdr=0x00 vendor=0x8086 device=0x1502 subvendor=0x103c subdevice=0x17a7
    vendor     = 'Intel Corporation'
    device     = '82579LM Gigabit Network Connection (Lewisville)'
    class      = network
    subclass   = ethernet
ehci0@pci0:0:26:0:      class=0x0c0320 rev=0x04 hdr=0x00 vendor=0x8086 device=0x1e2d subvendor=0x103c subdevice=0x17a7
    vendor     = 'Intel Corporation'
    device     = '7 Series/C216 Chipset Family USB Enhanced Host Controller'
    class      = serial bus
    subclass   = USB
hdac1@pci0:0:27:0:      class=0x040300 rev=0x04 hdr=0x00 vendor=0x8086 device=0x1e20 subvendor=0x103c subdevice=0x17a7
    vendor     = 'Intel Corporation'
    device     = '7 Series/C216 Chipset Family High Definition Audio Controller'
    class      = multimedia
    subclass   = HDA
pcib2@pci0:0:28:0:      class=0x060400 rev=0xc4 hdr=0x01 vendor=0x8086 device=0x1e10 subvendor=0x103c subdevice=0x17a7
    vendor     = 'Intel Corporation'
    device     = '7 Series/C216 Chipset Family PCI Express Root Port 1'
    class      = bridge
    subclass   = PCI-PCI
pcib3@pci0:0:28:2:      class=0x060400 rev=0xc4 hdr=0x01 vendor=0x8086 device=0x1e14 subvendor=0x103c subdevice=0x17a7
    vendor     = 'Intel Corporation'
    device     = '7 Series/C210 Series Chipset Family PCI Express Root Port 3'
    class      = bridge
    subclass   = PCI-PCI
pcib4@pci0:0:28:3:      class=0x060400 rev=0xc4 hdr=0x01 vendor=0x8086 device=0x1e16 subvendor=0x103c subdevice=0x17a7
    vendor     = 'Intel Corporation'
    device     = '7 Series/C216 Chipset Family PCI Express Root Port 4'
    class      = bridge
    subclass   = PCI-PCI
ehci1@pci0:0:29:0:      class=0x0c0320 rev=0x04 hdr=0x00 vendor=0x8086 device=0x1e26 subvendor=0x103c subdevice=0x17a7
    vendor     = 'Intel Corporation'
    device     = '7 Series/C216 Chipset Family USB Enhanced Host Controller'
    class      = serial bus
    subclass   = USB
isab0@pci0:0:31:0:      class=0x060100 rev=0x04 hdr=0x00 vendor=0x8086 device=0x1e55 subvendor=0x103c subdevice=0x17a7
    vendor     = 'Intel Corporation'
    device     = 'QM77 Express Chipset LPC Controller'
    class      = bridge
    subclass   = PCI-ISA
ahci0@pci0:0:31:2:      class=0x010601 rev=0x04 hdr=0x00 vendor=0x8086 device=0x1e03 subvendor=0x103c subdevice=0x17a7
    vendor     = 'Intel Corporation'
    device     = '7 Series Chipset Family 6-port SATA Controller [AHCI mode]'
    class      = mass storage
    subclass   = SATA
vgapci0@pci0:1:0:0:     class=0x030000 rev=0x00 hdr=0x00 vendor=0x1002 device=0x6841 subvendor=0x103c subdevice=0x17a9
    vendor     = 'Advanced Micro Devices, Inc. [AMD/ATI]'
    device     = 'Thames [Radeon HD 7550M/7570M/7650M]'
    class      = display
    subclass   = VGA
hdac0@pci0:1:0:1:       class=0x040300 rev=0x00 hdr=0x00 vendor=0x1002 device=0xaa90 subvendor=0x103c subdevice=0x17a9
    vendor     = 'Advanced Micro Devices, Inc. [AMD/ATI]'
    device     = 'Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series]'
    class      = multimedia
    subclass   = HDA
iwn0@pci0:4:0:0:        class=0x028000 rev=0x34 hdr=0x00 vendor=0x8086 device=0x0082 subvendor=0x8086 subdevice=0x1301
    vendor     = 'Intel Corporation'
    device     = 'Centrino Advanced-N 6205 [Taylor Peak]'
    class      = network
root@momh167-gjp4-8570p:~ # 

----

QuickSpecs (DA - 14304 Worldwide — Version 16 — June 6, 2013) for HP EliteBook 8470p and HP EliteBook 8570p
<https://web.archive.org/web/20150906211950/http://www8.hp.com:80/h20195/v2/GetPDF.aspx/c04163744.pdf>

HP EliteBook 8570p Notebook PC Specifications | HP® Customer Support
<https://support.hp.com/gb-en/document/c03393945>
Comment 6 Guido Falsi freebsd_committer 2020-09-17 19:57:30 UTC
*** Bug 249407 has been marked as a duplicate of this bug. ***
Comment 7 Yuri Victorovich freebsd_committer 2020-09-17 22:45:51 UTC
12.2-STABLE is also crashing.

12.2-STABLE #0 r365688 is still good.
12.2-STABLE #0 r365830 is bad.

Could you please take back the offending commits from 12?
Comment 8 Adriaan de Groot freebsd_committer 2020-09-18 08:12:37 UTC
I had hoped this PR would put the brakes on an MFH, but no. Since I filed it as a ports bug, I don't really know what else to do.

For latecomers to the thread: if you need virtualbox,

for 13-CURRENT, use r365487
for 12-STABLE, use r365688
Comment 9 Guido Falsi freebsd_committer 2020-09-18 08:34:58 UTC
(In reply to Adriaan de Groot from comment #8)

r365488 was merged to 12 in r365803, so 12-STABLE should be ok up to r365802.

In fact if someone could confirm this it would give a clearer indication that the problematic commit is r365488.
Comment 10 O. Hartmann 2020-09-18 16:31:20 UTC
I can confirm, that for CURRENT, at least reverting back to r365487 solves the issue with panicing kernel when voxdrv.ko is enabled with all the other bugs and failures back in CURRENT, which have been solved since then, the same is for 12-STABLE at r365688, as suggested.

On CURRENT, I also use an nvidia discrete GPU with driver version 440.100.
Comment 11 Tomasz Sowa 2020-09-18 20:37:41 UTC
(In reply to Guido Falsi from comment #9)

on 365802 12-STABLE works correctly for me

/home/tomek$ uname -a
FreeBSD s100.ttmath.org 12.2-STABLE FreeBSD 12.2-STABLE r365802 tomek  amd64
/home/tomek$ grep vbox /etc/rc.conf
vboxnet_enable="YES"
/home/tomek$ grep vbox /boot/loader.conf 
vboxdrv_load="YES"
/home/tomek$ kldstat
Id Refs Address                Size Name
 1   70 0xffffffff80200000  1aacc58 kernel
 2    1 0xffffffff81cad000    1e048 geom_journal.ko
 3    1 0xffffffff81ccd000     41e0 amdtemp.ko
 4    2 0xffffffff81cd2000     2550 amdsmn.ko
 5    1 0xffffffff81cd5000   165920 nvidia-modeset.ko
 6    7 0xffffffff81e3b000     d770 linux_common.ko
 7    3 0xffffffff81e49000    b2868 linux.ko
 8    2 0xffffffff81efc000  15b6618 nvidia.ko
 9    1 0xffffffff834b3000    27cc0 fuse.ko
10    1 0xffffffff834db000     9ef0 cuse.ko
11    3 0xffffffff834e5000    89148 vboxdrv.ko
12    1 0xffffffff83719000     1f3c linsysfs.ko
13    1 0xffffffff8371b000     5500 linprocfs.ko
14    1 0xffffffff83721000     87e8 tmpfs.ko
15    1 0xffffffff8372a000     1a28 fdescfs.ko
16    1 0xffffffff8372c000     2698 intpm.ko
17    1 0xffffffff8372f000      b40 smbus.ko
18    1 0xffffffff83730000     1860 uhid.ko
19    1 0xffffffff83732000     1a40 wmt.ko
20    1 0xffffffff83734000     2908 ums.ko
21    2 0xffffffff83737000     2cd0 vboxnetflt.ko
22    2 0xffffffff8373a000     9bd0 netgraph.ko
23    1 0xffffffff83744000     1770 ng_ether.ko
24    1 0xffffffff83746000     3f00 vboxnetadp.ko
25    1 0xffffffff8374a000    35cb0 linux64.ko
26    1 0xffffffff83780000      4f9 pty.ko
/home/tomek$ pkg info -x nvidia
nvidia-driver-390-390.138
nvidia-settings-440.100