Red Hat Bugzilla – Bug 1281287
Suspend causes a kernel crash
Last modified: 2016-12-20 10:43:01 EST
Description of problem:
Suspend causes a kernel crash. Every time I suspend abrt triggers on both the kernel and xorg-x11-drv-intel.
The kernel abrt is incomplete (because suspend), but because it happens on *most* suspends, and has happened on 4.2.5-300, 4.2.3-300 and 4.2.2-300, I thought I'd try and report it to the best of my ability.
It also has 548 similar reports in FAF.
It's hardware dependent.
gnome-abrt doesn't want to report by default, since the kernel has flags GW. This is correct, but it's the stock Fedora kernel.
I used to get it with tainted realtek modules; but those were not loaded when getting this particular crash.
Version-Release number of selected component (if applicable):
kernel 4.2.5-300 (and 4.2.3-300 and 4.2.2-300)
xorg-x11-drv-intel (same versions)
Most suspend operations
Steps to Reproduce:
2. log in
The screen goes black.
The CPU (or at least motherboard) is still running, drawing a bit of power
Suspend. Power consumption almost nil.
Fedora FAF related: https://retrace.fedoraproject.org/faf/reports/821282/
If it's not OK to report incomplete bugs here, please let me know.
Created attachment 1093066 [details]
Created attachment 1093067 [details]
Created attachment 1093068 [details]
Created attachment 1093069 [details]
Created attachment 1093070 [details]
Created attachment 1093071 [details]
Created attachment 1093072 [details]
Created attachment 1093074 [details]
Created attachment 1093086 [details]
Created attachment 1093089 [details]
Created attachment 1093090 [details]
I didn't duplicate os_info/suspend_stats, etc. The kernel crash had no dmesg, which is likely why it wasn't reportable.
I know that the xorg-x11-drv-intel bit has been reported before. This (suspend kernel crash) looks like it's related because I get them in pairs in gnome-abrt
I've saved the /var/spool/abrt entries if you want any additional files.
Created attachment 1093092 [details]
Created attachment 1093093 [details]
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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
Thank you for reporting this bug and we are sorry it could not be fixed.