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
| ||
|
Date: Fri, 17 Nov 2006 09:29:28 -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 02:43:36PM +0100, Stefan Richter wrote: > 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. Wow, that looks really neat. I will have to go read up on that tool. -- 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/
Powered by blists - more mailing lists