From: Phil Oester <kernel@linuxace.com>
To: Len Brown <len.brown@intel.com>
Cc: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ganesh.venkatesan@intel.com,
John Ronciak <john.ronciak@intel.com>
Subject: Re: Spurious interrupts when SCI shared with e100
Date: Tue, 9 Nov 2004 08:21:42 -0800 [thread overview]
Message-ID: <20041109162142.GA12926@linuxace.com> (raw)
In-Reply-To: <1099978966.6092.36.camel@d845pe>
On Tue, Nov 09, 2004 at 12:42:46AM -0500, Len Brown wrote:
> On Mon, 2004-11-08 at 05:59, Udo A. Steinberg wrote:
> > My laptop has IRQ9 configured as ACPI SCI. When IRQ9 is shared between
> > ACPI and e100 an IRQ9 storm occurs when e100 is enabled, as can be
> > seen in the dmesg output below.
>
> Is this new with 2.6.10-rc1, or has it always been broken in an
> ACPI-enabled kernel with acpi sharing an irq with e100?
>
> I suspect this may be a bug in the e100 -- it may have enabled
> interrupts before it has registered a handler.
I saw similar behaviour in 2.6.8.1 on a non-ACPI enabled kernel with
a dual-port e100. The nic simply would not work, spewing this error in
syslog:
NETDEV WATCHDOG: eth1: transmit timed out
If I booted with an ACPI enabled kernel, the box worked again. IRQ
sharing was involved, though can't recall which IRQ eth1 tried to use.
This was on a brand new Dell Optiplex.
Phil
prev parent reply other threads:[~2004-11-09 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 10:59 Spurious interrupts when SCI shared with e100 Udo A. Steinberg
2004-11-08 20:54 ` [patch] e100 and shared interrupts [was: Spurious interrupts when SCI shared with e100] peter swain
2004-11-09 22:22 ` J.A. Magallon
2004-11-09 5:42 ` Spurious interrupts when SCI shared with e100 Len Brown
2004-11-09 16:21 ` Phil Oester [this message]
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=20041109162142.GA12926@linuxace.com \
--to=kernel@linuxace.com \
--cc=ganesh.venkatesan@intel.com \
--cc=john.ronciak@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=us15@os.inf.tu-dresden.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.