From: Willy TARREAU <w@w.ods.org>
To: Joe Korty <joe.korty@ccur.com>
Cc: cramerj@intel.com, scott.feldman@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] e1000 fails on 2.4.26+bk with CONFIG_SMP=y
Date: Mon, 19 Apr 2004 23:54:50 +0200 [thread overview]
Message-ID: <20040419215450.GA331@pcw.home.local> (raw)
In-Reply-To: <20040419214247.GA5273@tsunami.ccur.com>
On Mon, Apr 19, 2004 at 05:42:47PM -0400, Joe Korty wrote:
> On Mon, Apr 19, 2004 at 09:39:30PM +0200, Willy Tarreau wrote:
> > On Mon, Apr 19, 2004 at 12:54:25PM -0400, Joe Korty wrote:
> >>
> >> Uniprocessor 2.4.26 works fine.
> >> Uniprocessor 2.4.26 + local apic works fine.
> >> Uniprocessor 2.4.26 + local apic + io apic fails.
> >
> > interesting. Unfortunately, I didn't have time to try on the machine I told
> > you about last day. But right here, I have a dual athlon communicating
> > with an alpha, both with e1000 (544) in 2.4.26. Since there's a PCI
> > bridge on your quad, I wonder if the IOAPIC doesn't trigger an interrupt
> > routing problem with bridges. Are all the ports unusable or do some of
> > them work reliably in APIC mode ?
>
> I just verified that the Quad Ethernet board works with 2.6.5 SMP, so it
> is unlikely to be a bridge or other hardware problem.
Sorry that was not what I meant. I meant that the 2.4.26 irq routing or
I don't know what might experience difficulties due to the presence of
a PCI bridge on this board, and potentially this one particularly. I once
encountered such a problem in a desktop machine which would only see 3 out
of the 4 ports on an adaptec quad board, depending on the PCI slot it was
fit in ! It turned out to be a problem with region alignment or something
like this which was not correctly forwarded through the bridge (bios bug
or so at initialization).
> For 2.4.26, the Dell 650 has an Intel 82545EM Gigabit Ethernet Controller
> soldered in, which also uses the e1000 driver, and that works fine, so
> we know the 2.4.26 e1000 driver works with some of these Intel chips.
OK, same here.
> When the Quad board works, it negotiates down to 10 MBits/sec Half Duplex.
> Not sure yet if this is what it is supposed to be doing in our environment.
I remember something like this not long ago. It was what ethtool reported, but
the card was running either gigabit or a forced 100FDX without auto-neg on the
other side, I don't remember. Can you try a simple 4-pairs cable between two
ports on the quad to check what media is negociated ?
Also, can you cat /proc/interrupts with and without io/apic, and try without
ACPI as Zwane suggested ?
Cheers,
Willy
next prev parent reply other threads:[~2004-04-19 21:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 22:44 [BUG] e1000 fails on 2.4.26+bk with CONFIG_SMP=y Joe Korty
2004-04-17 7:24 ` Willy Tarreau
2004-04-17 8:02 ` Willy Tarreau
2004-04-19 16:54 ` Joe Korty
2004-04-19 19:39 ` Willy Tarreau
2004-04-19 20:16 ` Zwane Mwaikambo
2004-04-19 22:04 ` Joe Korty
2004-04-19 21:42 ` Joe Korty
2004-04-19 21:54 ` Willy TARREAU [this message]
2004-04-19 22:03 ` Chris Croswhite
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=20040419215450.GA331@pcw.home.local \
--to=w@w.ods.org \
--cc=cramerj@intel.com \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@intel.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