Bug 468975 - System hanging on (II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware.
Summary: System hanging on (II) RADEON(0): [RESUME] Attempting to re-init Radeon hardw...
Keywords:
Status: CLOSED DUPLICATE of bug 471338
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Airlie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-29 10:23 UTC by Mads Kiilerich
Modified: 2008-11-13 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-11-13 22:07:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
X log from the session (137.75 KB, text/plain)
2008-10-29 10:23 UTC, Mads Kiilerich
no flags Details
dmesg (from another session) (39.54 KB, text/plain)
2008-10-29 10:24 UTC, Mads Kiilerich
no flags Details

Description Mads Kiilerich 2008-10-29 10:23:23 UTC
Created attachment 321775 [details]
X log from the session

Description of problem:

From X I switched to a text tty, and when I switched back the system hang with
(II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware.

Nothing relevant in /var/log/messages or .xsession-errors.

I was trying to reproduce Bug 468393 and had logged in and out from X a couple of times. Compiz was enabled, and I had been running glxgears. 

01:00.0 VGA compatible controller: ATI Technologies Inc RV516 [Radeon X1300/X1550 Series]
01:00.1 Display controller: ATI Technologies Inc RV516 [Radeon X1300 Pro] (Secondary)

No xorg.conf


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

kernel-2.6.27.4-58.fc10.i686
mesa-dri-drivers-7.2-0.13.fc10.i386
xorg-x11-drv-ati-6.9.0-34.fc10.i386
compiz-0.7.6-17.fc10.i386

Comment 1 Mads Kiilerich 2008-10-29 10:24:32 UTC
Created attachment 321776 [details]
dmesg (from another session)

Comment 2 Mads Kiilerich 2008-11-13 22:07:52 UTC
marking as duplicate of bug 471338 based on mcepls comment there

*** This bug has been marked as a duplicate of bug 471338 ***


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