VMware Communities
fboevere
Contributor
Contributor

Fedora 36 (guest) kernel panic on Windows 10 host with workstation 16

I'm running workstation 16.2.3 build-19376536 on Windows 10
Fedora 36 (kernel 5.17.12-300.fc36.x86_64) is the guest OS and the Fedora kernel panics accasionally when entering or exiting a RHEL8 docker image (from Dockerhub).
The container name is 'rhel8' and it is started with: docker start -i rhel8
Then ctrl-D to exit the RH8 container shell (and back in Fedora).
Repeating this eventually leads to a Fedora kernel panic (nr of attempts varies, sometimes 2, sometimes 30)

Attached is Fedora output from /proc/kmsg from 2 panics..
the first contains: "BUG: unable to handle page fault for address: 0000000100000000"
The second contains: "BUG: kernel NULL pointer dereference, address: 000000000000000f"
Also attached, output from Vmware Help -> Support -> Collect Support Data
This was generated after kernel panic 1, while it was in frozen state, but had not been powered down yet

0 Kudos
2 Replies
bluefirestorm
Champion
Champion

Have a look at this

https://www.redhat.com/sysadmin/linux-troubleshooting-navigating-perfect-storm

The call trace in your kernel panic looks similar; so you may want to try the workaround suggested in that link.

<1>[ 92.125361] BUG: kernel NULL pointer dereference, address: 000000000000000f
<1>[ 92.125366] #PF: supervisor read access in kernel mode

<4>[ 92.125412] Call Trace:
<4>[ 92.125415] <TASK>
<4>[ 92.125416] bfq_idle_extract+0xa7/0xb0
<4>[ 92.125421] bfq_put_idle_entity+0x12/0x60
<4>[ 92.125423] bfq_bfqq_served+0xb0/0x1a0
<4>[ 92.125426] bfq_dispatch_request+0x31e/0x12e0

0 Kudos
fboevere
Contributor
Contributor

I don't see this happen anymore on 5.18.5-200.fc36
It might be related to https://github.com/torvalds/linux/commit/ab552fcb17cc9e4afe0e4ac4df95fc7b30e8490a

 

Tags (1)
0 Kudos