linux-kernel - Re: [regression] Sound not transferred to docking station after resume from StR

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 19 Apr 2010 13:59:36 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Frans Pop <elendil@...net.nl>
Cc:	linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
	alsa-devel@...a-project.org
Subject: Re: [regression] Sound not transferred to docking station after resume from StR

At Mon, 19 Apr 2010 13:38:14 +0200,
Frans Pop wrote:
> 
> On Monday 19 April 2010, Takashi Iwai wrote:
> > Could you give alsa-info.sh on your machine, preferably before/after
> > suspend on both working (2.6.33) and non-working kernels?
> 
> See files in attached tarball. Contents are:
> * system boot (docked)
>   => alsa-info.txt_3[34]_docked
> * undock
>   => alsa-info.txt_3[34]_undocked
> * suspend - dock (while suspended) - resume
>   => alsa-info.txt_3[34]_after_resume_docked
> * undock - redock (this disables the internal speakers)
>   => alsa-info.txt_34_after_resume_redocked
> 
> > 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.
> 
> That fixes the problem.

Then my rough guess is

commit ea52bf260ecbb175339af3178c15788df21b7516
Author: Daniel T Chen <crimsun@...ntu.com>
Date:   Sun Dec 27 18:48:29 2009 -0500

    ALSA: hda: Add powerdown for Analog Devices HDA codecs
    
Could you try to revert it?


thanks,

Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/