Messages in this thread | | | Date | Mon, 20 Nov 2006 10:20:44 -0500 | Subject | Re: How to go about debuging a system lockup? | From | Lennart Sorensen <> |
| |
On Sat, Nov 18, 2006 at 12:09:54AM +0100, Stefan Richter wrote: > 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.
Sure seems that way. Makes me wonder if somehow a PCI transfer fails, and the PCI controller isn't aborting the transfer after a timeout (quite likely given the timeout timer is never enabled, and whenever I try to do so, it seems to hang the system). Time to start scoping the lines.
-- Len Sorensen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |