| Summary: | kdump doesn't work at all on Fedora 25 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Richard W.M. Jones <rjones> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | cz172638, divi, gansalmon, green, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, rjones, ruyang |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-12 10:02:54 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 1400956 | ||
|
Description
Richard W.M. Jones
2016-12-02 16:19:38 UTC
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs. Fedora 25 has now been rebased to 4.9.3-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those. Don't know why I bother. Reproduced on 4.9.10-200. kdump on F25 still does not work. enabled the kernel param, renabled kdump service rebooted Triggered the crash with sysrq. System reboots, nothing is in the /var/crash *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs. Fedora 25 has now been rebased to 4.10.9-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those. Yes it's still a bug. So, I hit this on one of my laptops with Fedora26. Ironic that RedHat people are not looking into it yet, but oh well, Fedora is a DYI thing, right? So I am taking a look. I actually have a bunch of Fedora25 testnodes that used to do over the network crashdumps. I remember there was a bunch of stuff done to make it owrk over nfs, things like installing dracut-network and whatnot. Also crashkernel=128M is way too low nowadays (at least in my setup, so I do 192M). Just checked and alas, no longer working. As usual the best way to debug this is to do the sysrq-c, and ensure that you have clear console visibility to see the messages from the crash kernel that is not going to bother to resetup your screen I suspect. Anyway for my test nodes mount.nfs: protocol is not supported was the message, nice, huh? It was easy to see because no gfx console muddied the waters. Apparently this is because nfsd in rhel7 (on the server) does not export nfs v2 by default, but kdump initramfs only includes nfs.ko. Adding "extra_modules nfsv4" to /etc/kdump.conf helps here. I guess we need a separate ticket for this in kexec-tools since nfs v2 is long disabled in both fedora and rhel by default, yet something relatively recently started this strange exclusion (I verified that rhel7 does not exclude the nfsv3/4 modules by default). Now on my laptop with graphical console getting rid of it seems to be a challenge. But actually switching to to vt2 from X before crash sows that it does work in the end. The problem at hand turned out to be the laptop disk was encrypted so you needed to enter the encryption password for it all to work. So... X froze, I blindly typed my luks password into it, and crashdump worked. Hopefully that'll help you too. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. I did not notice this bug at all :( kexec-tools bugs will route to me, I randomly search kernel bugs then found this.. Crypted disk is not supported, but in latest rawhide, we removed rootfs dependency (it was required previously by dracut), thus if you dump to nfs (non-root) then kdump should work naturally without prompt of password. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |