From: Jeff Chua <jeff.chua.linux@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Akinobu Mita <akinobu.mita@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
perex@perex.cz, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] sound updates for 2.6.30
Date: Wed, 8 Apr 2009 20:56:11 +0800 [thread overview]
Message-ID: <b6a2187b0904080556gdab1382t466c7fd1303800ee@mail.gmail.com> (raw)
In-Reply-To: <s5hmyarq5bh.wl%tiwai@suse.de>
On Wed, Apr 8, 2009 at 9:53 AM, Takashi Iwai <tiwai@suse.de> wrote:
> At Tue, 7 Apr 2009 14:04:28 +0800,
> Jeff Chua wrote:
>>
>> I encountered this oops with the latest linux git pull. Will this
>> update fix the problem? When I rolled back to 2.6.29-stable, the sound
>> works find.
>>
>> Oops from dmesg ...
>
> Judging also from other bug reports, this looks like Analog codec
> specific. Likely it's a typo or so...
>
> Could you add probe_only=1 module option and load the module, then
> run alsa-info.sh output with --no-upload option and attach the
> generated file? The script is found at
> http://www.alsa-project.org/alsa-info.sh
>
> (BTW, I'm on vacation now, and I'll check this bug after Easter
> holidays. Sorry for inconvenience.)
Good news is the latest linux git pull today makes the HDA opps go
away. It's all good now.
Thanks and Happy Easter!
Jeff.
next prev parent reply other threads:[~2009-04-08 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 2:53 Takashi Iwai
2009-04-07 3:42 ` Stephen Rothwell
2009-04-07 6:04 ` Jeff Chua
2009-04-07 8:23 ` Akinobu Mita
2009-04-08 1:53 ` Takashi Iwai
2009-04-08 12:56 ` Jeff Chua [this message]
2009-04-13 13:32 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2009-03-24 6:59 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=b6a2187b0904080556gdab1382t466c7fd1303800ee@mail.gmail.com \
--to=jeff.chua.linux@gmail.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®