[alsa-devel] [ALSA hda 3.4-rc] suspend2ram regression in snd_hda_intel

[Takashi Iwai]

At Tue, 08 May 2012 11:13:23 +0400,
Konstantin Khlebnikov wrote:
> 
> Takashi Iwai wrote:
> > At Sun, 06 May 2012 12:32:14 +0400,
> > Konstantin Khlebnikov wrote:
> >>
> >> Konstantin Khlebnikov wrote:
> >>> Mainline commit 785f857d1cb0856b612b46a0545b74aa2596e44a
> >>> ("ALSA: hda - Set codec to D3 forcibly even if not used")
> >>> breaks sound for my notebook (thinkpad x220),
> >>> looks like codec cannot wake from power-save state after resume.
> >>> After reverting looks like all works fine.
> >>>
> >>> how to reproduce:
> >>> * unplug the power cord (to enable hda power safe mode)
> >>> * play something and stop
> >>> * wait until the background noise disappears (codec went into power-save mode)
> >>> * suspend
> >>> * resume
> >>> * play something again and hear the silence
> >>> --
> >>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> >>> the body of a message to majordomo at vger.kernel.org
> >>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >>> Please read the FAQ at  http://www.tux.org/lkml/
> >>
> >> Bump
> >
> > It's a weekend, so don't expect quick responces from any normal person
> > :)
> 
> Yeah, sorry. In this country a mess with holidays and weekends.
> 
> >
> > Which 3.4-rc did you try?  There was a known problem with this codec
> > regarding the power-up sequence, but this should have been fixed in
> > the very recent version.
> 
> Bug still in latest v3.4-rc6.
> This is serious degradation since v3.3, so I hope it will be fixed before release.
> 
> >
> > If the latest Linus tree still shows the problem, try sound git tree
> > master or for-next branch.
> >     git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
> 
> I don't see there anything related to this problem. Bug is still there.
> It's 100% reproductible and disappears after reverting that commit.
> Looks like driver missed one power-up cycle after system-resume,
> after second power-save down/up cycle all work fine.

OK.  Could you try to pass model=auto and see whether it changes
the behavior?  I've checked only the auto-parser mode recently.
It might be just the static quirk that got broken.

Note that the mixer elements will be renamed by this, so make sure
that you adjust the mixer before testing S3.


Takashi