mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Carlos R. Mafra" <crmafra2@gmail.com>
To: tiwai@suse.de
Cc: Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org, alsa-devel@vger.kernel.org,
	Michal Jaegermann <michal@ellpspace.math.ualberta.ca>
Subject: Re: General protection fault when unloading snd_hda_intel on 2.6.30-rc1+ (bisected)
Date: Sun, 12 Apr 2009 03:58:11 +0200	[thread overview]
Message-ID: <20090412015811.GA3907@Pilar.aei.mpg.de> (raw)
In-Reply-To: <20090412003320.GA17346@ellpspace.math.ualberta.ca>

On Sat 11.Apr'09 at 18:33:20 -0600, Michal Jaegermann wrote:
> On Sat, Apr 11, 2009 at 02:39:50PM -0700, Arjan van de Ven wrote:
> > 
> > so... "dev" is pointing evbit at... 697665646632785 which looks like grabage.
> 
> FWIW 697665646632785c decodes in ASCII as "\x2fdevi".

So I painfully (exchanged 'good' for 'bad' in the middle and had
to restart all over) bisected this down to

commit 3be141494a080a9189b51fa78154c975ad8d9806
Author: Takashi Iwai <tiwai@suse.de>
Date:   Fri Feb 20 14:11:16 2009 +0100

    ALSA: hda - Add generic pincfg initialization

    Added the generic pincfg cache and save/restore functions.
    Also introduced the pin-overriding via hwdep sysfs.


It doesn't revert cleanly from the latest kernel, so I could not double 
check it.

OBS: All tests were done with the headphone plugged in.

  reply	other threads:[~2009-04-12  1:59 UTC|newest]

Thread overview: 9+ 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
2009-04-11 21:03   ` Carlos R. Mafra
2009-04-11 21:39     ` Arjan van de Ven
2009-04-12  0:33       ` Michal Jaegermann
2009-04-12  1:58         ` Carlos R. Mafra [this message]
2009-04-14 14:27 ` Takashi Iwai
2009-04-14 16:21   ` Carlos R. Mafra
2009-04-15 11:04     ` [alsa-devel] " 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=20090412015811.GA3907@Pilar.aei.mpg.de \
    --to=crmafra2@gmail.com \
    --cc=alsa-devel@vger.kernel.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal@ellpspace.math.ualberta.ca \
    --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 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®