linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Exner <dex@dragonslave.de>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
	Dmitry Osipenko <dmitry.osipenko@collabora.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: Regression in v5.19-rc4 Sound Distortion
Date: Wed, 13 Jul 2022 12:12:48 +0200	[thread overview]
Message-ID: <9ebfb3d5-ac2d-e664-8b71-dfc1fd6d6362@dragonslave.de> (raw)
In-Reply-To: <22805e12-7144-037f-c58c-4bc182d27919@leemhuis.info>

horsten Leemhuis wrote:
> On 12.07.22 18:35, Dmitry Osipenko wrote:
>> On 7/12/22 19:02, Daniel Exner wrote:
>>
>>> Since  v5.19-rc4 this box got some *loud* distorting sound on boot and
>>> after some time without any sound if something plays sound again from
>>> the integrated speakers in my monitor.
>>>
>>> I managed to bisect this down to:
>>>
>>>> commit 202773260023b56e868d09d13d3a417028f1ff5b
>>>> Author: Dmitry Osipenko <dmitry.osipenko@collabora.com>
>>>> Date:   Fri Jun 17 15:24:02 2022 +0300
>>>>
>>>>     PM: hibernate: Use kernel_can_power_off()
>>> Reverting that commit on top of v5.19-rc6 does indeed fix the problem here.
>> You're saying that the problem is on boot, but this patch is about
>> suspension to disk, which has nothing to do neither with the boot nor
>> with power-off. I'm afraid your bisection is incorrect.
> After quickly looking at the code this looks appropriate, but why does
> reverting that commit help then? That's a bit odd. Daniel: are you maybe
> using suspend-to-disk and forgot to mention it?

No, I am not. But it seems Dmitry was right, at some point I bisected 
wrong by declaring some point good too early because I didn't have the 
bug on boot.

Perhaps I have two effects here: some bug resulting in sound distortion 
and some bug triggering that faster.


I will redo the bisection, but I fear it will take some time.


Greetings

Daniel


  reply	other threads:[~2022-07-13 10:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 16:02 Regression in v5.19-rc4 Sound Distortion Daniel Exner
2022-07-12 16:35 ` Dmitry Osipenko
2022-07-13  9:47   ` Thorsten Leemhuis
2022-07-13 10:12     ` Daniel Exner [this message]
2022-07-14  5:22       ` Thorsten Leemhuis
2022-07-13  6:10 ` Thorsten Leemhuis
2022-09-16 21:34 ` Daniel Exner
2022-09-18 10:02   ` Regression in v5.19-rc4 Sound Distortion #forregzbot Thorsten Leemhuis

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=9ebfb3d5-ac2d-e664-8b71-dfc1fd6d6362@dragonslave.de \
    --to=dex@dragonslave.de \
    --cc=dmitry.osipenko@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=regressions@leemhuis.info \
    /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).