From: Brian Horton <go_gators@mail.com>
To: Oliver Xymoron <oxymoron@waste.org>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: how to debug a deadlock'ed kernel?
Date: Fri, 14 Dec 2001 15:35:26 -0600 [thread overview]
Message-ID: <3C1A709E.943034DE@mail.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0112111822060.13893-100000@waste.org>
Yup, the nmi_watchdog option didn't work, but I was able to get
information I needed with kdb!
thx! .bri.
Oliver Xymoron wrote:
>
> On Tue, 11 Dec 2001, Brian Horton wrote:
>
> > Thanks, I'll try the nmi_watchdog option out. It appears to not be in
> > the 2.2.14 kernel, but is in a 2.2.19 kernel that I have from RedHat.
>
> It's there by default in SMP, you just have to enable it with
> nmiwatchdog=1 at boot (or something). I didn't mention it because it
> probably won't help your problem: as you can use the magic sysrq keys to
> reboot, you are not deadlocked with interrupts off, therefore the timer
> interrupt will keep the NMI watchdog from ever firing. NMI watchdog is
> mostly of use when you can't even get the capslock light to toggle..
>
> > > > 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...
>
> --
> "Love the dolphins," she advised him. "Write by W.A.S.T.E.."
prev parent reply other threads:[~2001-12-14 21:35 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
2001-12-11 23:41 ` Brian Horton
2001-12-12 0:25 ` Oliver Xymoron
2001-12-14 21:35 ` Brian Horton [this message]
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=3C1A709E.943034DE@mail.com \
--to=go_gators@mail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.