* debugging a deadlock
@ 2006-09-08 7:36 Janne Karhunen
0 siblings, 0 replies; only message in thread
From: Janne Karhunen @ 2006-09-08 7:36 UTC (permalink / raw)
To: linux-kernel
Hi,
Sometimes you have to do strange things such as trying to debug occasional
deadlock of a system that has been in use for long, long time. So please, no
nasty comments about outdated system with no soft lock-up detection and
such :/
Anyhoo, it appears to be infinite semaphore wait. By modifying the semaphores
to dump stack on LONG wait I managed to get a stack trace. Looks like this:
kernel: [printk+340/384] [printk+340/384] [show_trace+203/240]
[show_trace+203/240] [show_stack+113/120] [show_registers+223/324]
kernel: [__down+147/276] [__down_failed+8/12]
[stext_lock+13538/52069] [error_code+16/64] [system_call+66/76]
Umm, this error_code thing is beyond my current knowledge. What's this?
Some sort of assembly-glued exception handling? Any ideas how to figure
out which semaphore this is?
--
// Janne
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-09-08 7:36 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-09-08 7:36 debugging a deadlock Janne Karhunen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®