From: Paul Grandperrin <paul.grandperrin@gmail.com>
To: "Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel.com>
Cc: "Greenman, Gregory" <gregory.greenman@intel.com>,
linux-wireless@vger.kernel.org
Subject: RE: Kernel oops in iwlwifi 6.6.3 with AX210 while scanning (looks like firmware bug)
Date: Thu, 07 Dec 2023 12:31:53 +0100 [thread overview]
Message-ID: <51OA5S.GFY9YXXZJUYI@gmail.com> (raw)
In-Reply-To: <MW5PR11MB5810C544ACFD6CB471A1CF1DA38BA@MW5PR11MB5810.namprd11.prod.outlook.com>
Sorry, last time I openned a bug there, there was no answers, only the
mailing list was monitored.
I opened https://bugzilla.kernel.org/show_bug.cgi?id=218239
On Thu, Dec 7 2023 at 10:16:25 +00:00:00, "Korenblit, Miriam Rachel"
<miriam.rachel.korenblit@intel.com> wrote:
>
>> -----Original Message-----
>> From: Paul Grandperrin <paul.grandperrin@gmail.com>
>> Sent: Thursday, December 07, 2023 03:00
>> To: Greenman, Gregory <gregory.greenman@intel.com>
>> Cc: linux-wireless@vger.kernel.org
>> Subject: Kernel oops in iwlwifi 6.6.3 with AX210 while scanning
>> (looks like
>> firmware bug)
>>
>> Hi!
>>
>> My system was running fine, no errors in the logs, and then it
>> started to happen,
>> an infinite flow of oops in the kernel logs.
>>
>> The bug seems to happen in "__ieee80211_scan_completed" and it
>> seems to
>> involve the firmware: "Microcode SW error detected. Restarting",
>> "ieee80211 phy0: Hardware restart was requested" and "iwlwifi
>> 0000:02:00.0: FW error in SYNC CMD SCAN_REQ_UMAC".
>>
>> Since then, the iwlwifi module oops all the time, even after
>> unloading and
>> reloading it.
>>
>> My system:
>> NixOS 23.11
>> Linux 6.6.3
>> Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 firmware version:
>> 83.e8f84e98.0 ty-
>> a0-gf-a0-83.ucode
>>
>> Here's the logs attached and more info about my system.
>>
>> I tried very hard to get decode_stacktrace.sh to works with module
>> symbols but
>> the NixOS file hierarchy makes things quite difficult.
>> I can try again if needed.
>>
>>
>> Sincerly,
>> Paul Grandperrin
>>
>>
>>
>>
>>
>>
>
> Hi Paul,
>
> Can you please open a bug in Bugzilla, so we can handle it there?
>
> Please attach there a sniffer capture and a trace-cmd log.
> This is how to:
> https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging
>
> Thanks,
> Miri
>
>
prev parent reply other threads:[~2023-12-07 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 1:00 Kernel oops in iwlwifi 6.6.3 with AX210 while scanning (looks like firmware bug) Paul Grandperrin
2023-12-07 10:16 ` Korenblit, Miriam Rachel
2023-12-07 11:31 ` Paul Grandperrin [this message]
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=51OA5S.GFY9YXXZJUYI@gmail.com \
--to=paul.grandperrin@gmail.com \
--cc=gregory.greenman@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
/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).