-
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
[rawhide][ppc64le] ext.config.kdump.crash failure #1698
Comments
Looks like this in a known upstream issue https://bugzilla.redhat.com/show_bug.cgi?id=2269991 |
Denylist PR : coreos/fedora-coreos-config#2922 |
Kdump currently fails on kernel-next, for ppc64le This is a known upstream bug See coreos/fedora-coreos-tracker#1698
Kdump currently fails on kernel-next, for ppc64le This is a known upstream bug See coreos/fedora-coreos-tracker#1698 Also see upstream bug : https://bugzilla.redhat.com/show_bug.cgi?id=2269991
Kdump currently fails on kernel-next, for ppc64le This is a known upstream bug See coreos/fedora-coreos-tracker#1698 Also see upstream bug : https://bugzilla.redhat.com/show_bug.cgi?id=2269991
This is a known upstream bug See coreos/fedora-coreos-tracker#1698 Also see upstream bug : https://bugzilla.redhat.com/show_bug.cgi?id=2269991
This is a known upstream bug See coreos/fedora-coreos-tracker#1698 Also see upstream bug : https://bugzilla.redhat.com/show_bug.cgi?id=2269991
supposedly fixed by |
@dustymabe testing this on a PPC64le machine today still fails. I did some digging and I think the issue is that this makedumpfile patch is not backported into
See: https://bugzilla.redhat.com/show_bug.cgi?id=2269991#c7 @coiby could you backport the makedumpfile fix to Another fix is to pin the kernel to a prior version than |
Hi @jbtrystram, kexec-tools-2.0.28-7.fc41 now includes the makedumpfile fix, thanks for the reminder! |
The snooze for this was dropped in coreos/fedora-coreos-config@7857871 All should be good now. |
relevant Console output:
test log :
How hard would it be to save
kexec-dmesg.log
from the test run ?The text was updated successfully, but these errors were encountered: