Re: DRI lockup on R200, 2.6.11.7

[Ryan Richter]

So I just got around to testing this today.  Using NO_TCL locks the
machine immediately:

[drm:drm_lock_take] *ERROR* 4 holds heavyweight lock

X isn't spinning the CPU, but the overall effect is the same.  When I
move the mouse it's doing:

ioctl(5, 0x4008642a, 0x7ffffffff448)    = ? ERESTARTSYS (To be restarted)
--- SIGIO (I/O possible) @ 0 (0) ---
select(7, [5 6], NULL, NULL, {0, 0})    = 1 (in [6], left {0, 0})
rt_sigprocmask(SIG_BLOCK, [IO], [IO], 8) = 0
read(6, "\10\3\4\0", 64)                = 4
rt_sigprocmask(SIG_BLOCK, [], [IO], 8)  = 0
select(1024, [6], NULL, NULL, {0, 0})   = 0 (Timeout)
rt_sigreturn(0x1)                       = -1 EINTR (Interrupted system call)
ioctl(5, 0x4008642a, 0x7ffffffff448)    = ? ERESTARTSYS (To be restarted)


Also, I tried to kill X using a sysrq-k and got:

SysRq : SAK
Badness in set_palette at drivers/char/vt.c:2918

Call Trace:<ffffffff8022391c>{set_palette+60} <ffffffff802244db>{__handle_sysrq+107} 
       <ffffffff80195bd5>{write_sysrq_trigger+53} <ffffffff80166510>{vfs_write+192} 
       <ffffffff80166663>{sys_write+83} <ffffffff8010d13a>{system_call+126} 

-ryan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/