Red Hat Bugzilla – Bug 495090
KMS freeze on suspend-to-disk/resume on Mobility Radeon X1300 [1002:7149]
Last modified: 2009-09-12 04:16:50 EDT
Created attachment 338962 [details]
X server logfile
Description of problem:
Latest kernel/driver breaks suspend-to-disk/resume with KMS. Either the machine freezes directly when suspend-to-disk is initiated or when resume tries to restart the tasks.
When the machine freezes the picture on the LCD looks like the CRTC is wrongly set up, e.g. you can see the vertical/horizontal blank periods. The picture parts don't show any content, just colors.
Version-Release number of selected component (if applicable):
Smolt profile attached as URL
As far as I can tell:
- KMS disabled: suspend-to-RAM/suspend-to-disk works perfectly
- KMS enabled: suspend-to-RAM works perfectly
An active WLAN connection (iwl3945) seems to be related to the freeze. Maybe this is an interrupts-not-disabled problem?
0: 153783 0 IO-APIC-edge timer
1: 198 0 IO-APIC-edge i8042
8: 13 0 IO-APIC-edge rtc0
9: 673 758 IO-APIC-fasteoi acpi
12: 2540 8291 IO-APIC-edge i8042
14: 6397 0 IO-APIC-edge ata_piix
15: 0 0 IO-APIC-edge ata_piix
16: 78476 0 IO-APIC-fasteoi uhci_hcd:usb2, radeon, yenta
17: 316 0 IO-APIC-fasteoi uhci_hcd:usb3, HDA Intel
18: 0 0 IO-APIC-fasteoi uhci_hcd:usb4
19: 28 0 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb5
29: 3168 6664 PCI-MSI-edge ahci
30: 4 351 PCI-MSI-edge eth0
31: 8168 0 PCI-MSI-edge iwl3945
NMI: 0 0 Non-maskable interrupts
LOC: 49660 116435 Local timer interrupts
RES: 16266 15656 Rescheduling interrupts
CAL: 47 79 Function call interrupts
TLB: 31 120 TLB shootdowns
TRM: 0 0 Thermal event interrupts
SPU: 0 0 Spurious interrupts
Created attachment 338963 [details]
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Fedora 12 Radeon Test Day: still no luck with KMS & suspend. Now tested also on the r6xx HW: HD3200 [1002:9610]
T60 does hibernate/resume when KMS is disabled.
See also bug #522070. Could be duplicate.
The story continues into F12.
I doubt this will ever be fixed for F11, because it still uses the old radeon code base.
*** This bug has been marked as a duplicate of bug 522070 ***