-
Notifications
You must be signed in to change notification settings - Fork 59
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
aws: kola podman.base tests failing with kernel warning unbind_from_irqhandler+0x4e/0x60 #606
Comments
Opened https://bugzilla.redhat.com/show_bug.cgi?id=1870209 for this. cc @masneyb |
Some more info here. This error happens very early on boot before systemd even starts. It seems as if there is nothing special that needs to happen in order for this "error" to occur. Our CI seems to catch it most in tests that consist of a reboot, which means that it's more likely the console output will contain the kernel trace text. I just booted a
|
Note that |
Though I do see the problem on
|
And even on |
yep.
|
I dusted off rpm-ostree-bisect and found that the first time this problem started showing up for us was in
|
I posted a patch that fixes the issue: https://lore.kernel.org/lkml/20201106003529.391649-1-bmasney@redhat.com/T/#u. Thanks to @dustymabe for setting up a Fedora system at AWS for me that reproduced the error. Note for future reference: when compiling torvalds/master or linux-next on a Fedora 33 system, the following error is thrown:
A workaround for this is posted at https://lore.kernel.org/bpf/20201016213835.GJ1461394@krava/T/. |
Thanks so much @masneyb! |
v2 fix has been merged into the xen subsystem tree for 5.10: https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/commit/?h=for-linus-5.10b&id=65cae18882f943215d0505ddc7e70495877308e6 |
Looks like this is indeed fixed. Tested on
|
We're seeing an
unbind_from_irqhandler+0x4e/0x60
kernel warning. This has been happening for a while and was confused with the other kernel issue in #507.An example of the error is in
32.20200818.20.0
(testing-devel
) withkernel-5.7.15-200.fc32.x86_64
.jenkins run
Here is the full stack trace:
The text was updated successfully, but these errors were encountered: