Bug 975073 - kernel BUG at include/drm/drm_mm.h:100
kernel BUG at include/drm/drm_mm.h:100
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: X/OpenGL Maintenance List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-06-17 10:48 EDT by Nathan Lynch
Modified: 2014-02-05 16:51 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-02-05 16:51:09 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
3.9.5-201 dmesg (177.30 KB, text/plain)
2013-06-17 10:48 EDT, Nathan Lynch
no flags Details
lspci output (25.15 KB, text/plain)
2013-06-17 10:50 EDT, Nathan Lynch
no flags Details

  None (edit)
Description Nathan Lynch 2013-06-17 10:48:51 EDT
Created attachment 762062 [details]
3.9.5-201 dmesg

Description of problem:

After updating kernel from 3.9.4-200.fc18.x86_64 to 3.9.5-201.fc18.x86_64, gnome shell goes unresponsive after login and console switching (ctrl-alt-f2) does not work.  Kernel appears to have hit an assertion in DRM (dmesg attached).  Additonally, soft lockup messages appear afterward.  Video card is a Radeon X1650 with dual displays.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Update kernel on F18 system to 3.9.5-201.fc18.x86_64
2. Reboot, log in to gnome shell default mode

Actual results:
Display locks up, unresponsive

Expected results:
Display doesn't lock up.

Additional info:
Booting 3.9.4-200.fc18.x86_64 works around the issue.
Comment 1 Nathan Lynch 2013-06-17 10:50:19 EDT
Created attachment 762063 [details]
lspci output

Attaching lspci output.
Comment 2 Nathan Lynch 2013-06-25 10:39:29 EDT
Update: this intermittently occurs with 3.9.4-200, so it was not introduced with 3.9.5-201 as initially reported.
Comment 3 Jaroslav Pulchart 2013-06-29 14:22:52 EDT
I experienced this issue with upgrade from mesa 9.0 to 9.2 (#969679)
Comment 4 Jaroslav Pulchart 2013-06-29 16:02:06 EDT
Setting GTT memory size to 1024GB by "radeon.gartsize=1024" parameter in kernel cmd line helped for me.
Comment 5 Alexandre Franke 2013-07-19 04:26:11 EDT
Duplicate of bug 967282.
Comment 6 Fedora End Of Life 2013-12-21 09:02:30 EST
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.
Comment 7 Fedora End Of Life 2014-02-05 16:51:09 EST
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.

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