Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: jean-charles <jcb@niluje.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: spurious APIC interrupt , then freeze
Date: Tue, 14 Oct 2003 18:42:48 +0200	[thread overview]
Message-ID: <s5hismru5x3.wl@alsa2.suse.de> (raw)
In-Reply-To: <20031014153243.GA6393@athena>

At Tue, 14 Oct 2003 17:32:43 +0200,
jean-charles wrote:
> 
> On Tuesday 14 October, 2003 ╴ 04:38:41PM +0200, Takashi Iwai wrote:
> > 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?
> > 
> 
> hi,
> 
> i already have tried to do that :(  what really annoy me is that the
> freeze does not happend every time !!!!
> how can i "debug" a system freeze ?

if it's a kernel panic, you can at least have the control with magic
sysrq.  if it's not, the last resort is NMI watchdog...


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php

      parent reply	other threads:[~2003-10-14 16:42 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
     [not found]     ` <20031014153243.GA6393@athena>
2003-10-14 16:42       ` Takashi Iwai [this message]

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=s5hismru5x3.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=jcb@niluje.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