From: Patrick Richard <patr@axion.net>
To: linux-kernel@vger.kernel.org
Subject: e1000 only works in 2.6.3 with UP kernel ?
Date: Wed, 25 Feb 2004 10:09:40 -0800 [thread overview]
Message-ID: <403CE4E4.9010608@axion.net> (raw)
Hi,
I have been struggling to get the e1000 driver working _at all_ in
2.6.3. It works fine under 2.4.xx (same machine). This is all on an ASUS
P4C800-E deluxe, using onboard e1000 and P4 with HT enabled.
I have tried with / without apic, ACPI (boot option and compiled in),
SCSI, libata. Depending on what I have configured in the kernel, it will
stop at various places, for example, sometimes we will get a solid
lockup when running ifconfig (with ACPI and apic enabled), whereas
elsewhere, (no ACPI compiled in, i.e. not just disabled on boot args) it
will lock not on ifconfig, but will on first attempy to use the card
(i.e. ping thyself).
Anyhow, the *only* configuration I have managed to get working is on a
UP-built kernel, built with SMP disabled. Despite having an affect on
where it would lock up in the SMP kernel, it seemed to not matter if
APIC or ACPI or libata etc. was enabled or not in the UP kernel. If I
disabled the SMP at boot with bootargs, it still didn't work.
Is anyone else seeing similar problems ? Seems like an interrupt/ACPI
type of thing to me based on what is affecting it but what do I know.
Does anyone have this working on an SMP kernel/machine with this
motherboard ? Is this a mis-config on my part ? Like I said it works
fine in 2.4 and in UP kernel.
-Pat
next reply other threads:[~2004-02-25 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 18:09 Patrick Richard [this message]
2004-02-25 18:30 ` e1000 only works in 2.6.3 with UP kernel ? Martin Josefsson
2004-02-25 19:36 ` Patrick Richard
2004-02-25 23:06 ` Jeff Garzik
2004-02-26 3:51 ` Patrick Richard
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=403CE4E4.9010608@axion.net \
--to=patr@axion.net \
--cc=linux-kernel@vger.kernel.org \
/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