| 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
| ||
|
Message-ID: <m3d4yuczqw.fsf@maximus.localdomain> Date: Sun, 15 Jul 2007 01:49:27 +0200 From: Krzysztof Halasa <khc@...waw.pl> To: William Montgomery <william@...nicus.com> Cc: linux-kernel@...r.kernel.org Subject: Re: e100 PCI bridge problem William Montgomery <william@...nicus.com> writes: > I am using a PCI analyzer and it shows the bus in an idle state after > the lockup. The PCI transactions just prior to the lockup show a > couple of interrupts from the card which appear to be handled > correctly. Anything I should be looking for in particular? I'd try to check with other machine using "secondary" bus slot. BTW: Are you able to analyze the "primary" bus transactions while using the card in "secondary" bus? Perhaps there is something wrong in front of the motherboard bridge? A broken motherboard may be hard to diagnose, unfortunately. Can you post something like "lspci -vv" taken on both machines? -- Krzysztof Halasa - 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