From: Len Brown <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: 07 Feb 2004 01:11:48 -0500 [thread overview]
Message-ID: <1076134307.2562.1553.camel@dhcppc4> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0023E89C2@hdsmsx402.hd.intel.com>
Can you isolate this regression to a specific release? There have been
several changes to arch/i386/kernel/irq.c since 2.6.0-test7. Also, it
would be interesting to know if it also happens with CONFIG_SMP=n (but
with the IOAPIC still enabled) Plus, a sanity check of the rate of
interrutps reported by /proc/interrupts might yield a clue.
thanks,
-Len
ps.
You can avoid the symptom by booting with "noirqdebug" or having the
interrupt handling always return IRQ_HANDLED. But then we'd lose the
means to find out why the driver is receiving interrupts for which it
can find no cause.
On Fri, 2004-02-06 at 23:42, Daniel Jacobowitz wrote:
> I've started getting this, every 24 hours or so:
>
> irq 19: nobody cared!
> Call Trace:
> [<c010d38a>] __report_bad_irq+0x2a/0x90
> [<c010d480>] note_interrupt+0x70/0xb0
> [<c010d7c0>] do_IRQ+0x160/0x1a0
> [<c0105000>] _stext+0x0/0x60
> [<c010b8d8>] common_interrupt+0x18/0x20
> [<c0108990>] default_idle+0x0/0x40
> [<c0105000>] _stext+0x0/0x60
> [<c01089bc>] default_idle+0x2c/0x40
> [<c0108a4b>] cpu_idle+0x3b/0x50
> [<c04b64a0>] unknown_bootoption+0x0/0x120
> [<c04b6926>] start_kernel+0x1a6/0x1f0
> [<c04b64a0>] unknown_bootoption+0x0/0x120
>
> handlers:
> [<f886b290>] (au_isr+0x0/0xb0 [au8830])
> Disabling IRQ #19
>
> and then sound doesn't work for a while.
>
> There's a good chance this is my fault. IRQ 19 is:
>
> 19: 18500001 0 IO-APIC-level au88xx
>
> and the au88xx driver is an out-of-tree driver that was developed on
> 2.4/early-2.5, and I ported it to 2.6 myself. It worked flawlessly on
> 2.6.0-test7; has something changed in how interrupt handlers are
> required to
> behave?
>
> [Just ask if you actually want the source to this driver... I don't
> know
> enough about the card to actually submit it to Linus's tree and the
> driver's
> original authors aparently didn't care to.]
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next parent reply other threads:[~2004-02-07 6:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE0023E89C2@hdsmsx402.hd.intel.com>
2004-02-07 6:11 ` Len Brown [this message]
2004-02-07 6:33 ` 2.6.2-rc3: irq#19 - nobody cared - with an au88xx Daniel Jacobowitz
2004-04-06 18:02 ` Daniel Jacobowitz
2004-04-06 22:04 ` Daniel Jacobowitz
2004-04-06 23:43 ` Joshua Kwan
2004-04-07 4:08 Brown, Len
2004-04-07 14:59 ` Daniel Jacobowitz
2004-04-12 18:51 ` Daniel Jacobowitz
2004-04-12 21:28 ` Daniel Jacobowitz
2004-04-12 21:51 ` Jeff Garzik
-- 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=1076134307.2562.1553.camel@dhcppc4 \
--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).