On Sat, Oct 06, 2007 at 10:14:06PM +0200, Ahmed S. Darwish wrote:
quoted text
> Pressing sysRq+T always produce an Oops for every running system task (94 
> Oopses, that's a record ;)).

uh-oh. For every sleeping task, I think.

quoted text
> The bug is 100% reproducable. Should I begin bisecting/investigating the 
> issue or it's a known problem ?

Start with some old kernel, like mmm.. 2.6.0. The fact that same behaviour
was present there may make you think about faulty assumptions you've
made.

quoted text
> [  226.309874] SysRq : Show State
> [  226.309948]   task                PC stack   pid father
> [  226.310105] init          S c1465b64     0     1      0
> [  226.310195]        c1465b54 00000082 00000286 c1465b64 c04255c0 c03c3ec0 00000000 00000286 
> [  226.310414]        c1465b64 fffd689a 0000000b 00000000 c02e8fda c1537040 00000292 c0425ab4 
> [  226.310664]        c0425ab4 fffd689a c0123cd0 c14634f0 c04255c0 00000800 c1465f9c c0176bf5 
> [  226.310914] Call Trace:
> [  226.310995]  [<c02e8fda>] schedule_timeout+0x4a/0xc0
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/