On this system kdump works when manually triggered, but not when 1) system sometimes reboots on resume from suspend, 1096989 2) have happened four times that the system just reboots during use (there is not even a delay like when it is saving vmcore) - it would be vey interesting to catch the causes ! Actual results: direct reboot Expected results: kdump should save dump before reboot How reproducible: I have had more than 30 crashes, ang got one dump. Versions: kexec-tools 2.0.4-27.fc20.x86_64 kernel 3.14.4-200.fc20.x86_64 Hardware: Lenovo Thinkpad R61 and T61 - identical behaviour (same disk swapped between laptops for testing) System have / in regular unencrypted LVM, but /home and /swap in encrypted lvm.
Hi From the description it looks like a kernel bug instead of kdump bug, rebooting happens sometimes after resume from suspend, right? So I guess there's no panic happens thus kdump did not triggered. Could you try the latest mainline kernel (make sure there's no RANDOMIZE_BASE=y)? If you have serial console log it will be helpful. Thanks Dave
Sorry for the delay. Yes sometimes it reboots when we wake it up from suspend. I am new to fedora, so please tell me: 1) How do i change to mainline kernel ? 2) How can I make sure there's no RANDOMIZE_BASE=y ? 3) How do I get a console log ?
Moving this to kernel component (In reply to Morgan Leijström from comment #2) > Sorry for the delay. > > Yes sometimes it reboots when we wake it up from suspend. > > I am new to fedora, so please tell me: > 1) How do i change to mainline kernel ? You can download source from kernel.org and build by yourself. But latest Fedora rawhide kernel is very close to mainline. So probably you can download the rpm and try: http://koji.fedoraproject.org/koji/packageinfo?packageID=8 Below is the latest rpm I see: http://koji.fedoraproject.org/koji/buildinfo?buildID=537825 > 2) How can I make sure there's no RANDOMIZE_BASE=y ? Probably not necessary if this is not a kdump problem.. > 3) How do I get a console log ? You need a serial port on your machine and connect it to another machine. http://www.vanemery.com/Linux/Serial/serial-console.html Thanks Dave
Thanks for the hints. I have been swamped with jobs... meanwhile the normal kernel have updated twice and many other things of course. And suddenly it worked, at least now - kdump saved a vmcore: https://bugzilla.redhat.com/show_bug.cgi?id=1096989#c20
Status: Problem is worse, crashing almost every resume, and never a kdump log. kernel 3.15.6-200.fc20.x86_64 At the same time we run mageia 5 alpha 1 on the T61 and the problem is gone there now. Being swamped with jobs and this is a production machine, we are thinking on simply switching back to mageia on this machine too.
*********** 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 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. 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 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.