public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Fri, 17 Nov 2006 17:44:03 -0500	[thread overview]
Message-ID: <20061117224403.GE8238@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20061117142928.GT8236@csclub.uwaterloo.ca>

On Fri, Nov 17, 2006 at 09:29:28AM -0500, Lennart Sorensen wrote:
> Wow, that looks really neat.  I will have to go read up on that tool.

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.

--
Len Sorensen

  reply	other threads:[~2006-11-17 22:44 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 [this message]
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=20061117224403.GE8238@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