From: Grant Grundler <grundler@parisc-linux.org>
To: John Sigler <linux.kernel@free.fr>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: How to debug complete kernel lock-ups
Date: Wed, 24 Oct 2007 22:06:36 -0600 [thread overview]
Message-ID: <20071025040636.GA3608@colo.lackof.org> (raw)
In-Reply-To: <471F0DB4.1080709@free.fr>
On Wed, Oct 24, 2007 at 11:17:40AM +0200, John Sigler wrote:
...
> I've tested with a vanilla 2.6.22.10 kernel (no PREEMPT_RT patch).
> That system also locks up and remains completely unresponsive (I can't open
> new ssh sessions, the system won't answer ICMP echo requests).
>
> How do driver writers deal with complete kernel hangs?
Use different HW. Both IA64 and PARISC gives useful diagnostics
when the machine has a hard crash (MCA or HPMC respectively). I'll bet
PPC does too on the POWER machines.
Maybe a newer x86 machine can provide some MCE data as well?
Otherwise it's what gregkh said...not the "we slowly go crazy"
part. :) Well, sometimes. :)
BTW, getting PCI bus traces would be quite helpful in this case.
It'll give you clear data as to whether the devices are being programmed
as expected (also to rule out chipset/Host bus controller issues) and
whether they are responding as expected (maybe something else dies
when they do).
hth,
grant
hth,
grant
next prev parent reply other threads:[~2007-10-25 4:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 16:11 How to debug complete kernel lock-ups John Sigler
2007-10-24 9:17 ` John Sigler
2007-10-24 15:56 ` Greg KH
2007-10-24 16:19 ` Ray Lee
2007-10-25 4:06 ` Grant Grundler [this message]
2007-10-31 9:25 ` John Sigler
2007-10-31 21:28 ` Ray Lee
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=20071025040636.GA3608@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux.kernel@free.fr \
/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