Bug 236917 - emulators/virtualbox-ose: Sleeping thread owns a non-sleepable lock kernel panic
Summary: emulators/virtualbox-ose: Sleeping thread owns a non-sleepable lock kernel panic
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: vbox
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-31 19:42 UTC by Derek Schrock
Modified: 2019-04-13 23:35 UTC (History)
0 users

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


Attachments
Three set of panic backtraces (5.86 KB, text/plain)
2019-04-13 23:35 UTC, Derek Schrock
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Derek Schrock 2019-03-31 19:42:59 UTC
FreeBSD 12.0-RELEASE-p3 amd64 host running multiple guests (FreeBSD, RHEL, Fedora, Windows) I'll get the follow kernel panic (see below).  It seems to be popular during startups of the hosts however I've seen it on long running states as well.  I've had this kernel panic this host 4 time in the past month.  I don't have any reproducers.

The vbox home directory and data is hosted on a ZFS mirror.

 kernel: Sleeping thread (tid 100909, pid 1118) owns a non-sleepable lock
 kernel: KDB: stack backtrace of thread 100909:
 kernel: #0 0xffffffff80ba6de1 at mi_switch+0xe1
 kernel: #1 0xffffffff80bf5c45 at sleepq_catch_signals+0x405
 kernel: #2 0xffffffff80bf5f24 at sleepq_timedwait_sig+0x14
 kernel: #3 0xffffffff82669ba6 at rtR0SemEventMultiBsdWait+0x2a6
 kernel: #4 0xffffffff82a9784a at __stop_set_sysinit_set+0x9e02
 kernel: #5 0xffffffff8263fa61 at supdrvIOCtlInnerUnrestricted+0x1781
 kernel: #6 0xffffffff8264d3fd at VBoxDrvFreeBSDIOCtl+0xed
 kernel: #7 0xffffffff80a51acd at devfs_ioctl+0xad
 kernel: #8 0xffffffff811f945e at VOP_IOCTL_APV+0x7e
 kernel: #9 0xffffffff80c7a144 at vn_ioctl+0x1a4
 kernel: #10 0xffffffff80a520af at devfs_ioctl_f+0x1f
 kernel: #11 0xffffffff80c04f3d at kern_ioctl+0x26d
 kernel: #12 0xffffffff80c04c5e at sys_ioctl+0x15e
 kernel: #13 0xffffffff81075449 at amd64_syscall+0x369
 kernel: #14 0xffffffff8104fd1d at fast_syscall_common+0x101
 kernel: panic: sleeping thread
 kernel: cpuid = 2
 kernel: time = 1554059485
 kernel: KDB: stack backtrace:
 kernel: #0 0xffffffff80be7977 at kdb_backtrace+0x67
 kernel: #1 0xffffffff80b9b563 at vpanic+0x1a3
 kernel: #2 0xffffffff80b9b3b3 at panic+0x43
 kernel: #3 0xffffffff80bfd412 at propagate_priority+0x2b2
 kernel: #4 0xffffffff80bfe048 at turnstile_wait+0x338
 kernel: #5 0xffffffff80b7ade6 at __mtx_lock_sleep+0x196
 kernel: #6 0xffffffff80f0071e at vm_reserv_alloc_page+0x4ee
 kernel: #7 0xffffffff80ef2c7e at vm_page_alloc_domain_after+0xde
 kernel: #8 0xffffffff80ef2aa4 at vm_page_alloc+0x74
 kernel: #9 0xffffffff80edbd3c at vm_fault_hold+0x13ac
 kernel: #10 0xffffffff80eda940 at vm_fault+0x60
 kernel: #11 0xffffffff81074ae3 at trap_pfault+0x163
 kernel: #12 0xffffffff81074175 at trap+0x425
 kernel: #13 0xffffffff8104f435 at calltrap+0x8
Comment 1 Derek Schrock 2019-04-13 23:35:20 UTC
Created attachment 203654 [details]
Three set of panic backtraces

After upgrading to virtualbox-ose-5.2.26_4 today three panics in a row with mildly different backtraces.  Disabling vboxheadless and starting vboxheadless by hand did not panic the machine.

All panics were "Sleeping thread (tid X, pid Y) owns a non-sleepable lock"
All referencing VBoxDrvFreeBSDIOCtl and rtR0SemEventWait

Should this be reported to upsteam?