Bug 1139036 - kernel panic after resume: unable to handle kernel paging request at ffff8800ad1f0000 [NEEDINFO]
Summary: kernel panic after resume: unable to handle kernel paging request at ffff8800...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-07 17:27 UTC by Kamil Páral
Modified: 2014-12-10 14:57 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-12-10 14:57:11 UTC
Type: Bug
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
kernel panic printout (2.91 MB, image/jpeg)
2014-09-07 17:27 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2014-09-07 17:27:49 UTC
Created attachment 935174 [details]
kernel panic printout

Description of problem:
I suspend (to memory) a lot. Sometimes the computer freezes on resume (let say 20% cases). Usually I see just a frozen GNOME, or my screen doesn't turn on at all, but this time I saw a kernel panic printed on screen instead. I took the opportunity and took a picture. Attached.

I have a suspicion it might be related to my Radeon R9 270 graphics card (radeon driver), because it didn't happen so often back when I was using an Intel graphics card. Also it varies a lot during the release lifecycle (maybe according to radeon drivers being updated)? But that's just my suspicion.

Version-Release number of selected component (if applicable):
kernel-3.15.10-201.fc20.x86_64
xorg-x11-drv-ati-7.2.0-3.20131101git3b38701.fc20.x86_64
libdrm-2.4.54-1.fc20.x86_64
systemd-208-21.fc20.x86_64
xorg-x11-server-Xorg-1.14.4-11.fc20.x86_64

How reproducible:
(unfortunately) reasonably often, but I can't say whether it is this exact problem or some other; I saw the kernel panic printed on the screen for the first time ever

Steps to Reproduce:
1. suspend to ram
2. resume
3. frozen pc

Comment 1 Justin M. Forbes 2014-11-13 15:55: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 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.

Comment 2 Justin M. Forbes 2014-12-10 14:57:11 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.