New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kernel: [ 32.960029] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [ip:1924] #171
Comments
If I disable audio/camera/gps in avd/config.ini there are "only" CPU soft lockups and there are no other audio/camera warnings/errors that I saw earlier. I'm seeing soft lockups elsewhere on the net with Qemu in some old threads but usually related to specific (buggy) kernel versions or Linux distro version but nothing specific to Android emulator and CentOS. Is it possible that the kernel version used on this VM with CentOS 7.8 has bugs and incompatible with Qemu/Android emulator? Not sure how to verify.
Previously on different (physical) machine I managed to run scripts successfully and these were CentOS and kernel versions:
|
A bit more of kernel logging before the soft lockup:
This @pokowaka any idea how this "Comm: ip" can be further diagnosed? I've tried with older kernel and it's the same. Also I've tried with qemu monitor but it's removed and can't open adb shell since emulator is offline. |
Unfortunately I'm not the kernel expert on the team. @741g would you have any insights? |
According to https://www.kernel.org/doc/html/latest/admin-guide/tainted-kernels.html, the last log line merely indicates that the kernel marked itself as tainted after the soft lockup. The soft lockup indicates that the kernel was spinning for 23s without scheduling another thread. Resulting in no progress (which likely causes the device to be offline). |
It looks like the kernel is trying to notify the host (https://elixir.bootlin.com/linux/v4.14.156/source/drivers/virtio/virtio_pci_common.c#L44) but is unable to proceed. I guess this should trap the hypervisor and give control to qemu to handle the actual write. |
Gives:
2 cases it seems:
|
Thank you for help with debugging. 👍 Small update: I am seeing soft lockup in the same VM also with native Android Emulator without using docker:
Somehow O system image (Android kernel 3.10.x) does boot without the soft lockup issue. |
Seems like an issue with CentOS 7 inside ESXi 6.5 and not connected directly to the project. No known workaround found. CentOS 8 seems to be working without soft lockups. Closing issue. |
I'm trying to make scripts work on CentOS VM and I'm seeing
soft lockups
. Any hint is appreciated. KVM is enabled. Proxy is used and I can see env variables are correctly configured inside container, proxy is not localhost but an IP. I'm creating image and running container as:Emulator stays in offline mode forever. Private/public keys are set and seems to be correctly passed in container.
There are
soft lockups
in log. Whole log iscontainer_soft_lockup.txt and below is only the first
soft lockup
:Last `soft lockup` error (click to expand)
Only errors filtered (click to expand)
Thank you!
/cc @pokowaka
The text was updated successfully, but these errors were encountered: