From: Greg KH <gregkh@suse.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: stable@kernel.org, alsa-devel@alsa-project.org,
Emmanuel Benisty <benisty.e@gmail.com>,
Andrew Clayton <andrew@digital-domain.net>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.38.4 broke my audio
Date: Sun, 24 Apr 2011 17:01:26 -0700 [thread overview]
Message-ID: <20110425000126.GA18681@suse.de> (raw)
In-Reply-To: <20110424113037.11af0b04@omega.digital-domain.net>
On Sun, Apr 24, 2011 at 11:30:37AM +0100, Andrew Clayton wrote:
> Hi guys.
>
> Just upgraded to .4 from .3 and found my audio was _really_ quiet. All
> the mixers looked sane.
>
> A quick check of the changelog and a revert of:
>
> commit 58541cc27531727f7120683a7cb123ee3ada4bd4
> Author: Takashi Iwai <tiwai@suse.de>
> Date: Mon Mar 28 12:05:31 2011 +0200
>
> ALSA: hda - Fix pin-config of Gigabyte mobo
>
> commit c6b358748e19ce7e230b0926ac42696bc485a562 upstream.
>
> Use pin-fix instead of the static quirk for Gigabyte mobos 1458:a002.
>
> Bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=677256
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> made it normal again.
Takashi, do you have a fix for this, or should I revert this from the
.38 stable tree? It looks like we now have 2 reports of this problem.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@suse.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Andrew Clayton <andrew@digital-domain.net>,
Emmanuel Benisty <benisty.e@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: 2.6.38.4 broke my audio
Date: Sun, 24 Apr 2011 17:01:26 -0700 [thread overview]
Message-ID: <20110425000126.GA18681@suse.de> (raw)
In-Reply-To: <20110424113037.11af0b04@omega.digital-domain.net>
On Sun, Apr 24, 2011 at 11:30:37AM +0100, Andrew Clayton wrote:
> Hi guys.
>
> Just upgraded to .4 from .3 and found my audio was _really_ quiet. All
> the mixers looked sane.
>
> A quick check of the changelog and a revert of:
>
> commit 58541cc27531727f7120683a7cb123ee3ada4bd4
> Author: Takashi Iwai <tiwai@suse.de>
> Date: Mon Mar 28 12:05:31 2011 +0200
>
> ALSA: hda - Fix pin-config of Gigabyte mobo
>
> commit c6b358748e19ce7e230b0926ac42696bc485a562 upstream.
>
> Use pin-fix instead of the static quirk for Gigabyte mobos 1458:a002.
>
> Bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=677256
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> made it normal again.
Takashi, do you have a fix for this, or should I revert this from the
.38 stable tree? It looks like we now have 2 reports of this problem.
thanks,
greg k-h
next prev parent reply other threads:[~2011-04-25 0:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 10:30 2.6.38.4 broke my audio Andrew Clayton
2011-04-25 0:01 ` Greg KH [this message]
2011-04-25 0:01 ` Greg KH
2011-04-25 9:25 ` Takashi Iwai
2011-04-25 9:25 ` Takashi Iwai
2011-04-25 17:34 ` Greg KH
2011-04-25 17:34 ` Greg KH
2011-04-25 20:25 ` Takashi Iwai
2011-04-25 20:25 ` Takashi Iwai
2011-04-26 0:12 ` Andrew Clayton
2011-04-26 12:41 ` Takashi Iwai
2011-04-26 12:41 ` Takashi Iwai
2011-04-27 1:05 ` Andrew Clayton
2011-04-26 1:42 ` Emmanuel Benisty
2011-04-26 12:49 ` Takashi Iwai
2011-04-26 12:49 ` Takashi Iwai
2011-04-27 1:15 ` Emmanuel Benisty
2011-04-27 8:36 ` Takashi Iwai
2011-04-27 8:36 ` Takashi Iwai
2011-04-27 14:57 ` Emmanuel Benisty
2011-04-27 15:47 ` Takashi Iwai
2011-04-27 15:47 ` Takashi Iwai
2011-04-27 16:17 ` Emmanuel Benisty
2011-04-27 19:35 ` Takashi Iwai
2011-04-27 19:35 ` Takashi Iwai
2011-04-28 1:07 ` Emmanuel Benisty
2011-04-28 5:37 ` Takashi Iwai
2011-04-28 5:37 ` Takashi Iwai
2011-04-28 5:50 ` Emmanuel Benisty
2011-04-28 6:16 ` Takashi Iwai
2011-04-28 6:16 ` Takashi Iwai
2011-04-29 8:25 ` Andrew Clayton
2011-04-29 9:13 ` Takashi Iwai
2011-04-29 9:13 ` Takashi Iwai
2011-05-01 11:19 ` Emmanuel Benisty
2011-05-02 8:49 ` Takashi Iwai
2011-04-26 13:06 ` Raymond Yau
2011-04-26 2:02 ` Raymond Yau
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=20110425000126.GA18681@suse.de \
--to=gregkh@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andrew@digital-domain.net \
--cc=benisty.e@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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.