Bug 546264

Summary: KMS:RV610:HD2400 GPU lockup
Product: [Fedora] Fedora Reporter: Ilkka Tengvall <ikke>
Component: xorg-x11-drv-atiAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: jglisse, mcepl, milan.kerslager, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-03 17:51:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
lspci output
none
radeon bug log
none
dmesg from the system none

Description Ilkka Tengvall 2009-12-10 15:06:42 UTC
Created attachment 377474 [details]
lspci output

Description of problem:

X is stuck, no access even to virtual console via keyboard. Screen looks ok (not blank), but is totally stuck.

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

kernel:
------------------------
# uname -a
Linux whipper.mobile.fp.nsn-rdnet.net 2.6.31.6-162.fc12.x86_64 #1 SMP Fri Dec 4 00:06:26 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
------------------------

xorg:
------------------------
xorg-x11-drv-apm-1.2.2-1.fc12.x86_64
xorg-x11-drv-sis-0.10.2-1.fc12.x86_64
xorg-x11-drv-rendition-4.2.2-4.fc12.x86_64
xorg-x11-drv-voodoo-1.2.3-1.fc12.x86_64
xorg-x11-drv-glint-1.2.4-1.fc12.x86_64
xorg-x11-drv-mach64-6.8.2-1.fc12.x86_64
xorg-x11-drv-void-1.3.0-2.fc12.x86_64
xorg-x11-drv-nv-2.1.15-2.fc12.x86_64
xorg-x11-drv-vmmouse-12.6.5-2.fc12.x86_64
xorg-x11-utils-7.4-7.fc12.x86_64
xorg-x11-drv-vesa-2.2.1-1.fc12.x86_64
xorg-x11-proto-devel-7.4-34.fc12.noarch
xorg-x11-xauth-1.0.2-7.fc12.x86_64
xorg-x11-drv-r128-6.8.1-2.fc12.x86_64
xorg-x11-drv-cirrus-1.3.2-1.fc12.x86_64
xorg-x11-drv-v4l-0.2.0-3.fc12.1.x86_64
xorg-x11-drv-nouveau-0.0.15-17.20091105gite1c2efd.fc12.x86_64
xorg-x11-drv-dummy-0.3.3-1.fc12.x86_64
xorg-x11-drv-mouse-1.4.99.1-2.fc12.x86_64
xorg-x11-xinit-1.0.9-13.fc12.x86_64
xorg-x11-server-Xorg-1.7.1-7.fc12.x86_64
xorg-x11-drv-mga-1.4.11-1.fc12.x86_64
xorg-x11-drv-trident-1.3.3-1.fc12.x86_64
xorg-x11-drv-hyperpen-1.3.0-3.fc12.x86_64
xorg-x11-drv-ast-0.89.9-1.fc12.x86_64
xorg-x11-drv-ati-6.13.0-0.11.20091119git437113124.fc12.x86_64
xorg-x11-drv-evdev-2.3.1-2.fc12.x86_64
xorg-x11-font-utils-7.2-10.fc12.x86_64
xorg-x11-drv-acecad-1.4.0-1.fc12.x86_64
xorg-x11-xtrans-devel-1.2.2-4.fc12.noarch
xorg-x11-drv-elographics-1.2.3-4.fc12.x86_64
xorg-x11-drv-i128-1.3.3-1.fc12.x86_64
xorg-x11-drv-savage-2.3.1-1.fc12.x86_64
xorg-x11-drv-intel-2.9.1-1.fc12.x86_64
xorg-x11-drv-sisusb-0.9.3-1.fc12.x86_64
xorg-x11-drv-mutouch-1.2.1-4.fc12.x86_64
xorg-x11-drv-fbdev-0.4.1-1.fc12.x86_64
xorg-x11-drv-i740-1.3.2-1.fc12.x86_64
xorg-x11-drivers-7.3-13.fc12.x86_64
xorg-x11-fonts-misc-7.2-9.fc12.noarch
xorg-x11-drv-synaptics-1.2.0-2.fc12.x86_64
xorg-x11-drv-openchrome-0.2.904-1.fc12.x86_64
xorg-x11-drv-penmount-1.4.0-4.fc12.x86_64
xorg-x11-drv-fpit-1.3.0-4.fc12.x86_64
xorg-x11-drv-keyboard-1.4.0-2.fc12.x86_64
xorg-x11-server-common-1.7.1-7.fc12.x86_64
xorg-x11-drv-s3virge-1.10.4-1.fc12.x86_64
xorg-x11-drv-aiptek-1.3.0-1.fc12.x86_64
xorg-x11-drv-siliconmotion-1.7.3-1.fc12.x86_64
xorg-x11-drv-vmware-10.16.7-2.fc12.x86_64
xorg-x11-server-utils-7.4-13.fc12.x86_64
xorg-x11-drv-tdfx-1.4.3-1.fc12.x86_64
xorg-x11-xkb-utils-7.4-6.fc12.x86_64
------------------------


How reproducible:

Second time within a day, no clear path how to get there.

Steps to Reproduce:
1. Compiz is on (with the experimental driver)
2. this time I was moving from desktop to another, not doing anything special I could remember.
3. Not really reproceable.
  
Actual results:

Screen got stuck. Yesterday the whole kernel got stuck after pressing ctrl-alt-F2 to enter vt2. This time it does not take the keyboard input.

Expected results:

not to get stuck....

Additional info:

See the Xorg.log as attached.

Comment 1 Ilkka Tengvall 2009-12-10 15:07:31 UTC
Created attachment 377475 [details]
radeon bug log

Comment 2 Ilkka Tengvall 2009-12-10 15:10:25 UTC
Created attachment 377476 [details]
dmesg from the system

Comment 3 Ilkka Tengvall 2009-12-10 15:11:22 UTC
Is this bug similar https://bugzilla.redhat.com/show_bug.cgi?id=465884

Comment 4 Milan Kerslager 2010-02-02 18:45:18 UTC
Seems to be similar to bug #557805.

Comment 5 Matěj Cepl 2010-02-03 17:51:43 UTC
(In reply to comment #4)
> Seems to be similar to bug #557805.

Closing this one, the other bug has more information.

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