Summary: | The audio playback does not work anymore after suspend & resume on ASUS E406MA | ||
---|---|---|---|
Product: | DRI | Reporter: | jian-hong |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | major | ||
Priority: | medium | CC: | intel-gfx-bugs, tiwai, ville.syrjala |
Version: | XOrg git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | Triaged | ||
i915 platform: | GLK | i915 features: | display/audio |
Attachments: |
Description
jian-hong
2019-06-14 05:27:03 UTC
Created attachment 144538 [details] The dmesg with drm.debug=0xe and snd_hda_intel.probe_mask=0x01 in boot command I also follow Takashi's comment [1] After add "snd_hda_intel.probe_mask=0x01" to boot command, the built-in audio (including internal speaker, mic and headset) works after resume, and there is no error message mentioned in comment #0. However, the HDMI audio is not listed and cannot be used. [1] https://bugzilla.kernel.org/show_bug.cgi?id=203623#c5 Reporter, you have tried to verify the issue with drmtip (https://cgit.freedesktop.org/drm-tip)? If so, can you attach the dmesg? Created attachment 144540 [details] The dmesg with drm-tip tree and drm.debug=0xe in boot command (In reply to Lakshmi from comment #2) I tried with https://cgit.freedesktop.org/drm-tip The attachment is the corresponding dmesg. The test result is same as the comment: the audio works after resume. https://bugzilla.kernel.org/show_bug.cgi?id=203623#c6 Hmm. I do see [ 57.460391] [drm:intel_dump_cdclk_state [i915]] Changing CDCLK to 79200 kHz, VCO 633600 kHz, ref 19200 kHz, bypass 19200 kHz, voltage level 4 in the logs. Ah, that's for the case when we disable all display pipes (glk_calc_cdclk(0) cases). Apparently we didn't add the audio cdclk requirement to those code paths :( The backports went in I believe. We can close this. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.