linux-kernel - Re: e100 PCI bridge problem

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]

Date:	Sat, 14 Jul 2007 21:27:11 -0400
From:	William Montgomery <william@...nicus.com>
To:	Krzysztof Halasa <khc@...waw.pl>
CC:	linux-kernel@...r.kernel.org
Subject: Re: e100 PCI bridge problem

Krzysztof Halasa wrote:

>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?
>  
>
I will post more info on Monday when I am able to power them up.

I'm not so sure the motherboard is broken, I am leaning more towards a 
misconfigured
bridge.  This computer is a 4U 19 inch rackmount chassis with a PCMIG 
CPU and a 12 slot PCI backplane.  I have done a lot of testing with this 
box trying to characterize this problem.  In one case I have put 3 Intel 
PRO 100S NICs on the secondary PCI bus and they ran under heavy stress 
test loads overnight.  The 4 port NIC seems to be the only card that 
doesnt want to cooperate.
-
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/