From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
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: Fri, 17 Nov 2006 14:43:36 +0100 [thread overview]
Message-ID: <455DBC88.6040701@s5r6.in-berlin.de> (raw)
In-Reply-To: <20061116223721.GS8236@csclub.uwaterloo.ca>
Lennart Sorensen wrote:
> On Thu, Nov 16, 2006 at 04:01:03PM -0600, Protasevich, Natalie wrote:
>> There are some port 80 cards that you can buy:
...
> Hmm, one of those on the PCI bus might work. Or perhaps the parallel
> port will. Of course if the problem is that somehow the PCI bus is
> locked up, then I won't get a message anywhere since all the busses are
> connected via PCI it seems. I don't know if a PCI bus can lock up, but
> for now I was assuming anything was possible.
If the PCI bus itself isn't brought down, you could debug from remote
using Benjamin Herrenschmidt's Firescope on the remote node and a
FireWire card in the test machine. Once the ohci1394 driver was loaded,
the FireWire controller is able to read and write to the 32bit PCI
address range (and thus to system memory) without assistance of
interrupt handlers.
--
Stefan Richter
-=====-=-==- =-== =---=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2006-11-17 13:43 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 [this message]
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
-- 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=455DBC88.6040701@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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