Red Hat Bugzilla – Bug 427269
PPORT:RHEL51: Audio does not work after S3/S4 on Dell Precision M4300/M6300
Last modified: 2010-10-22 17:28:06 EDT
Description of problem:
With RHEL5.1 , upon resuming from S3/S4, audio does not work on M4300 and
Try , for example, "aplay /usr/share/sounds/pop.wav". No sound could be heard.
Version-Release number of selected component (if applicable):
alsa driver version 1.0.14rc3
Steps to Reproduce:
2. Run "aplay /usr/share/sounds/pop.wav"
Audio should work
I have looked into the issue a little and found out the followings:
1) The issue is resolved with alsa driver version 1.0.15
2) The issue can also be resolved if you rmmod snd-hda-intel before
suspending and modprobe it on resume.
The fix in alsa driver 1.0.15 for this issue needs to be backported to
I used the RHEL-5.1 2.6.18-53 kernel on both the M4300 and M6300 and heard sound
via the headphone jack after resuming from s3 and s4 BUT not via the built-in
speakers so the scope of this bug is somewhat reduced.
A fix for bz254067 was added to RHEL5.2 that handles suspend/resume and I heard
sound through the speakers with this patch in place. Thus, I would ask that this
bugzilla be tested with RHEL5.2.
Tested with the kernel below as mentioned by John in comment#1:
Confirming that the kernel above resolves the issue. This is a must have for
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Removing this one as an exception as we are just waiting on test results.
Please close out as currentrelease when the results come back, (positive).
This request was previously evaluated by Red Hat Product Management
for inclusion in the current Red Hat Enterprise Linux release, but
Red Hat was unable to resolve it in time. This request will be
reviewed for a future Red Hat Enterprise Linux release.
Could we get this verified in a 5.2 snapshot release and get this closed as
"currentrelease" if fixed? It keeps drawing unwarranted attention.
Verified as fixed in RHEL5.2 Snapshot3.
Since this was found not to fail in RHEL5.2 (see comment #9), I am closing this
as CURRENTRELEASE. The fix for this bugzilla was included in the fix for
bz254067 which has just been verified as working as well.