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: <455E4142.8090202@s5r6.in-berlin.de>
Date:	Sat, 18 Nov 2006 00:09:54 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>
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?

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.
-- 
Stefan Richter
-=====-=-==- =-== =--=-
http://arcgraph.de/sr/
-
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/