From: Takashi Iwai <tiwai@suse.de>
To: Juan <jcb@niluge.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: spurious APIC interrupt , then freeze
Date: Tue, 14 Oct 2003 16:38:41 +0200 [thread overview]
Message-ID: <s5hr81fubny.wl@alsa2.suse.de> (raw)
In-Reply-To: <20031012213253.GA441@zeus.homenet>
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
At Sun, 12 Oct 2003 23:32:53 +0200,
Juan wrote:
>
>
> Soon after i load the maestro3 driver on a dell c600 laptop, kernel
> 2.6.0-test7; i get a 'spurious APIC interrupt on CPU#0, should never
> happen.'
>
> then the laptop freezes and i have to power off by pressing the power
> button.
>
> what does this mean ? how can it be fixed ?
does the attached patch have some influence?
Takashi
[-- Attachment #2: m3-mpu-fix.dif --]
[-- Type: application/octet-stream, Size: 657 bytes --]
Index: alsa-kernel/pci/maestro3.c
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-kernel/pci/maestro3.c,v
retrieving revision 1.43
diff -u -r1.43 maestro3.c
--- alsa-kernel/pci/maestro3.c 12 Aug 2003 14:05:07 -0000 1.43
+++ alsa-kernel/pci/maestro3.c 14 Oct 2003 14:36:33 -0000
@@ -2349,7 +2349,8 @@
{
unsigned long io = chip->iobase;
- outw(ASSP_INT_ENABLE | MPU401_INT_ENABLE, io + HOST_INT_CTRL);
+ /* TODO: MPU401 not supported yet */
+ outw(ASSP_INT_ENABLE /*| MPU401_INT_ENABLE*/, io + HOST_INT_CTRL);
outb(inb(io + ASSP_CONTROL_C) | ASSP_HOST_INT_ENABLE,
io + ASSP_CONTROL_C);
}
next prev parent reply other threads:[~2003-10-14 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 20:42 Maybe a bug with cmipci cmi8738 sound chip Attila Konietzka
2003-10-12 21:32 ` spurious APIC interrupt , then freeze Juan
2003-10-14 14:38 ` Takashi Iwai [this message]
[not found] ` <20031014153243.GA6393@athena>
2003-10-14 16:42 ` Takashi Iwai
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=s5hr81fubny.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=jcb@niluge.net \
/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