From: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>,
Jesper Juhl <jesper.juhl@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: How to go about debuging a system lockup?
Date: Mon, 20 Nov 2006 10:20:44 -0500 [thread overview]
Message-ID: <20061120152044.GX8236@csclub.uwaterloo.ca> (raw)
In-Reply-To: <455E4142.8090202@s5r6.in-berlin.de>
On Sat, Nov 18, 2006 at 12:09:54AM +0100, Stefan Richter wrote:
> Lennart Sorensen wrote:
> > OK, I have now tried connecting with firescope to just follow the dmesg
> > buffer across firewire. Works great, until the system hangs, then
> > firescope reports that it couldn't perform the read. I wonder what part
> > of the system has to lock up for the firewire card to no longer be able
> > to read memory on the system.
>
> I suppose the PCI bus is no longer accessible to the chip.
Sure seems that way. Makes me wonder if somehow a PCI transfer fails,
and the PCI controller isn't aborting the transfer after a timeout
(quite likely given the timeout timer is never enabled, and whenever I
try to do so, it seems to hang the system). Time to start scoping the
lines.
--
Len Sorensen
next prev parent reply other threads:[~2006-11-20 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 22:01 How to go about debuging a system lockup? Protasevich, Natalie
2006-11-16 22:37 ` Lennart Sorensen
2006-11-17 13:43 ` Stefan Richter
2006-11-17 14:29 ` Lennart Sorensen
2006-11-17 22:44 ` Lennart Sorensen
2006-11-17 23:09 ` Stefan Richter
2006-11-20 15:20 ` Lennart Sorensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-16 15:34 Lennart Sorensen
2006-11-16 20:49 ` Jesper Juhl
2006-11-16 21:21 ` Lennart Sorensen
2006-11-16 21:30 ` Jesper Juhl
2006-11-18 1:14 ` Krzysztof Halasa
2006-11-21 4:17 ` Keith Owens
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=20061120152044.GX8236@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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