mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Eliad Peller <eliad@wizery.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	Gregory Greenman <gregory.greenman@intel.com>,
	Linus Lotz <register+kernelbugzilla@lotz.li>,
	Darrell Enns <darrell@darrellenns.com>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: Fwd: iwlwifi: rfkill locking up kernel 6.5.12, 6.6.2
Date: Mon, 4 Dec 2023 09:12:39 +0100	[thread overview]
Message-ID: <b5063044-e82d-4f73-a1fa-db6eeacd0498@leemhuis.info> (raw)
In-Reply-To: <af62295b-b757-49ec-83ce-9d3ef93e24af@leemhuis.info>

On 02.12.23 07:07, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 30.11.23 09:23, Bagas Sanjaya wrote:
>>
>> I notice a regression report on Bugzilla [1]. Quoting from it:
>>
>>> Rfkilling the iwlwifi can lock up my machine, rfkill will not
>>> respond and other networking related things (e.g. ip a or ip r) I
>>> see this on 6.5.12 and 6.6.2 (fedora kernel). On 6.5.11 it does not
>>> lockup AFAICT, but also shows kernel oops. WiFi Hardware: AC 8265
>>
>> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=218206
> 
> TWIMC: More people that seem to be affected by the same problem joined
> the report. And one user performed a bisection on 6.6.y. According to
> that the problem is caused by a 6.6.y-backport of 37fb29bd1f90f1 ("wifi:
> iwlwifi: pcie: synchronize IRQs before NAPI") [v6.7-rc1] from Johannes.
> 
> Another reported user also stated that the same problem happens on
> 6.7-rc3 as well. No confirmation yet that 37fb29bd1f90f1 causes it
> there, but it seems likely.

TWIMC, it was now confirmed that reverting 37fb29bd1f90f1 in 6.7-rc
fixes the problem.

The bugzilla ticket has the details; it's sadly all a bit mess (it was
afaics actually a gentoo user that confirmed the above in a downstream
bug tracker [https://bugs.gentoo.org/918128#c21] and a gentoo kernel dev
forwarded the result to our bugzilla...).

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

  reply	other threads:[~2023-12-04  8:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30  8:23 Bagas Sanjaya
2023-12-02  6:07 ` Linux regression tracking (Thorsten Leemhuis)
2023-12-04  8:12   ` Thorsten Leemhuis [this message]
2023-12-23  9:31 ` Linux regression tracking #update (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=b5063044-e82d-4f73-a1fa-db6eeacd0498@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=bagasdotme@gmail.com \
    --cc=darrell@darrellenns.com \
    --cc=eliad@wizery.com \
    --cc=gregory.greenman@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=register+kernelbugzilla@lotz.li \
    --cc=regressions@lists.linux.dev \
    /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

all inboxes | Powered by JetHome®