[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ddc25d-9c80-399f-3378-aa5594318dce@leemhuis.info>
Date: Wed, 13 Jul 2022 08:10:01 +0200
From: Thorsten Leemhuis <regressions@...mhuis.info>
To: Daniel Exner <dex@...gonslave.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Dmitry Osipenko <dmitry.osipenko@...labora.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Cc: "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>
Subject: Re: Regression in v5.19-rc4 Sound Distortion
[TLDR: I'm adding this regression report to the list of tracked
regressions; all text from me you find below is based on a few templates
paragraphs you might have encountered already already in similar form.]
Hi, this is your Linux kernel regression tracker.
On 12.07.22 18: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@...labora.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.
>
> Any ideas?
CCing the regression mailing list, as it should be in the loop for all
regressions, as explained here:
https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html
Thanks for the report. To be sure below issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
tracking bot:
#regzbot ^introduced 202773260023b56e868d09d13d3a417028f1f
#regzbot title PM: hibernate: Sound Distortion on boot
#regzbot ignore-activity
This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply -- ideally with also
telling regzbot about it, as explained here:
https://linux-regtracking.leemhuis.info/tracked-regression/
Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report (the mail this one replies to), as explained for
in the Linux kernel's documentation; above webpage explains why this is
important for tracked regressions.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
Powered by blists - more mailing lists