From: Krzysztof Halasa <khc@pm.waw.pl>
To: William Montgomery <william@opinicus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: e100 PCI bridge problem
Date: Sun, 15 Jul 2007 01:49:27 +0200 [thread overview]
Message-ID: <m3d4yuczqw.fsf@maximus.localdomain> (raw)
In-Reply-To: <46995998.70706@opinicus.com> (William Montgomery's message of "Sat, 14 Jul 2007 19:17:44 -0400")
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?
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-07-14 23:49 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 [this message]
2007-07-15 1:27 ` William Montgomery
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=m3d4yuczqw.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=william@opinicus.com \
/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.