From: Takashi Iwai <tiwai@suse.de>
To: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Santinoli <david@santinoli.com>
Subject: Re: ALSA: hda/realtek: quirk for D945GCLF2 mainboard
Date: Fri, 07 May 2010 10:42:23 +0200 [thread overview]
Message-ID: <s5hiq70rtlc.wl%tiwai@suse.de> (raw)
In-Reply-To: <201005070259.08094.s.L-H@gmx.de>
At Fri, 7 May 2010 02:59:01 +0200,
Stefan Lippers-Hollmann wrote:
>
> [1 <text/plain; iso-8859-1 (7bit)>]
> Hi
>
> On Friday 07 May 2010, Takashi Iwai wrote:
> > At Thu, 29 Apr 2010 23:00:42 +0200,
> > Stefan Lippers-Hollmann wrote:
> > >
> > > Hi
> > >
> > > Since kernel 2.6.33 (and including 2.6.34-rc5-git10), sound output is
> > > broken on my Intel D945GCLF2 mainboard, while it did work well on earlier
> > > kernels up to and including 2.6.32.12.
> >
> > Could you give alsa-info.sh output (run with --no-upload option)?
> > I would revert in the worst case, but before that, I'd like to analyze
> > the real issue.
>
> Attached are alsa-info.sh and full, as far as the buffer allows, dmesg
> outputs from:
> - plain 2.6.34-rc6-git5, no sound:
> + alsa-info_plain-2.6.34-rc6-git5.log.gz
> + dmesg_plain-2.6.34-rc6-git5.log.gz
> - 2.6.34-rc6-git5 with the proposed
> "revert-ALSA_hda-realtek_quirk-for-D945GCLF2-mainboard" applied:
> + alsa-info_revert-ALSA_hda-realtek_quirk-for-D945GCLF2-mainboard.log.gz
> + dmesg_revert-ALSA_hda-realtek_quirk-for-D945GCLF2-mainboard.log.gz
> the kernel config is config-2.6.34-rc6-sidux-amd64.gz in both cases.
>
> Additionally I've tested a current OpenSuSE factory live CD
> (openSUSE-KDE-LiveCD-x86_64-Build0589-Media.iso) daily with kernel
> 2.6.34-rc - sound not working:
> + alsa-info_openSUSE-KDE-LiveCD-x86_64-Build0589-Media.log.gz
> + dmesg_openSUSE-KDE-LiveCD-x86_64-Build0589-Media.log.gz
> and a few days old Fedora rawhide nightly with exactly the same symptoms,
> no logs attached.
>
> Up to and including kernel 2.6.32 (tested since ~2.6.26) ALSA always worked
> out-of-the-box, once I revert 7aee67466536bbf8bb44a95712c848a61c5a0acd
> (ALSA: hda/realtek: quirk for D945GCLF2 mainboard) from 2.6.33(.3) or
> 2.6.34-rc6-git5, snd-hda-intel/ snd_hda_codec_realtek have managed to
> initialize again in all my my tests so far. I'd be happy to test any
> potential alternatives to that patch. Unfortunately I usually don't notice
> graphics or audio regressions quickly, as that system is running quasi
> headless/ speakerless most of the time, but I can test it any time of
> course.
Could you try probe_mask=4 option without reverting?
I don't find any wrong verb with the quirk, so this looks more like a
problem in the slot probing.
thanks,
Takashi
next prev parent reply other threads:[~2010-05-07 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 21:00 ALSA: hda/realtek: quirk for D945GCLF2 mainboard Stefan Lippers-Hollmann
2010-05-06 10:50 ` Takashi Iwai
2010-05-07 0:59 ` Stefan Lippers-Hollmann
2010-05-07 8:42 ` Takashi Iwai [this message]
2010-05-08 23:24 ` Stefan Lippers-Hollmann
2010-05-10 15:18 ` 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=s5hiq70rtlc.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=david@santinoli.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.L-H@gmx.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