All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
Cc: 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: 09 Nov 2004 00:42:46 -0500	[thread overview]
Message-ID: <1099978966.6092.36.camel@d845pe> (raw)
In-Reply-To: <20041108115955.1c8bf10f.us15@os.inf.tu-dresden.de>

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.

Assuming it is a receive interrupt, you may be able to verify this by
plugging in the network cable after the system has probed e100 and see
if it works normally after that.

Also, you might try out the eepro100 driver to see if it behaves any
differently.

thanks,
-Len



  parent reply	other threads:[~2004-11-09  6:07 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 ` Len Brown [this message]
2004-11-09 16:21   ` Spurious interrupts when SCI shared with e100 Phil Oester

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=1099978966.6092.36.camel@d845pe \
    --to=len.brown@intel.com \
    --cc=ganesh.venkatesan@intel.com \
    --cc=john.ronciak@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.