public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: William Montgomery <william@opinicus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: e100 PCI bridge problem
Date: Fri, 13 Jul 2007 13:36:26 -0700	[thread overview]
Message-ID: <4697E24A.4030609@intel.com> (raw)
In-Reply-To: <4697B85B.4040902@opinicus.com>

William Montgomery wrote:
> In an earlier post to the list I described a hard lockup condition
> that occurs on linux kernels 2.4.22, 2.6.13, and 2.6.17 when using
> a 4 port 10/100 fast ethernet card.  The lockup is easily repeatable
> and occurs on 2 out of 3 computers.
> 
> Further testing has revealed that the lockup can be prevented on all
> computers by making sure the card is installed on the primary PCI bus.
> If the card is installed in a slot on the secondary PCI bus (behind a
> PCI to PCI bridge) the lockup occurs.

sounds like int-A/B/C/D routing issues

> Are there any PCI tuning registers that I can tweak to get around
> this problem?  Any changes I could make to the e100 driver to fix this?

this issue might be resolvable by quirking the bridgee chips and adjusting any 
APIC where needed. Unfortunately I don't know much about this but it's 
physically not possible from the e100 driver. The special (non-intel) card that 
has these 4 ports onboard contains a bridge chip itself which explains the 
issues. Even a BIOS issue could be the cause here.

Perhaps the linuxfirmwarekit will reveal more information. In any case, fixing 
this in software would be a gigantic effort.

Auke

  reply	other threads:[~2007-07-13 20:36 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 [this message]
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
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=4697E24A.4030609@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox