Most recent kernel where this bug did not occur: 2.6.16 Distribution: Debian Testing, Kernel from kernel.org Hardware Environment: Thinkpad X31 (ati radeon M6) Software Environment: xorg 7.022 as of debian testing Problem Description: After upgrade to kernel 2.6.17.3 the machine completely locks up, sysrq keys don't work, system was running X on each occurence. Time to freeze after startup may vary from ~ 10 to 30 minutes (approx.) Steps to reproduce: Just run 2.6.17.3 with X. Switching back to 2.6.16 resolves that problem.
Are you using DRI? If so does it make any different disabling it?
Yes, I did use DRI. I disabled it in xorg.conf and made sure that the radeon module wasn't loaded and up to now (*knock on wood*) it is still up and running. Although I cannot say for sure that it will stay so (could not foresee the exact moment of system freeze), I can already state that _without_ DRI, vertical scrolling in Firefox (dragging the vertical scroll bar up and down with the mouse) is a _lot_ faster. Without DRI it scrolls instantly while with DRI it tends to lag behind like being pulled with a rubber band. I guess that these are two independed issues, just wanted to mention, because I believe that on one of the freezes it happened while scrolling a page in Firefox.
I see something similar since 2.6.17, which enabled DRI on R300 cards. X locks up, and SysRq-T shows something like this... Xorg D 000000000f6a2538 9504 2770 2769 2824 (NOTLB) Call Trace: [C0000001140A7810] [C0000001140A78D0] 0xc0000001140a78d0 (unreliable) [C0000001140A79E0] [C00000000000F758] .__switch_to+0x12c/0x150 [C0000001140A7A70] [C00000000037AA44] .schedule+0xd20/0xe68 [C0000001140A7B80] [C00000000037999C] .__down+0x6c/0xf0 [C0000001140A7C40] [C00000000037DB08] .lock_kernel+0x7c/0xa8 [C0000001140A7CD0] [D00000000043989C] .radeon_compat_ioctl+0x64/0xfc [radeon] [C0000001140A7D70] [C00000000010FB60] .compat_sys_ioctl+0x158/0x3b8 [C0000001140A7E30] [C00000000000871C] syscall_exit+0x0/0x40
So SysRq keys still work for you? If my box freezes, I can neither switch to console nor use any of the SysRq keys (sync, reboot, ...).
On that occasion I was able to log in over the network and use /proc/sysrq-trigger
Any update on this bug please. Is the problem still there with recent kernel? Thanks.
Update: All running fine now. AFAIR it turned out not be a kernel but an xorg issue.
Thanks for the update. Closing the bug.