From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@digeo.com>
Cc: Shane Shrybman <shrybman@sympatico.ca>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.68-mmX: Drowning in irq 7: nobody cared!
Date: 06 May 2003 10:35:34 +0100 [thread overview]
Message-ID: <1052213733.28797.1.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030505143006.29c0301a.akpm@digeo.com>
On Llu, 2003-05-05 at 22:30, Andrew Morton wrote:
> Shane Shrybman <shrybman@sympatico.ca> wrote:
> >
> > Hi,
> >
> > I am getting a lot of these in the logs. This is with the ALSA emu10k1
> > driver for a SB live card. This is a x86, UP, KT133 system with preempt
> > enabled. The system seems to be running fine.
> >
> > handlers:
> > [<d8986540>] (gcc2_compiled.+0x0/0x390 [snd_emu10k1])
> > irq 7: nobody cared!
>
> Beats me. Does this fix it up?
With APIC at least it doesnt suprise me the least. The IRQ hack seems
extremely racey. Remember on most systems (especially with PIII type
APIC) IRQ delivery is asynchronous to the bus so you get
IRQ arrives
sound card
loop
clean up IRQ
IRQ sent
still more work, do it
done
HANDLED
IRQ arrives
sound card
Umm duh no work for me
NOT HANDLED
Whine
For anything where you get pairs of close IRQ's
next prev parent reply other threads:[~2003-05-06 10:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 13:23 Shane Shrybman
2003-05-05 21:30 ` Andrew Morton
2003-05-06 9:35 ` Alan Cox [this message]
2003-05-06 10:41 ` Zwane Mwaikambo
2003-05-06 11:17 ` Alan Cox
2003-05-06 15:17 ` Andrew Morton
2003-05-06 15:07 ` Alan Cox
2003-05-06 16:12 ` Andrew Morton
2003-05-07 22:10 ` Shane Shrybman
2003-05-06 21:44 Chuck Ebbert
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=1052213733.28797.1.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shrybman@sympatico.ca \
/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
all inboxes | Powered by JetHome®