All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, linux-kernel@vger.kernel.org, alsa-devel@vger.kernel.org
Subject: Re: General protection fault when unloading snd_hda_intel on 2.6.30-rc1+
Date: Sat, 11 Apr 2009 13:20:33 -0700	[thread overview]
Message-ID: <20090411132033.003c581c@infradead.org> (raw)
In-Reply-To: <20090411193630.GA16968@Pilar.aei.mpg.de>

On Sat, 11 Apr 2009 21:36:30 +0200
"Carlos R. Mafra" <crmafra2@gmail.com> wrote:

> general protection fault:

Hi,

if you happen to have CONFIG_DEBUG_INFO enabled, then you can run the
oops through scripts/markup_oops.pl to get the source code of the exact
line that is oopsing.. makes diagnosing it even easier!



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

WARNING: multiple messages have this Message-ID (diff)
From: Arjan van de Ven <arjan@infradead.org>
To: "Carlos R. Mafra" <crmafra2@gmail.com>
Cc: linux-kernel@vger.kernel.org, tiwai@suse.de, alsa-devel@vger.kernel.org
Subject: Re: General protection fault when unloading snd_hda_intel on 2.6.30-rc1+
Date: Sat, 11 Apr 2009 13:20:33 -0700	[thread overview]
Message-ID: <20090411132033.003c581c@infradead.org> (raw)
In-Reply-To: <20090411193630.GA16968@Pilar.aei.mpg.de>

On Sat, 11 Apr 2009 21:36:30 +0200
"Carlos R. Mafra" <crmafra2@gmail.com> wrote:

> general protection fault:

Hi,

if you happen to have CONFIG_DEBUG_INFO enabled, then you can run the
oops through scripts/markup_oops.pl to get the source code of the exact
line that is oopsing.. makes diagnosing it even easier!



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2009-04-11 20:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-11 19:36 General protection fault when unloading snd_hda_intel on 2.6.30-rc1+ Carlos R. Mafra
2009-04-11 20:20 ` Arjan van de Ven [this message]
2009-04-11 20:20   ` Arjan van de Ven
2009-04-11 21:03   ` Carlos R. Mafra
2009-04-11 21:03   ` Carlos R. Mafra
2009-04-11 21:39     ` Arjan van de Ven
2009-04-11 21:39       ` Arjan van de Ven
2009-04-12  0:33       ` Michal Jaegermann
2009-04-12  0:33       ` Michal Jaegermann
2009-04-12  1:58         ` General protection fault when unloading snd_hda_intel on 2.6.30-rc1+ (bisected) Carlos R. Mafra
2009-04-12  1:58         ` Carlos R. Mafra
2009-04-14 14:27 ` General protection fault when unloading snd_hda_intel on 2.6.30-rc1+ Takashi Iwai
2009-04-14 14:27   ` Takashi Iwai
2009-04-14 16:21   ` Carlos R. Mafra
2009-04-14 16:21   ` Carlos R. Mafra
2009-04-15 11:04     ` Takashi Iwai
2009-04-15 11:04       ` [alsa-devel] " Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2009-04-11 19:36 Carlos R. Mafra

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=20090411132033.003c581c@infradead.org \
    --to=arjan@infradead.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-devel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.