From: Takashi Iwai <tiwai@suse.de>
To: "Lenar Lõhmus" <lenar@vision.ee>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: irq 7: nobody cared! (intel8x0 sound / 2.6.2-rc3-mm1)
Date: Tue, 10 Feb 2004 20:05:35 +0100 [thread overview]
Message-ID: <s5hvfmebvr4.wl@alsa2.suse.de> (raw)
In-Reply-To: <4029143B.30408@vision.ee>
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
At Tue, 10 Feb 2004 19:26:19 +0200,
Lenar Lõhmus wrote:
>
> Takashi Iwai wrote:
>
> >
> >could you check the status register value when this happens with the
> >attached patch?
> >
> >
> It never happened after applying this patch (not the right circumstances
> I think). It always printed this:
>
> intel8x0: ignored irq, status = 0x300100, sta_mask = 0xf0
>
> And sound worked.
>
> Today discovered this message from dmesg:
>
> intel8x0: ignored irq, status = 0x300100, sta_mask = 0xf0
> intel8x0: ignored irq, status = 0x300100, sta_mask = 0xf0
> intel8x0: ignored irq, status = 0x300100, sta_mask = 0xf0
> irq 7: nobody cared!
ok then really some unknown status bits are set.
the attached patch should fix this problem anyway.
Takashi
[-- Attachment #2: Type: text/plain, Size: 340 bytes --]
--- linux/sound/pci/intel8x0.c 6 Feb 2004 17:47:49 -0000 1.115
+++ linux/sound/pci/intel8x0.c 10 Feb 2004 19:03:43 -0000
@@ -807,7 +807,7 @@
if (status)
iputdword(chip, chip->int_sta_reg, status);
spin_unlock(&chip->reg_lock);
- return IRQ_NONE;
+ return IRQ_HANDLED(status);
}
for (i = 0; i < chip->bdbars_count; i++) {
next prev parent reply other threads:[~2004-02-10 19:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 16:19 irq 7: nobody cared! (intel8x0 sound / 2.6.2-rc3-mm1) Lenar Lõhmus
2004-02-09 18:56 ` Takashi Iwai
2004-02-10 17:26 ` Lenar Lõhmus
2004-02-10 19:05 ` Takashi Iwai [this message]
2004-02-10 19:50 ` Ralf Gerbig
2004-02-10 20:23 ` Linus Torvalds
2004-02-10 20:49 ` Ralf Gerbig
2004-02-11 10:42 ` Takashi Iwai
2004-02-11 20:11 ` Ralf Gerbig
2004-02-13 11:05 ` Takashi Iwai
2004-02-10 19:09 ` Ralf Gerbig
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=s5hvfmebvr4.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=lenar@vision.ee \
--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