Bug 443834 - kernel BUG in :radeon:radeon_cp_init_ring_buffer on resume-from-ram
Summary: kernel BUG in :radeon:radeon_cp_init_ring_buffer on resume-from-ram
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dave Airlie
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F9Target
TreeView+ depends on / blocked
Reported: 2008-04-23 16:16 UTC by Hans Ulrich Niedermann
Modified: 2009-07-14 14:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 14:57:37 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/var/log/messages kernel-BUG-on-resume 2.6.25-8.fc9.i686.PAE (3.67 KB, text/plain)
2008-04-24 11:00 UTC, Hans Ulrich Niedermann
no flags Details

Description Hans Ulrich Niedermann 2008-04-23 16:16:25 UTC
Description of problem:

  Kernel BUG is triggered on resume-from-RAM after I played around with
  the Gnome user switch thingie before doing the suspend-to-RAM.

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


How reproducible:

  regularly, and I don't seem to be the only one:

Steps to Reproduce:
1. Take my ThinkPad T60 with ATI X1400 graphics chip
2. switch to different user
3. try to suspend, which will fail due to policymagic
4. switch back to first user
5. suspend (STR)
6. resume
Actual results:

  Xorg for first user killed due to oops. Other user still logged in.
  After logging in as first user, kerneloops applet pops up.

Expected results:

  No oops.

Additional info:

Comment 1 Hans Ulrich Niedermann 2008-04-23 16:19:40 UTC
Xorg is using driver "radeon". Package versions:


Comment 2 Dave Airlie 2008-04-24 03:38:33 UTC
can you test with the kernel-2.6.25-8.fc9 from koji 

or if it hits rawhide.

Comment 3 Hans Ulrich Niedermann 2008-04-24 10:00:09 UTC
kernel-PAE-2.6.25-8.fc9.i686 appears to have fixed the BUG/Oops.

Now some non-oopsy bug remains somewhere (kernel, Xorg, radeon driver)
preventing me from switching between users, but that needs a separate
investigation and probably a separate bz ticket.

Comment 4 Hans Ulrich Niedermann 2008-04-24 10:57:19 UTC
OK, I was wrong about that. One user-switch, then suspend/resume gives me the
BUG again. /var/log/messages attachment to follow.

Comment 5 Hans Ulrich Niedermann 2008-04-24 11:00:11 UTC
Created attachment 303611 [details]
/var/log/messages kernel-BUG-on-resume 2.6.25-8.fc9.i686.PAE

Excerpt from /var/log/messages with 2.6.26-8.fc9 kernel-PAE from koji.

Comment 6 Adam Jackson 2008-04-29 16:58:30 UTC
This also breaks fast user switching.  Any call to EnterVT, really.

Comment 7 Hans Ulrich Niedermann 2008-04-30 01:10:51 UTC
Fast user switching with the
xorg-x11-drv-radeonhd-1.2.1-1.1.20080429git.fc9.i386 driver and
kernel-PAE-2.6.25-8.fc9.i686 works.

This shows that the Gnome/Xorg-server/hal/... magic all work. The difference to
non-working is xorg-x11-drv-ati with kernel DRM vs xorg-x11-drv-radeonhd without

Comment 8 Dave Jones 2008-04-30 19:50:10 UTC
I just had someone show me another instance of this on .25-8, and he hadn't
resumed from ram, just a straight forward boot up.
Full trace available, but it looks very similar to the one in comment #5 modulo
some offsets.

Comment 9 Hans Ulrich Niedermann 2008-05-05 07:35:10 UTC
I have just tested kernel-PAE-2.6.25-14.fc9.i686 straight from bootup:

  1. Cold boot.
  2. gdm comes up
  3. Log in as $USER1
  4. Choose "Other..." on fast user switching applet
  5. Watch gdm come up
  6. Watch gdm assemble its list of users
  7. Watch as the mouse pointer stops reacting to movements.
     System appears completely frozen.
     (Sysrq emergency sync does not flicker HDD LED)

Time between 5 and 8 is betweeb 0 and 4 seconds (two tries).

Comment 10 Hans Ulrich Niedermann 2008-05-05 07:35:51 UTC
Forgot to mention for the record: xorg-x11-drv-ati-6.8.0-12.fc9.i386

Comment 11 Bug Zapper 2008-05-14 10:01:09 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:

Comment 12 Hans Ulrich Niedermann 2008-05-16 09:05:02 UTC
I have just tried the current F9 packages


Comment #9 still applies. A hard freeze happens, with no apparent way to get
crash information from the box.

Hardware is Lenovo ThinkPad T60, ATI X1400.

Comment 13 Hans Ulrich Niedermann 2008-06-20 21:20:18 UTC
Comment #9 and comment #12 (complete system freeze) confirmed with


Comment 14 Hans Ulrich Niedermann 2008-07-07 08:51:08 UTC
I have recently checked


and am still getting the total system freeze when using fast user switching.

Using xorg-x11-drv-radeonhd-1.2.1-3.3.20080630git.fc9.i386 now as workaround,
which works flawlessly in the FUS department, probably due to not doing anything
with DRI.

Comment 15 François Cami 2009-02-16 14:31:53 UTC
Could you test a fully updated F10 and report ?
Preferably both with and without nomodeset in the kernel command line.

Fedora Bugzappers volunteer triage team

Comment 16 Hans Ulrich Niedermann 2009-02-16 15:25:06 UTC
I installed F10 on this system (Lenovo ThinkPad T60 with M54 Mobile X1400 graphics) around 2009-02-01. I needed to boot with the nomodeset kernel parameter in order to make resume-from-RAM work, with whatever kernel and xorg-x11-drv-ati versions were current then.

I will check with an up to date F10 later today.

Comment 17 Hans Ulrich Niedermann 2009-02-16 16:10:44 UTC
I have just tested the following package versions in an updated
F10 installation:


I have examined the following four test cases:

  A) rhgb quiet
  B)     rhgb quiet
  C) nomodeset
  D)     nomodeset

The test procedure:

  1. boot given kernel with the given command line params
  2. wait until gdm comes up
  3. log into Gnome desktop as normal user
  4. suspend to ram clicking System -> Shut Down... -> [Suspend].
  5. wait until computer is suspended
  6. press Fn key to resume from RAM
  7. observe


  A) and B) result in vertical stripes on the display and sync problems.
  The only fix is a reboot which can be triggered by pressing Ctrl-Alt-Del.

  C) and D) resume without issue.

  None of the four test cases appear to produce kernel BUGs any more.
  Apparently, the really bad BUG has been fixed, but there are still
  bugs preventing resume-from-RAM with KMS.

Comment 18 Bug Zapper 2009-06-10 00:22:50 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 '9'.

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 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 

Comment 19 Bug Zapper 2009-07-14 14:57:37 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.

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.