From: Takashi Iwai <tiwai@suse.de>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org, alsa-devel@alsa-project.org
Subject: Re: [regression] Sound not transferred to docking station after resume from StR
Date: Mon, 19 Apr 2010 09:47:37 +0200 [thread overview]
Message-ID: <s5hbpdfrihy.wl%tiwai@suse.de> (raw)
In-Reply-To: <201004171106.23787.elendil@planet.nl>
At Sat, 17 Apr 2010 11:06:22 +0200,
Frans Pop wrote:
>
> On Friday 16 April 2010, Frans Pop wrote:
> > Scenario:
> > - suspend laptop while *un*docked, i.e. with laptop speakers in use
> > - dock laptop
> > - resume
> >
> > With 2.6.33 and earlier the sound would always come from the external
> > speakers connected to the docking station. But with 2.6.34-rc4 I get
> > sound still coming from the laptop's internal speakers, which is not
> > correct.
>
> The problem is slightly different than I thought. Turns out *both* the
> internal (laptop) and external (docking station) speakers are active after
> the resume. So the problem is that the internal speakers are not switched off.
>
> I have traced this to an ALSA merge: 524df55725217. Unfortunately I get
> boot failures when I try to bisect down into that merge.
>
> Here's the bisect log:
> # bad: [0d0fb0f9c5fddef4a10242fe3337f00f528a3099] Linux 2.6.34-rc4
> # good: [724e6d3fe8003c3f60bf404bf22e4e331327c596] Linux 2.6.33-rc8
> git bisect start 'v2.6.34-rc4' 'v2.6.33-rc8'
> # bad: [94468080220162f74dc6ce5c3e95e5fec8022902]
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty-2.6
> git bisect bad 94468080220162f74dc6ce5c3e95e5fec8022902
> # bad: [524df55725217b13d5a232fb5badb5846418ea0e] Merge branch 'for-linus'
> of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6
> git bisect bad 524df55725217b13d5a232fb5badb5846418ea0e
> # good: [0f4533979473a456a8adb3869365e12c7a99cf65]
> Merge branches 'futexes-for-linus', 'irq-core-for-linus' and
> 'bkl-drivers-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip
> git bisect good 0f4533979473a456a8adb3869365e12c7a99cf65
Could you give alsa-info.sh on your machine, preferably before/after
suspend on both working (2.6.33) and non-working kernels?
Also, you can try to copy sound/pci/hda/patch_analog.c from 2.6.33 to
2.6.34 to check whether it works. There shouldn't be many changes in
that file.
thanks,
Takashi
next prev parent reply other threads:[~2010-04-19 7:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 19:31 Frans Pop
2010-04-16 19:48 ` Frans Pop
2010-04-17 9:06 ` Frans Pop
2010-04-19 7:47 ` Takashi Iwai [this message]
2010-04-19 11:38 ` Frans Pop
2010-04-19 11:59 ` Takashi Iwai
2010-04-19 12:14 ` Takashi Iwai
2010-04-19 12:39 ` Frans Pop
2010-04-19 12:53 ` Takashi Iwai
2010-04-19 14:58 ` Frans Pop
2010-04-19 16:17 ` Takashi Iwai
2010-04-19 12:18 ` Frans Pop
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=s5hbpdfrihy.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.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
Powered by JetHome