From: "Brown, Len" <len.brown@intel.com>
To: "Daniel Jacobowitz" <dan@debian.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: 2.6.2-rc3: irq#19 - nobody cared - with an au88xx
Date: Wed, 7 Apr 2004 00:08:59 -0400 [thread overview]
Message-ID: <BF1FE1855350A0479097B3A0D2A80EE002F7B775@hdsmsx402.hd.intel.com> (raw)
>I'm assuming that it is not the fault of either of these drivers, since
>both of those are quite straightforward; they appear to be actually
>being triggered when nothing is going on.
If IRQ initialization is done incorrectly, it is possible
For a driver to request_irq(X), while the hardware is actually
on IRQ Y.
Then when that device becomes active, it would kill the other
devices on Y because its handler is looking for interrupts on X.
If this happens with acpi enabled, but doesn't happen with acpi=off
or pci=noacpi, then we need to compare the /proc/interrupts between
the working and failintg configs to see if the IRQs have moved around
when perhaps they should not have. Dmesg from the ACPI case would
also be needed.
>There was a set of APIC errors an hour before, but they're probably
>unrelated:
>Apr 6 11:31:31 nevyn kernel: APIC error on CPU1: 00(08)
>Apr 6 11:31:31 nevyn kernel: APIC error on CPU0: 00(02)
I believe this is due to transient hardware errors on your MB.
Though not fatal, it isn't a good indicator.
-Len
next reply other threads:[~2004-04-07 4:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 4:08 Brown, Len [this message]
2004-04-07 14:59 ` 2.6.2-rc3: irq#19 - nobody cared - with an au88xx Daniel Jacobowitz
2004-04-12 18:51 ` Daniel Jacobowitz
2004-04-12 21:28 ` Daniel Jacobowitz
2004-04-12 21:51 ` Jeff Garzik
[not found] <BF1FE1855350A0479097B3A0D2A80EE0023E89C2@hdsmsx402.hd.intel.com>
2004-02-07 6:11 ` Len Brown
2004-02-07 6:33 ` Daniel Jacobowitz
2004-04-06 18:02 ` Daniel Jacobowitz
2004-04-06 22:04 ` Daniel Jacobowitz
2004-04-06 23:43 ` Joshua Kwan
-- strict thread matches above, loose matches on Subject: below --
2004-02-07 4:42 Daniel Jacobowitz
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=BF1FE1855350A0479097B3A0D2A80EE002F7B775@hdsmsx402.hd.intel.com \
--to=len.brown@intel.com \
--cc=dan@debian.org \
--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;
as well as URLs for NNTP newsgroup(s).