lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <fdca8918-730c-c36d-a3ca-4c95f16d1e8e@leemhuis.info>
Date:   Thu, 27 Oct 2022 07:37:34 +0200
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>
Cc:     alsa-devel@...a-project.org,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>, Takashi Iwai <tiwai@...e.de>
Subject: Re: [Regression] Bug 216613 - Sound stopped working with v6.0.3 on
 Lenovo T14 Gen2i: ASoC: error at snd_soc_component_probe

[CCing Takashi in case he is interested in this and/or wants to make my
life as regression tracker a little easier in the future]

On 26.10.22 22:41, Pierre-Louis Bossart wrote:
> On 10/26/22 07:08, Thorsten Leemhuis wrote:
>> On 22.10.22 08:35, Thorsten Leemhuis wrote:
>>>
>>> I noticed a regression report in bugzilla.kernel.org. As many (most?)
>>> kernel developer don't keep an eye on it, I decided to forward it by
>>> mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216613 :
>>>
>>>> After upgrade kernel from 6.0.2 to 6.0.3 on Lenovo T14 Gen2i, sound stopped working.
>>>> dmesg:
>>>>
>>>> paź 21 21:11:45 kernel: snd_hda_codec_hdmi ehdaudio0D2: failed to create hda codec -12
>>>> paź 21 21:11:45 kernel: snd_hda_codec_hdmi ehdaudio0D2: ASoC: error at snd_soc_component_probe on ehdaudio0D2: -12
>>>> paź 21 21:11:45 kernel: skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: failed to instantiate card -12
>>>>
>>
>> #regzbot introduced: 7494e2e6c55ed19
>> #regzbot fixed-by: 02356311982b
> 
> Revert on its way:
> https://lore.kernel.org/r/20221024143931.15722-1-tiwai@suse.de

Thx, in fact it was already merged:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.0.y&id=02356311982bbb117310a27985fa8938e82c0b6e

That "#regzbot fixed-by: 02356311982b" above told my regression tracking
bot about the commit. I sadly had to do that manually, as Takashi used
the non-standard "BugLink" tag to link to the report, which Linus
doesn't want:

https://lore.kernel.org/all/CAHk-=wgs38ZrfPvy=nOwVkVzjpM3VFU1zobP37Fwd_h9iAD5JQ@mail.gmail.com/

To quote: ```please stop making up random tags that make no sense. Just
use "Link:"```

Maybe regzbot nevertheless should resolve a tracked regression as
resolved, if it sees BugLink to a tracked regression. But I think the
real solution is: checkpatch.pl should complain.

Ciao, Thorsten

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ