linux-kernel - Re: How to go about debuging a system lockup?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061117224403.GE8238@csclub.uwaterloo.ca>
Date:	Fri, 17 Nov 2006 17:44:03 -0500
From:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	"Protasevich, Natalie" <Natalie.Protasevich@...SYS.com>,
	Jesper Juhl <jesper.juhl@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: How to go about debuging a system lockup?

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/