From: Jeff Garzik <jgarzik@pobox.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: Samuel Flory <sflory@rackable.com>, netdev@oss.sgi.com
Subject: Re: More 2.4.22pre10 ACPI breakage
Date: Tue, 05 Aug 2003 22:58:12 -0400 [thread overview]
Message-ID: <3F306EC4.1030109@pobox.com> (raw)
In-Reply-To: <C6F5CF431189FA4CBAEC9E7DD5441E01022292CD@orsmsx402.jf.intel.com>
Feldman, Scott wrote:
>> It appears that the intel Se7501BR mother is also having
>>issues with ACPI. When ACPI support is enable the e1000
>>controller stops working printing "<6>NETDEV WATCHDOG:
>>eth0: transmit timed out".
>
>
> Must...have...interrupts.
You are 100% correct.
That said... I'm tempted to extend NAPI just a bit, to provide an
"always poll" mode. It seems like all the bug reports I get these days
for 8139too are caused by x86 ACPI/APIC/irq routing troubles completely
unrelated to the driver. Tulip-almost-NAPI in 2.4 has an always-poll
mode, so I have a convenient excuse :)
Jeff
next parent reply other threads:[~2003-08-06 2:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C6F5CF431189FA4CBAEC9E7DD5441E01022292CD@orsmsx402.jf.intel.com>
2003-08-06 2:58 ` Jeff Garzik [this message]
2003-08-06 22:34 More 2.4.22pre10 ACPI breakage Feldman, Scott
2003-08-10 22:22 ` Robert Olsson
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=3F306EC4.1030109@pobox.com \
--to=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.com \
--cc=sflory@rackable.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;
as well as URLs for NNTP newsgroup(s).