Description of problem: lenovo t60, ati X1400 the screen is garbled after resume, log overflows with errors Version-Release number of selected component (if applicable): xorg-x11-drv-ati-6.13.0-0.3.20090908git651fe5a47.fc12-x86_64 How reproducible: Steps to Reproduce: 1. suspend 2. resume Actual results: screen garbled, constantly repeating error logs: Sep 9 21:16:47 stinkpad kernel: [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(4). Sep 9 21:16:47 stinkpad kernel: [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! Sep 9 21:16:47 stinkpad kernel: [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(4). Sep 9 21:16:47 stinkpad kernel: [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB ! Expected results: duh Additional info: smolt hw uuid 71799f21-8222-4257-a472-d67c3727584d
with xorg-x11-drv-ati.x86_64 6.13.0-0.4.20090908git651fe5a47.fc12 the machine does not reach suspend state anymore. the sleep led keeps blinking indicating the machine does not sleep yet. the screen is turned off though.
when I set the nomodeset option on the kernel command line in grub then suspend/resume works correctly. clearly KMS messes up suspend/resume
still true for xorg-x11-drv-ati.x86_64 6.13.0-0.7.20091006git457646d73.fc12 kernel.x86_64 2.6.31.1-56.fc12 must say that suspend resume now works with KMS. previously I had to set nomodeset on the kernel commandline to make suspend resume work
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
here they come: - there is no xorg.conf (default install) - other 2 files are attached as pre suspend and post suspend variants, the post suspend variant is what is _extra_ in the file after resume (with the garbled screen) - I analysed the dmesg file a bit and found a clear radeon error and a suspicious pci message: pci (this one comes before the radeon error): pciehp 0000:00:1c.0:pcie04: Device 0000:02:00.0 already exists at 0000:02:00, cannot hot-add pciehp 0000:00:1c.0:pcie04: Cannot add device at 0000:02:00 radeon: [drm:r100_ring_test] *ERROR* radeon: ring test failed (sracth(0x15E4)=0xCAFEDEAD) [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22).
Created attachment 364620 [details] dmesg.pre.suspend
Created attachment 364621 [details] dmesg.post.suspend
Created attachment 364622 [details] Xorg.0.log.pre.suspend
Created attachment 364624 [details] Xorg.0.log.post.suspend
Created attachment 364625 [details] lspci -v
the messages in the log are gone now, machine reaches suspend state, and can also resume, but the screen stays black. we're nearly there :-) xorg-x11-drv-ati.x86_64 6.13.0-0.10.20091006git457646d73.fc12 kernel.x86_64 2.6.31.5-96.fc12
Created attachment 366501 [details] messages for suspend/resume cycle these are the system log messages for a suspend/resume cycle. as far as i can see there are no messages for the resume part of the cycle. when I use nomodeset suspend/resume does work.
Duplicate of 527874 *** This bug has been marked as a duplicate of bug 527874 ***