From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Keyon Jie <yang.jie@linux.intel.com>,
alsa-devel@alsa-project.org, curtis@malainey.com,
linux-kernel@vger.kernel.org, tiwai@suse.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 20:22:13 +0100 [thread overview]
Message-ID: <20200318192213.GA2987@light.dominikbrodowski.net> (raw)
In-Reply-To: <e49eec28-2037-f5db-e75b-9eadf6180d81@intel.com>
On Wed, Mar 18, 2020 at 07:27:58PM +0100, Cezary Rojewski wrote:
> On 2020-03-18 17:20, Dominik Brodowski wrote:
> > On Wed, Mar 18, 2020 at 10:13:54AM -0500, Pierre-Louis Bossart wrote:
> > > > > > 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.
>
> >
> > I had (see 18d78b64fddc), but not any more in years (and I'd like to keep
> > using I2S, which has worked flawlessly in these years).
> >
>
> Due to pandemic I'm working remotely and right now won't be able to test
> audio quality so focusing on the stream==NULL issue. And thus we got to help
> each other out : )
Sure, and thanks for taking a look at this!
> Could you verify issue reproduces on 5.6.0-rc1 on your machine?
It reproduces on 5.6.0-rc1 + i915-bugfix. I'm trying to bisect it further in
the background, but that may take quite some time.
Thanks,
Dominik
next prev parent reply other threads:[~2020-03-18 19:22 UTC|newest]
Thread overview: 37+ 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
2020-03-18 9:57 ` Dominik Brodowski
2020-03-18 10:05 ` Cezary Rojewski
2020-03-18 10:19 ` Dominik Brodowski
2020-03-18 10:49 ` Keyon Jie
2020-03-18 12:39 ` Dominik Brodowski
2020-03-18 15:13 ` Pierre-Louis Bossart
2020-03-18 16:20 ` Dominik Brodowski
2020-03-18 17:08 ` Pierre-Louis Bossart
2020-03-18 17:19 ` Dominik Brodowski
2020-03-18 17:29 ` Pierre-Louis Bossart
2020-03-18 17:35 ` Cezary Rojewski
[not found] ` <CAOReqxjmUCGX18y_XW_sjcU2xWha_+wJ7L+SuzJ5ZrOddCfZkw@mail.gmail.com>
2020-03-18 19:13 ` Ross Zwisler
2020-03-18 18:27 ` Cezary Rojewski
2020-03-18 19:22 ` Dominik Brodowski [this message]
2020-03-18 20:43 ` Cezary Rojewski
2020-03-18 21:52 ` Dominik Brodowski
2020-03-18 22:20 ` Cezary Rojewski
2020-03-19 13:00 ` Dominik Brodowski
2020-03-19 13:17 ` Cezary Rojewski
2020-03-19 13:41 ` Mark Brown
2020-03-19 15:48 ` Cezary Rojewski
2020-03-19 16:51 ` Dominik Brodowski
2020-03-19 17:21 ` Pierre-Louis Bossart
2020-03-19 17:35 ` Mark Brown
2020-03-20 3:21 ` Keyon Jie
2020-03-19 17:41 ` Cezary Rojewski
2020-03-19 17:33 ` Cezary Rojewski
2020-03-19 17:45 ` Cezary Rojewski
2020-03-19 18:24 ` Dominik Brodowski
2020-03-19 18:35 ` Cezary Rojewski
2020-03-19 19:05 ` Pierre-Louis Bossart
2020-03-30 10:23 ` Dominik Brodowski
2020-03-30 11:10 ` Cezary Rojewski
2020-03-30 11:39 ` Mark Brown
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=20200318192213.GA2987@light.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=curtis@malainey.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).