Bug 5621 - no sound with snd-via82xx after resume from S3
Summary: no sound with snd-via82xx after resume from S3
Status: REJECTED UNREPRODUCIBLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Sound(ALSA) (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Jaroslav Kysela
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-17 02:11 UTC by richlv
Modified: 2007-04-28 12:49 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.15-rc1
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description richlv 2005-11-17 02:11:32 UTC
Most recent kernel where this bug did not occur: 2.6.13.2
Distribution: slackware
Hardware Environment: fujitsu-siemens lifebook c-1020

this laptop has via technologies vt8233/a/8235/8237 ac97 audio controller that 
uses snd-via82xx driver (compiled in)

this seems to be a regression, as sound works after resuming with 2.6.13.2.
applications do not complain, there seems to be nothing relevant in logfiles, 
but there is no sound at all.
Comment 1 Karol Kozimor 2005-12-08 15:07:17 UTC
Might be unrelated, but I see the same behaviour with snd_intel8x0 on ICH3 on 
2.6.15-rc[45]. No sound until module reload, fiddling with mixer controls 
doesn't help. 
Comment 2 Karol Kozimor 2005-12-14 15:02:50 UTC
Ugh, changing mixer controls *does* help, but apparently you need to change 
both Master and PCM (which still is a regression). Sorry for the noise, 
though. 
Comment 3 richlv 2005-12-14 22:34:57 UTC
grmh. thanks for the hint.
seems to be the same problem for me, so this is not a single audiocard.

after resuming mixer levels are correct (so i did not bother changing them both
;) ), but there is no sound. as mentioned, changing both master and pcm 
restores it.
Comment 4 Lee Revell 2006-01-20 19:11:31 UTC
This (and several other recent regressions) is probably related to the recent
ALSA PM changes.
Comment 5 Karol Kozimor 2006-02-18 03:13:39 UTC
Still no change as of 2.6.16-rc2. 
 
OTOH, sound is fine after S4 (software suspend), only S3 seems to be affected. 
Comment 6 Rafael J. Wysocki 2006-09-29 03:05:14 UTC
Can you please verify if the problem is still present in 2.6.18?
Comment 7 richlv 2006-09-29 03:13:22 UTC
unfortunately motherboard died for the laptop in question during this time.
i hope somebody has a similar machine or one that also has such a problem.

i could try gaining access to a similar laptop, but that is a relatively small 
chance.

Note You need to log in before you can comment on or make changes to this bug.