Created attachment 18588 [details] gdb full bt Lockup using EXA. Attached gdb backtrace reveals in-kernel lockup performing a DRM_RADEON_CP_IDLE ioctl due to EXA accelerated composite activity. Kernel log is spammed with: [drm] wait idle failed status : 0x80010140 0x00000000 hardware is a r300 (Mobility radeon X600 SE PCIE) I am using compiz. drm, xorg and DDX driver are of today (30 aug 08) git checkout.
does ati git master help?
I also encountered this one with git master (commit 19b4f5f9b647cd470616b8ec1d34f1e4afa357ad ) on my RV610. It occured while the machine was idle over the weekend. As I came back in the morning today the displays wouldn't come back and keyboard and mouse ssemed to be dead and I had to hard-reset the machine. I'm not using KMS and am still on Ubuntu 9.04 Jaunty. The Xorg.0.log says nothing about a problem and /var/log/messages is flooded with messages like: [418028.635578] [drm] wait idle failed status : 0xA0003030 0x00000003 [418028.830394] [drm] wait idle failed status : 0xA0003030 0x00000003 [418029.023992] [drm] wait idle failed status : 0xA0003030 0x00000003 [418029.214830] [drm] wait idle failed status : 0xA0003030 0x00000003 [418029.404961] [drm] wait idle failed status : 0xA0003030 0x00000003 [418029.595129] [drm] wait idle failed status : 0xA0003030 0x00000003 [418029.785338] [drm] wait idle failed status : 0xA0003030 0x00000003 [418029.979013] [drm] wait idle failed status : 0xA0003030 0x00000003 [418030.176744] [drm] wait idle failed status : 0xA0003030 0x00000003 [418030.367609] [drm] wait idle failed status : 0xA0003030 0x00000003 [418030.557658] [drm] wait idle failed status : 0xA0003030 0x00000003 [418030.747621] [drm] wait idle failed status : 0xA0003030 0x00000003 [418030.937626] [drm] wait idle failed status : 0xA0003030 0x00000003 [418031.128979] [drm] wait idle failed status : 0xA0003030 0x00000003 [418031.321450] [drm] wait idle failed status : 0xA0003030 0x00000003 [418031.512827] [drm] wait idle failed status : 0xA0003030 0x00000003 [418031.702925] [drm] wait idle failed status : 0xA0003030 0x00000003 [418031.892934] [drm] wait idle failed status : 0xA0003030 0x00000003 The machine was last booted on wednesday, Oct 28th 2009 at 11:28:41 AM and the first of those messages occured on monday, Nov 2nd 2009 at 08:09:10 AM and continues in the same speed until I did the hard reset. Well, it tried to come back from the idle as I see some devices getting registered again: [428749.444026] usb 2-6: new high speed USB device using ehci_hcd and address 15 ... [428750.172242] usb 2-6: configuration #1 chosen from 1 choice [428750.172417] hub 2-6:1.0: USB hub found ... [428750.354482] hub 2-6:1.0: 3 ports detected ... [428751.028055] usb 2-6.1: new high speed USB device using ehci_hcd and addre... [428751.124372] usb 2-6.1: configuration #1 chosen from 1 choice ... [428751.130129] hub 2-6.1:1.0: USB hub found [428751.130178] hub 2-6.1:1.0: 3 ports detected [428751.216054] usb 2-6.2: new low speed USB device using ehci_hcd and addres... ... [428751.329249] usb 2-6.2: configuration #1 chosen from 1 choice [428751.335219] input: Dell Premium USB Optical Mouse as /devices/pci0000:00 ... ... [428752.096371] generic-usb 0003:413C:3016.0005: input,hidraw1: USB HID v11.1... ... [428752.282192] usb 2-6.1.1: new high speed USB device using ehci_hcd and add... ... [428753.508378] usb 2-6.1.1: configuration #1 chosen from 1 choice ... [428753.624383] scsi7 : SCSI emulation for USB Mass Storage devices ... I will attach my xorg.conf, Xorg.0.log, /var/log/messages and output of lspci -vvnn. Ancoron
Created attachment 30907 [details] /etc/X11/xorg.conf
Created attachment 30908 [details] /var/log/Xorg.0.log.old
Created attachment 30909 [details] /var/log/messages
Created attachment 30910 [details] The correct /var/log/messages (gzipped - orig size ~ 6 MiB)
Created attachment 30911 [details] Output of lspci -vvnn
Is this still an issue with KMS?
Sorry, I don't have that particular hardware anymore. I have two radeon machines: one RS780 and one Evergreen, and I haven't seen this bug on any of them. So the best is maybe to just close the bug for now.
(In reply to comment #9) > So the best is maybe to just close the bug for now. Doing that, thanks.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.