From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Sergio Callegari <sergio.callegari@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Possible regression with kernel 6.1.0 freezing (6.0.14 is fine) on haswell laptop (issue identified and patch already available)
Date: Tue, 27 Dec 2022 16:12:42 +0100 [thread overview]
Message-ID: <39289e9a-2afa-1d1e-dda0-7958c66c73c2@leemhuis.info> (raw)
In-Reply-To: <18216b2c-d5f8-ada5-6110-192895772cbf@gmail.com>
On 27.12.22 15:46, Sergio Callegari wrote:
> My issue was
Likely not important, but FWIW: I assume you meant "will be" here, as
unless I'm missing something that patch is not even in mainline (and not
even marked explicitly for backporting to 6.1.y; sigh :-/)
> the one described in
> https://patchwork.kernel.org/project/linux-wireless/patch/20221217085624.52077-1-nbd@nbd.name/
Thx for letting us know. Ideally you want to rely to that mail (see
https://lore.kernel.org/all/20221217085624.52077-1-nbd@nbd.name/
) to let the developer know that their patch fixes your problem.
Ciao, Thorsten
#regzbot fix: wifi: mac80211: fix initialization of rx->link and
rx->link_sta
> On 24/12/2022 06:22, Thorsten Leemhuis wrote:
>> Hi, this is your Linux kernel regression tracker.
>>
>> On 23.12.22 20:51, Sergio Callegari wrote:
>>> On 23/12/2022 15:25, Greg KH wrote:
>>>
>>>> Reported to the distro, but seems serious enough to report here too.
>> Out of curiosity: where?
>>
>>>> Can you use 'git bisect' to find the offending commit?
>>> Must learn a bit more about the distro I am using and what it requires
>>> for a custom kernel but I may try.
>> I'm writing a document I plan to submit for inclusion that might be of
>> help for you:
>>
>> http://www.leemhuis.info/files/misc/How%20to%20quickly%20build%20a%20Linux%20kernel%20%e2%80%94%20The%20Linux%20Kernel%20documentation.html
>>
>> It doesn't cover bisection, I left that for later (and maybe separate
>> document), as I want this one reviewed and merged first.
>>
>> Ciao, Thorsten
>
next prev parent reply other threads:[~2022-12-27 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 14:13 Possible regression with kernel 6.1.0 freezing (6.0.14 is fine) on haswell laptop Sergio Callegari
2022-12-23 14:25 ` Greg KH
2022-12-23 19:51 ` Sergio Callegari
2022-12-24 5:22 ` Thorsten Leemhuis
2022-12-27 14:46 ` Possible regression with kernel 6.1.0 freezing (6.0.14 is fine) on haswell laptop (issue identified and patch already available) Sergio Callegari
2022-12-27 15:12 ` Thorsten Leemhuis [this message]
2022-12-27 15:21 ` Sergio Callegari
2022-12-27 15:28 ` Thorsten Leemhuis
2022-12-27 16:01 ` Sergio Callegari
2022-12-24 7:57 ` Possible regression with kernel 6.1.0 freezing (6.0.14 is fine) on haswell laptop #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=39289e9a-2afa-1d1e-dda0-7958c66c73c2@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=gregkh@linuxfoundation.org \
--cc=regressions@lists.linux.dev \
--cc=sergio.callegari@gmail.com \
--cc=stable@vger.kernel.org \
/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).