netdev - Re: Linux-6.5 iwlwifi crash

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Wed, 5 Jul 2023 13:11:38 -0500
From: Larry Finger <Larry.Finger@...inger.net>
To: Jeff Chua <jeff.chua.linux@...il.com>,
 Linux regressions mailing list <regressions@...ts.linux.dev>
Cc: lkml <linux-kernel@...r.kernel.org>,
 Gregory Greenman <gregory.greenman@...el.com>, Kalle Valo
 <kvalo@...nel.org>, "David S. Miller" <davem@...emloft.net>,
 Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
 Paolo Abeni <pabeni@...hat.com>,
 Linux Wireless <linux-wireless@...r.kernel.org>,
 Linux Networking <netdev@...r.kernel.org>,
 Bagas Sanjaya <bagasdotme@...il.com>
Subject: Re: Linux-6.5 iwlwifi crash

On 7/5/23 06:56, Jeff Chua wrote:
> On Wed, Jul 5, 2023 at 4:37 PM Linux regression tracking (Thorsten
> Leemhuis) <regressions@...mhuis.info> wrote:
>>
>> Hi! Thanks for your report.
>>
>> Side note: is there any relation to the thread[1] you posted this in?
> 
> Sorry, I was just posting to the same email list that I had reported
> about a different wifi list earlier. No relation to this, but it's a
> new wifi issue.
> 
>> Doesn't look like it from here.
>>
>> Side note: discussing multiple unrelated issues in one thread increases
>> the risk a lot that some or all of them are ignored:
>> https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/
>>
>> [1] https://lore.kernel.org/all/ZE0kndhsXNBIb1g7@debian.me/
>>
>> On 05.07.23 09:24, Jeff Chua wrote:
>>> Latest linux-6.4
>>
>> What do you mean by that? From later in the mail it sounds like you mean
>> latest mainline -- is that correct?
> 
> It's from linux git pull. It's 6.5-rc but I didn't write that way
> becuase Linus's branch is still 6.4 ... that 6.5-rc0 or rc1 should
> have more appropriate.
> 
>>> after June 27 crash my whole linux notebook once
>>> iwlwifi is loaded. Anyone seeing this?
>>
>> I haven't heard of any such problems, but that doesn't have to mean much.
> 
>>> Bisect? Or there's a patch for this?
>>>
>>> # modprobe iwlwifi
>>> ... Whole system frozen!
>>>
>>>
>>> Here's my system before the crash ...
>>>
>>> # dmesg
>>> cfg80211: Loading compiled-in X.509 certificates for regulatory database
>>> Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>>> iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
>>> iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
>>> thermal thermal_zone1: failed to read out thermal zone (-61)
>>> iwlwifi 0000:00:14.3: Sorry - debug buffer is only 4096K while you
>>> requested 65536K
>>>
>>> # lspci
>>> 00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi
>>> WiFi (rev 01)
>>>
>>> # linux git log
>>> commit d528014517f2b0531862c02865b9d4c908019dc4 (HEAD -> master,
>>> origin/master, origin/HEAD)
>>> Author: Linus Torvalds <torvalds@...ux-foundation.org>
>>> Date:   Tue Jul 4 15:05:12 2023 -0700
>>>
>>> # lsmodModule                  Size  Used by
>>> iwlmvm                397312  0
>>> mac80211              626688  1 iwlmvm
>>> iwlwifi               307200  1 iwlmvm
>>> cfg80211              413696  3 iwlmvm,iwlwifi,mac80211

Jeff,

Fow what it is worth, my 6.4-git (6.5-rc0?) commit d528014517f2 (pulled today) 
is working OK with iwlmvm. Lspci says my device is

04:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] 
(rev 73)

I think you do need to do a bisection.

Larry