From: Joe Korty <joe.korty@ccur.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Willy Tarreau <w@w.ods.org>,
cramerj@intel.com, scott.feldman@intel.com,
linux-kernel@vger.kernel.org, csc@cadence.com
Subject: Re: [BUG] e1000 fails on 2.4.26+bk with CONFIG_SMP=y
Date: Mon, 19 Apr 2004 18:04:37 -0400 [thread overview]
Message-ID: <20040419220437.GA5817@tsunami.ccur.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0404191615560.2252@montezuma.fsmlabs.com>
On Mon, Apr 19, 2004 at 04:16:58PM -0400, Zwane Mwaikambo wrote:
> On Mon, 19 Apr 2004, Willy Tarreau wrote:
>
> > Hi Joe,
> >
> > 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 ?
>
> Joe could you also try it without ACPI if possible.
That was it. Actually I had CONFIG_ACPI off (unknown reasons, inherited
.config), when I turned it on the board started to work.
Thanks everyone for all the input.
Joe
next prev parent reply other threads:[~2004-04-19 22:04 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 [this message]
2004-04-19 21:42 ` Joe Korty
2004-04-19 21:54 ` Willy TARREAU
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=20040419220437.GA5817@tsunami.ccur.com \
--to=joe.korty@ccur.com \
--cc=cramerj@intel.com \
--cc=csc@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@intel.com \
--cc=w@w.ods.org \
--cc=zwane@linuxpower.ca \
/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