Created attachment 377587 [details] System Info Description of problem: Kernel crashes during GUI interaction. System Ok without KMS but X is slow with one second stalls in operation when moving windows or changing desktops. Version-Release number of selected component (if applicable): System info is enclosed. How reproducible: Four times a day while using. Steps to Reproduce: 1. Use system 2. 3. Actual results: The kernel panic message is: Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Oops: 0002 [#1] SMP Message from syslogd@beam at Dec 9 13:02:22 ... kernel:last sysfs file: /sys/devices/system/cpu/cpu3/topology/core_siblings Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Process events/2 (pid: 17, ti=f70d0000 task=f70b72c0 task.ti=f70d0000) Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Stack: Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Call Trace: Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Code: ff 8d 65 f4 89 f8 5b 5e 5f 5d c3 55 89 e5 53 0f 1f 44 00 00 89 c3 8b 8b b0 00 00 00 8d 80 b0 00 00 00 8b 93 b4 00 00 00 89 51 04 <89> 0a 89 83 b0 00 00 00 89 83 b4 00 00 00 89 d8 e8 57 f5 ff ff Message from syslogd@beam at Dec 9 13:02:22 ... kernel:EIP: [<f7f6a0f9>] radeon_ttm_object_object_destroy+0x20/0x3f [radeon] SS:ESP 0068:f70d1f1c Message from syslogd@beam at Dec 9 13:02:22 ... kernel:CR2: 0000000000000000 Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Oops: 0002 [#2] SMP Message from syslogd@beam at Dec 9 13:02:22 ... kernel:last sysfs file: /sys/devices/system/cpu/cpu3/topology/core_siblings Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Process X (pid: 5555, ti=f64e4000 task=db451980 task.ti=f64e4000) Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Stack: Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Call Trace: Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Code: ff 8d 65 f4 89 f8 5b 5e 5f 5d c3 55 89 e5 53 0f 1f 44 00 00 89 c3 8b 8b b0 00 00 00 8d 80 b0 00 00 00 8b 93 b4 00 00 00 89 51 04 <89> 0a 89 83 b0 00 00 00 89 83 b4 00 00 00 89 d8 e8 57 f5 ff ff Message from syslogd@beam at Dec 9 13:02:22 ... kernel:EIP: [<f7f6a0f9>] radeon_ttm_object_object_destroy+0x20/0x3f [radeon] SS:ESP 0068:f64e5d90 Message from syslogd@beam at Dec 9 13:02:22 ... kernel:CR2: 0000000000000000 Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Oops: 0002 [#3] SMP Message from syslogd@beam at Dec 9 13:02:22 ... kernel:last sysfs file: /sys/devices/system/cpu/cpu3/topology/core_siblings Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Process X (pid: 5555, ti=f64e4000 task=db451980 task.ti=f64e4000) Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Stack: Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Call Trace: Message from syslogd@beam at Dec 9 13:02:22 ... kernel:Code: fe ff ff 5d c3 55 89 e5 0f 1f 44 00 00 ba 00 01 00 00 f0 66 0f c1 10 38 f2 74 06 f3 90 8a 10 eb f6 5d c3 55 89 e5 0f 1f 44 00 00 <f0> 81 28 00 00 00 01 74 05 e8 ed fd ff ff 5d c3 55 89 e5 0f 1f Message from syslogd@beam at Dec 9 13:02:22 ... kernel:EIP: [<c0778a99>] _write_lock+0x8/0x18 SS:ESP 0068:f64e5b78 Message from syslogd@beam at Dec 9 13:02:22 ... kernel:CR2: 0000000000000010 Read from remote host beam: Connection reset by peer Connection to beam closed. Expected results: Additional info:
Note this is an AGP graphics card in a dual Xeon system.
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), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
There is no /etc/X11/xorg.conf file (uses X-Server defaults). I have attached the X-Server log. The system has been much better since a kernel update to: 2.6.31.6-166.fc12.i686.PAE although it has still locked up once.
Created attachment 378986 [details] /var/log/Xorg.0.log
bo list issue. Fixed upstream but fix is pretty big and need other 2.6.33 changes. Dunno if we will backport. please attach full dmesg of session when this oops happen.
Please test: http://koji.fedoraproject.org/koji/buildinfo?buildID=150696 I should have the fix i am thinking about.
Ok, I will have a go. Won't be for a few days as the machine is at work and I am snow bound at home at the moment. Cheers.
*** This bug has been marked as a duplicate of bug 537981 ***
I have been using kernel 2.6.32.7-37.fc12.i686.PAE from updates-testing for 3 days now and have not had the problem. I consider it has been fixed. Cheers to all.