From: Len Brown <len.brown@intel.com>
To: Christopher Swingley <cswingle@iarc.uaf.edu>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: IRQ issues, (nobody cared, disabled), not USB
Date: 10 Jul 2004 22:48:48 -0400 [thread overview]
Message-ID: <1089514128.32038.62.camel@dhcppc2> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615FFACC@hdsmsx403.hd.intel.com>
On Fri, 2004-07-09 at 11:32, Christopher Swingley wrote:
> I can no longer recall when this first started happening, but there's
> a good chance this happened when I was running 2.6.5 too. I track the
> vanilla releases pretty closely.
It would be interesting if the IRQ failure was always on IRQ7.
When you moved slots, did the device move to a different
IRQ and fail there too?
Running ACPI, you may be able to move that device off of
IRQ7 with "acpi_irq_balance" plus "acpi_isa_irq=7".
Hardware routes spurious interrupts to IRQ7, so your
device may be an innocent victim of those. Also,
there may be some motherboard device pulling on IRQ7
that Linux doesn't know about -- so see if you can
disable any extra motherboard devices in BIOS setup.
Finally, you might run a kernel with the IOAPIC enabled,
such as the CONFIG_SMP kernel, to see if you have an
IOAPIC on the board and if that mode works differently.
cheers,
-Len
next parent reply other threads:[~2004-07-11 2:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FFACC@hdsmsx403.hd.intel.com>
2004-07-11 2:48 ` Len Brown [this message]
2004-07-12 14:43 ` IRQ issues, (nobody cared, disabled), not USB Christopher Swingley
2004-07-08 15:53 Christopher Swingley
2004-07-09 5:05 ` Andrew Morton
2004-07-09 15:32 ` Christopher Swingley
2004-07-11 8:39 ` Ville Herva
2004-07-13 10:49 ` Ville Herva
2004-07-12 14:38 ` Christopher Swingley
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=1089514128.32038.62.camel@dhcppc2 \
--to=len.brown@intel.com \
--cc=akpm@osdl.org \
--cc=cswingle@iarc.uaf.edu \
--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