Quantcast
Channel: VirtualBox on linux: hangs on __lock_acquire on Fedora Core 35 - Server Fault
Viewing all articles
Browse latest Browse all 2

VirtualBox on linux: hangs on __lock_acquire on Fedora Core 35

$
0
0

VirtualBox (VirtualBox-6.1.x86_64) has for sometime been useless on my workstation (Linux FC35,kernel is 5.16.12-200.fc35.x86_64+debug: but the issue existed previously on FC33). The GUI starts, but attempting to activate any VM results in a hang window ("Starting VM...." and "Starting VM.../2").dmesg complains about a null pointer:

[Mon Mar  7 15:38:56 2022] SUPR0GipMap: fGetGipCpu=0xb[Mon Mar  7 15:38:59 2022] BUG: kernel NULL pointer dereference, address: 0000000000000018[Mon Mar  7 15:38:59 2022] #PF: supervisor read access in kernel mode[Mon Mar  7 15:38:59 2022] #PF: error_code(0x0000) - not-present page[Mon Mar  7 15:38:59 2022] PGD 3c993067 P4D 3c993067 PUD 3ca29067 PMD 0 [Mon Mar  7 15:38:59 2022] Oops: 0000 [#1] PREEMPT SMP NOPTI[Mon Mar  7 15:38:59 2022] CPU: 1 PID: 12343 Comm: EMT-0 Tainted: G           OE     5.16.12-200.fc35.x86_64+debug #1[Mon Mar  7 15:38:59 2022] Hardware name: Dell Inc. Studio XPS 7100/0FF3FN, BIOS A02 05/05/2010[Mon Mar  7 15:38:59 2022] RIP: 0010:__lock_acquire+0x5df/0x1de0

After killing the windows and associated processes leaves the vbox kernel modules in an unresponsive state (they cannot be unloaded), and at least two stray userspace processes, VBoxXPCOMIPCD and VBoxSvc (the first can be disposed of via kill, the second becomes a zombie after kill). At that point vboxmanage is also hosed. straceing shows it hangs on a futex:

futex(0xacb320, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {tv_sec=1649267441, tv_nsec=663216000}, FUTEX_BITSET_MATCH_ANY

I scoured the net, not finding much (in fact, exceedingly littel) Any ideas/experiences?


Viewing all articles
Browse latest Browse all 2

Latest Images

Trending Articles



Latest Images