From: george anzinger <george@mvista.com>
To: Brian Horton <go_gators@mail.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: how to debug a deadlock'ed kernel?
Date: Tue, 11 Dec 2001 13:41:44 -0800 [thread overview]
Message-ID: <3C167D98.90651C10@mvista.com> (raw)
In-Reply-To: <3C166540.DC0BDBEE@mail.com>
Brian Horton wrote:
>
> Anyone got any good tips on how to debug a SMP system that is locked up
> in a deadlock situation in the kernel? I'm working on a kernel module,
> and after some number of hours of stress testing, the box locks up. None
> of the sysrq options show anything on the display, though the reBoot
> option does reboot the system. RedHat 6.2 and its 2.2.14 kernel. Doesn't
> hang for me on 2.4, so I need to debug it here...
>
> Any hints?
First read about the NMI boot option in Documentation/nmi_watchdog.txt.
If you have this turned on and are not oopsing, then the timer (at
least) is interrupting. The next step I would take would be to used
either kdb (no experience) or kgdb. I have my own version of this if
you are interested. It does, however, require an RS232 (serial)
connection to a host machine.
I don't know about kdb, but kgdb (my version) uses the NMI to trap the
other cpus and also traps NMIs on the way to oopsing.
--
George george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Real time sched: http://sourceforge.net/projects/rtsched/
next prev parent reply other threads:[~2001-12-11 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 19:57 how to debug a deadlock'ed kernel? Brian Horton
2001-12-11 19:58 ` Bruce Harada
2001-12-11 21:15 ` Oliver Xymoron
2001-12-11 21:41 ` george anzinger [this message]
2001-12-11 23:41 ` Brian Horton
2001-12-12 0:25 ` Oliver Xymoron
2001-12-14 21:35 ` Brian Horton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C167D98.90651C10@mvista.com \
--to=george@mvista.com \
--cc=go_gators@mail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox