Re: [BUG] e1000 fails on 2.4.26+bk with CONFIG_SMP=y

From: Chris Croswhite
Date: Mon Apr 19 2004 - 16:59:04 EST


FYI, using the dual 85540 board w/e1000 works fine on a quad SMP w/APIC
support.

However, if I try to bond, I get immediate detonation.


On Mon, 2004-04-19 at 14:42, 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.
>
> 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.
>
> 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.
>
> Regards,
> Joe
>
> PS: do you CC'ed Intel guys have some insights or data for us?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/