Hide Forgot
Created attachment 531613 [details] dmesg from when it failed Description of problem: The screen got turned off by power manager due to inactivity. When I came back, it did not respond after moving the mouse. Interesting pieces from dmesg: Nov 3 17:52:00 localhost kernel: [40929.118164] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec Nov 3 17:52:00 localhost kernel: [40929.118172] GPU lockup (waiting for 0x0001175F last fence id 0x0001175E) Nov 3 17:52:00 localhost kernel: [40929.119340] radeon 0000:01:00.0: GPU reset succeed Nov 3 17:52:00 localhost kernel: [40929.119351] radeon 0000:01:00.0: f2ef7800 unpin not necessary Nov 3 17:52:00 localhost kernel: [40929.127934] [drm] radeon: 1 quad pipes, 1 z pipes initialized. Nov 3 17:52:00 localhost kernel: [40929.130997] [drm] PCIE GART of 512M enabled (table at 0x00040000). Nov 3 17:52:00 localhost kernel: [40929.131044] radeon 0000:01:00.0: WB enabled Nov 3 17:52:00 localhost kernel: [40929.131116] [drm] radeon: ring at 0x0000000008001000 Nov 3 17:52:00 localhost kernel: [40929.801129] [drm:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD) Nov 3 17:52:00 localhost kernel: [40929.801138] [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22). Nov 3 17:52:00 localhost kernel: [40929.801145] radeon 0000:01:00.0: failed initializing CP (-22). ... Nov 3 17:52:16 localhost kernel: [40945.740688] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(2). Nov 3 17:52:16 localhost kernel: [40945.740696] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! At that point Xorg was definitely stuck, though the frambuffer (in the console) did work. I was running KDE, all bling bling disabled. Unfortunately I did not manage to grab contents of /sys/kernel/debug/dri/0/ Version-Release number of selected component (if applicable): kernel-3.1.0-0.rc10.git0.1.fc16.i686 mesa-dri-drivers-7.11-8.fc16.i686 mesa-dri-filesystem-7.11-8.fc16.i686 How reproducible: randomly (first time it happened) Steps to Reproduce: 1. uknown 2. 3. Actual results: Expected results: Additional info: smolt profile: http://www.smolts.org/client/show/pub_e280de94-21ab-4973-80c0-828bdf969de6
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.