From: William Montgomery <william@opinicus.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: e100 PCI bridge problem
Date: Sat, 14 Jul 2007 21:27:11 -0400 [thread overview]
Message-ID: <469977EF.7050709@opinicus.com> (raw)
In-Reply-To: <m3d4yuczqw.fsf@maximus.localdomain>
Krzysztof Halasa wrote:
>William Montgomery <william@opinicus.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.
next prev parent reply other threads:[~2007-07-15 1:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 17:37 e100 PCI bridge problem William Montgomery
2007-07-13 20:36 ` Kok, Auke
2007-07-13 22:30 ` William Montgomery
2007-07-13 22:41 ` Kok, Auke
2007-07-14 0:54 ` William Montgomery
2007-07-14 14:43 ` Krzysztof Halasa
2007-07-14 23:17 ` William Montgomery
2007-07-14 23:49 ` Krzysztof Halasa
2007-07-15 1:27 ` William Montgomery [this message]
2007-07-17 18:29 ` William Montgomery
2007-07-17 18:55 ` Kok, Auke
2007-07-17 19:37 ` William Montgomery
2007-07-17 21:04 ` Krzysztof Halasa
2007-07-17 20:54 ` Krzysztof Halasa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=469977EF.7050709@opinicus.com \
--to=william@opinicus.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.