Summary: | [i915] [SKL] Unclaimed register detected | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Direx <direx> | ||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||
Version: | unspecified | ||||||
Hardware: | x86-64 (AMD64) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | SKL | i915 features: | display/audio | ||||
Attachments: |
|
Description
Direx
2016-05-24 11:12:06 UTC
Created attachment 124020 [details]
Output of intel_reg dump
HSW_AUD_CHICKENBIT is accessed without holding an audio power domain reference. Could you try the following: diff --git a/sound/hda/hdac_i915.c b/sound/hda/hdac_i915.c index c9af022..c6552f3c 100644 --- a/sound/hda/hdac_i915.c +++ b/sound/hda/hdac_i915.c @@ -101,7 +101,9 @@ EXPORT_SYMBOL_GPL(snd_hdac_display_power); #define CONTROLLER_IN_GPU(pci) (((pci)->device == 0x0a0c) || \ ((pci)->device == 0x0c0c) || \ ((pci)->device == 0x0d0c) || \ - ((pci)->device == 0x160c)) + ((pci)->device == 0x160c) || \ + ((pci)->device == 0xa170) || \ + ((pci)->device == 0x9d70)) /** * snd_hdac_i915_set_bclk - Reprogram BCLK for HSW/BDW If it doesn't fix it, could you provide the PCI ID for your HDA device: $ lspci -nn -s 0:1f.3; lspci -nn -s 0:3 I have tried your patch against drm-intel-nightly, but unfortunately it does not fix the issue. The PCI id of my card is correct, though: 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d70] (rev 21) I can now also describe how to reproduce the issue (it is unrelated to suspend): 1. Boot system normally 2. Play back any sound 3. Run `powertop` and apply all "optimizations" (I think the `snd_hda_intel.power_save` optimization is not enough) 4. Wait for a few seconds 5. Play back any sound -> the warning message appears in the system log BTW: The register involved in this is always 0x65f10 |
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.