From: Scott Lee <scottlee@redhot.rose.hp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Debugging hard lockups (hardware?)
Date: Fri, 11 Apr 2003 11:08:16 -0700 (PDT) [thread overview]
Message-ID: <200304111808.LAA06725@redhot.rose.hp.com> (raw)
On Sunday, April 06, 2003 at 11:34 AM Alan Cox wrote:
> For the NMI watchdog to fail (if you have it enabled) requires pretty
> major disaster to have occurred since the NMI will be delivered through
> any kind of system hang
Has anyone ever thought about that fact that although the dog might bark (printk), klogd may be deaf in some cases? It seems to me that there will be cases where this happens and thus we see no data.
I don't know if all x86 hardware has this, but I know that the couple of systems I typically use have a small amount of battery backed ram that is available for use in the RTC. Anyone ever write a patch to dump data (small stack trace) to this memory so it can be retrieved after a reboot? It seems to me that some data is better than none... Of course it would be nice to know what the lowest common denominator is so that one patch will work with all PC hardware but I don't even know if a general approach is really feasible.
Regards,
Scott
next reply other threads:[~2003-04-11 17:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 18:08 Scott Lee [this message]
2003-04-11 19:22 ` Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2003-04-08 18:36 Scott Lee
2003-04-07 23:24 Richard J Moore
2003-04-09 1:24 ` Nick Urbanik
2003-04-06 10:12 mikpe
2003-04-06 16:01 ` Nick Urbanik
2003-04-06 6:32 Nick Urbanik
2003-04-06 6:39 ` Nick Urbanik
2003-04-06 9:27 ` John Bradford
2003-04-06 10:55 ` Bruce Harada
2003-04-06 18:34 ` Alan Cox
2003-04-06 20:29 ` Arador
2003-04-06 21:04 ` Alan Cox
2003-04-17 16:12 ` Arador
2003-04-06 20:31 ` Dave Jones
2003-04-06 22:02 ` Nick Urbanik
2003-04-06 23:15 ` Dave Jones
2003-04-08 3:33 ` Andre Hedrick
2003-04-08 12:35 ` Dave Jones
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=200304111808.LAA06725@redhot.rose.hp.com \
--to=scottlee@redhot.rose.hp.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
all inboxes | Powered by JetHome®