From: Cezary Rojewski <cezary.rojewski@intel.com> To: Dominik Brodowski <linux@dominikbrodowski.net>, tiwai@suse.com Cc: pierre-louis.bossart@linux.intel.com, liam.r.girdwood@linux.intel.com, yang.jie@linux.intel.com, broonie@kernel.org, perex@perex.cz, alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org Subject: Re: snd_hda_intel/sst-acpi sound breakage on suspend/resume since 5.6-rc1 Date: Wed, 18 Mar 2020 10:41:42 +0100 [thread overview] Message-ID: <66c719b3-a66e-6a9f-fab8-721ba48d7ad8@intel.com> (raw) In-Reply-To: <20200318063022.GA116342@light.dominikbrodowski.net> On 2020-03-18 07:30, Dominik Brodowski wrote: > Hi! > > While 5.5.x works fine, mainline as of ac309e7744be (v5.6-rc6+) causes me > some sound-related trouble: after boot, the sound works fine -- but once I > suspend and resume my broadwell-based XPS13, I need to switch to headphone > and back to speaker to hear something. But what I hear isn't music but > garbled output. > > A few dmesg snippets from v5.6-rc6-9-gac309e7744be which might be of > interest. I've highlighted the lines differing from v.5.5.x which might be > of special interest: > Thank you for the report, Dominik. You definitely got our attention. I've checked the market: Dell XPS 13 9343, yes? Once you confirm model id, I'll order a piece immediately to our site. In regard to logs, thanks for highlighting important lines. Build is of 'rc' so bugs can still be in plenty - any reason for switching to cutting-edge kernel on production stuff? Our CI didn't detect any anomalies yet as it is running on 5.5. I'll direct your ticket on todays meeting. On the first look, issue seems to be connected with recent changes to /drivers/dma/dmaengine.c. DesignWare DMA controller drv - which HSW/BDW makes use of - might not have been updated accordingly. Will dig further on that. One more, just to make it clear for the rest of the viewers: > haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 > haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) Back in the ancient days of DSP (HSW/BDW are actually the very first audio DSP hws for Intel) topology was part of FW - SW could not configure it and probably that's why library IntcPP01 is attempted to be loaded on every boot, even if it's not part of configuration for given hw. Maybe we could make it quieter though.. > > (these last two messages already are printed a couple of time after boot, and then > again during a suspend/resume cycle. On v.5.5.y, there are similar messages > "no context buffer need to restore!"). Everything is built-in, no modules > are loaded. > > Unfortunately, I cannot bisect this issue easily -- i915 was broken for > quite some time on this system[*], prohibiting boot... Hmm, sounds like that issue is quite old. DSP for Haswell and Broadwell is available for I2S devices only, so this relates directly to legacy HDA driver. Compared to Skylake+, HDAudio controller for older platforms is found within GPU. My advice is to notify the DRM guys about this issue. Takashi, are you aware of problems with HDMI on HSW/ BDW or should I just loop Jani and other DRM peps here? Czarek
WARNING: multiple messages have this Message-ID (diff)
From: Cezary Rojewski <cezary.rojewski@intel.com> To: Dominik Brodowski <linux@dominikbrodowski.net>, tiwai@suse.com Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org, yang.jie@linux.intel.com, pierre-louis.bossart@linux.intel.com, liam.r.girdwood@linux.intel.com, broonie@kernel.org Subject: Re: snd_hda_intel/sst-acpi sound breakage on suspend/resume since 5.6-rc1 Date: Wed, 18 Mar 2020 10:41:42 +0100 [thread overview] Message-ID: <66c719b3-a66e-6a9f-fab8-721ba48d7ad8@intel.com> (raw) In-Reply-To: <20200318063022.GA116342@light.dominikbrodowski.net> On 2020-03-18 07:30, Dominik Brodowski wrote: > Hi! > > While 5.5.x works fine, mainline as of ac309e7744be (v5.6-rc6+) causes me > some sound-related trouble: after boot, the sound works fine -- but once I > suspend and resume my broadwell-based XPS13, I need to switch to headphone > and back to speaker to hear something. But what I hear isn't music but > garbled output. > > A few dmesg snippets from v5.6-rc6-9-gac309e7744be which might be of > interest. I've highlighted the lines differing from v.5.5.x which might be > of special interest: > Thank you for the report, Dominik. You definitely got our attention. I've checked the market: Dell XPS 13 9343, yes? Once you confirm model id, I'll order a piece immediately to our site. In regard to logs, thanks for highlighting important lines. Build is of 'rc' so bugs can still be in plenty - any reason for switching to cutting-edge kernel on production stuff? Our CI didn't detect any anomalies yet as it is running on 5.5. I'll direct your ticket on todays meeting. On the first look, issue seems to be connected with recent changes to /drivers/dma/dmaengine.c. DesignWare DMA controller drv - which HSW/BDW makes use of - might not have been updated accordingly. Will dig further on that. One more, just to make it clear for the rest of the viewers: > haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 > haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) Back in the ancient days of DSP (HSW/BDW are actually the very first audio DSP hws for Intel) topology was part of FW - SW could not configure it and probably that's why library IntcPP01 is attempted to be loaded on every boot, even if it's not part of configuration for given hw. Maybe we could make it quieter though.. > > (these last two messages already are printed a couple of time after boot, and then > again during a suspend/resume cycle. On v.5.5.y, there are similar messages > "no context buffer need to restore!"). Everything is built-in, no modules > are loaded. > > Unfortunately, I cannot bisect this issue easily -- i915 was broken for > quite some time on this system[*], prohibiting boot... Hmm, sounds like that issue is quite old. DSP for Haswell and Broadwell is available for I2S devices only, so this relates directly to legacy HDA driver. Compared to Skylake+, HDAudio controller for older platforms is found within GPU. My advice is to notify the DRM guys about this issue. Takashi, are you aware of problems with HDMI on HSW/ BDW or should I just loop Jani and other DRM peps here? Czarek
next prev parent reply other threads:[~2020-03-18 9:41 UTC|newest] Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-18 6:30 snd_hda_intel/sst-acpi sound breakage on suspend/resume since 5.6-rc1 Dominik Brodowski 2020-03-18 9:41 ` Cezary Rojewski [this message] 2020-03-18 9:41 ` Cezary Rojewski 2020-03-18 9:57 ` Dominik Brodowski 2020-03-18 9:57 ` Dominik Brodowski 2020-03-18 10:05 ` Cezary Rojewski 2020-03-18 10:05 ` Cezary Rojewski 2020-03-18 10:19 ` Dominik Brodowski 2020-03-18 10:19 ` Dominik Brodowski 2020-03-18 10:49 ` Keyon Jie 2020-03-18 10:49 ` Keyon Jie 2020-03-18 12:39 ` Dominik Brodowski 2020-03-18 12:39 ` Dominik Brodowski 2020-03-18 15:13 ` Pierre-Louis Bossart 2020-03-18 15:13 ` Pierre-Louis Bossart 2020-03-18 16:20 ` Dominik Brodowski 2020-03-18 16:20 ` Dominik Brodowski 2020-03-18 17:08 ` Pierre-Louis Bossart 2020-03-18 17:08 ` Pierre-Louis Bossart 2020-03-18 17:18 ` Curtis Malainey 2020-03-18 17:19 ` Dominik Brodowski 2020-03-18 17:19 ` Dominik Brodowski 2020-03-18 17:25 ` Curtis Malainey 2020-03-18 19:13 ` Ross Zwisler 2020-03-18 19:13 ` Ross Zwisler 2020-03-18 17:29 ` Pierre-Louis Bossart 2020-03-18 17:29 ` Pierre-Louis Bossart 2020-03-18 17:35 ` Cezary Rojewski 2020-03-18 18:27 ` Cezary Rojewski 2020-03-18 18:27 ` Cezary Rojewski 2020-03-18 19:22 ` Dominik Brodowski 2020-03-18 19:22 ` Dominik Brodowski 2020-03-18 20:43 ` Cezary Rojewski 2020-03-18 20:43 ` Cezary Rojewski 2020-03-18 21:52 ` Dominik Brodowski 2020-03-18 21:52 ` Dominik Brodowski 2020-03-18 22:20 ` Cezary Rojewski 2020-03-18 22:20 ` Cezary Rojewski 2020-03-19 13:00 ` Dominik Brodowski 2020-03-19 13:00 ` Dominik Brodowski 2020-03-19 13:17 ` Cezary Rojewski 2020-03-19 13:17 ` Cezary Rojewski 2020-03-19 13:41 ` Mark Brown 2020-03-19 13:41 ` Mark Brown 2020-03-19 15:48 ` Cezary Rojewski 2020-03-19 15:48 ` Cezary Rojewski 2020-03-19 16:51 ` Dominik Brodowski 2020-03-19 16:51 ` Dominik Brodowski 2020-03-19 17:21 ` Pierre-Louis Bossart 2020-03-19 17:21 ` Pierre-Louis Bossart 2020-03-19 17:35 ` Mark Brown 2020-03-19 17:35 ` Mark Brown 2020-03-20 3:21 ` Keyon Jie 2020-03-20 3:21 ` Keyon Jie 2020-03-19 17:41 ` Cezary Rojewski 2020-03-19 17:41 ` Cezary Rojewski 2020-03-19 17:33 ` Cezary Rojewski 2020-03-19 17:33 ` Cezary Rojewski 2020-03-19 17:45 ` Cezary Rojewski 2020-03-19 17:45 ` Cezary Rojewski 2020-03-19 18:24 ` Dominik Brodowski 2020-03-19 18:24 ` Dominik Brodowski 2020-03-19 18:35 ` Cezary Rojewski 2020-03-19 18:35 ` Cezary Rojewski 2020-03-19 19:05 ` Pierre-Louis Bossart 2020-03-19 19:05 ` Pierre-Louis Bossart 2020-03-30 10:23 ` Dominik Brodowski 2020-03-30 10:23 ` Dominik Brodowski 2020-03-30 11:10 ` Cezary Rojewski 2020-03-30 11:10 ` Cezary Rojewski 2020-03-30 11:39 ` Mark Brown 2020-03-30 11:39 ` Mark Brown 2020-03-30 15:37 ` Pierre-Louis Bossart 2020-03-30 15:37 ` Pierre-Louis Bossart
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=66c719b3-a66e-6a9f-fab8-721ba48d7ad8@intel.com \ --to=cezary.rojewski@intel.com \ --cc=alsa-devel@alsa-project.org \ --cc=broonie@kernel.org \ --cc=liam.r.girdwood@linux.intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@dominikbrodowski.net \ --cc=perex@perex.cz \ --cc=pierre-louis.bossart@linux.intel.com \ --cc=tiwai@suse.com \ --cc=yang.jie@linux.intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.