-
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
kola: ext.config.kdump.crash
test fails on AWS aarch64 instances
#1187
Comments
It turns out removing |
The irqpoll` karg that gets added when the crash kernel is started causes issues on AWS aarch64 instances. Let's workaround by removing that from `KDUMP_COMMANDLINE_APPEND` in `/etc/sysconfig/kdump` for now. See coreos/fedora-coreos-tracker#1187
The irqpoll` karg that gets added when the crash kernel is started causes issues on AWS aarch64 instances. Let's workaround by removing that from `KDUMP_COMMANDLINE_APPEND` in `/etc/sysconfig/kdump` for now. See coreos/fedora-coreos-tracker#1187
The irqpoll` karg that gets added when the crash kernel is started causes issues on AWS aarch64 instances. Let's workaround by removing that from `KDUMP_COMMANDLINE_APPEND` in `/etc/sysconfig/kdump` for now. See coreos/fedora-coreos-tracker#1187
The irqpoll` karg that gets added when the crash kernel is started causes issues on AWS aarch64 instances. Let's workaround by removing that from `KDUMP_COMMANDLINE_APPEND` in `/etc/sysconfig/kdump` for now. See coreos/fedora-coreos-tracker#1187
The irqpoll` karg that gets added when the crash kernel is started causes issues on AWS aarch64 instances. Let's workaround by removing that from `KDUMP_COMMANDLINE_APPEND` in `/etc/sysconfig/kdump` for now. See coreos/fedora-coreos-tracker#1187
The irqpoll` karg that gets added when the crash kernel is started causes issues on AWS aarch64 instances. Let's workaround by removing that from `KDUMP_COMMANDLINE_APPEND` in `/etc/sysconfig/kdump` for now. See coreos/fedora-coreos-tracker#1187
The irqpoll` karg that gets added when the crash kernel is started causes issues on AWS aarch64 instances. Let's workaround by removing that from `KDUMP_COMMANDLINE_APPEND` in `/etc/sysconfig/kdump` for now. See coreos/fedora-coreos-tracker#1187
The irqpoll` karg that gets added when the crash kernel is started causes issues on AWS aarch64 instances. Let's workaround by removing that from `KDUMP_COMMANDLINE_APPEND` in `/etc/sysconfig/kdump` for now. See coreos/fedora-coreos-tracker#1187
While we wait on the issue to be fixed upstream we'll workaround for now with: coreos/fedora-coreos-config@4c31f58 |
This should be "fixed" in kexec-tools so we should remove our workaround. |
Links to the fix and subsequent move of the fix: |
I just realized there are a few things that will make it hard to verify this right now. In anything other than So.. if you remove the workaround you can test this in AWS with a |
The issues mentioned in my previous comment are now resolved. You should now be able to test this on |
The irqpoll` karg that gets added when the crash kernel is started causes issues on AWS aarch64 instances. Let's workaround by removing that from `KDUMP_COMMANDLINE_APPEND` in `/etc/sysconfig/kdump` for now. See coreos/fedora-coreos-tracker#1187
The irqpoll` karg that gets added when the crash kernel is started causes issues on AWS aarch64 instances. Let's workaround by removing that from `KDUMP_COMMANDLINE_APPEND` in `/etc/sysconfig/kdump` for now. See coreos/fedora-coreos-tracker#1187
No longer need that workaround since the issue has been fixed Fixes: coreos/fedora-coreos-tracker#1187
No longer need that workaround since the issue has been fixed Fixes: coreos/fedora-coreos-tracker#1187
No longer need that workaround since the issue has been fixed Fixes: coreos/fedora-coreos-tracker#1187
No longer need that workaround since the issue has been fixed Fixes: coreos/fedora-coreos-tracker#1187
This is a follow on issue to #1075. This is specific to AWS aarch64 instances.
kdump on aarch64 AWS instances (in this case c6g.xlarge) gets stuck. This is somehow related to the serial console of the machine.
When setting up kdump and using sysrq to trigger a crash we notice that the crash kernel hangs and never completes. It always gets stuck at a particular point:
If I then type some characters into the serial console the system (or the console) gets unstuck, but it looks like another kexec happens in the background. That kernel eventually bails out (though I do notice this interested stack trace before it does bail out):
and then the system seems to go through a reboot (i.e. I see grub and a full boot happens). At the end of all this there is still never any files created in
/var/crash
.Since the system got hung up initially on a message about the console I decided to try the test after removing
console=ttyS0,115200n8
on the kernel command line. In this case the test passes, but I have no idea why.I have opened a BZ#2080468 to track this issue.
The text was updated successfully, but these errors were encountered: