* Bug 215635 - iwlwifi: Firmware crash with firmware 36.ca7b901d.0 (8265-36.ucode) @ 2022-03-14 11:51 Thorsten Leemhuis 2022-06-16 18:58 ` Jakub Kicinski 0 siblings, 1 reply; 5+ messages in thread From: Thorsten Leemhuis @ 2022-03-14 11:51 UTC (permalink / raw) To: golan.ben.ami, Luca Coelho; +Cc: Udo Steinberg, linux-wireless, regressions Hi, this is your Linux kernel regression tracker. I noticed a regression report in bugzilla.kernel.org that afaics isn't properly handled, that's why I decided to forward it to the lists and a few relevant people to the CC. To quote from https://bugzilla.kernel.org/show_bug.cgi?id=215635 : > Seeing the following firmware crash frequently with > firmware-version: 36.ca7b901d.0 8265-36.ucode > > [...] > > Afterwards iwlwifi is entirely unusable, i.e. the hardware does not recover. > I have not been able to observe the problem with 5.15.x so far. > > The problem manifests either by Wi-Fi becoming entirely unresponsive (not even ping to gateway works anymore) or by producing a firmware crash. > > In response to #3, the problem was most recently observed as a firmware crash on Linux 5.16.13. HW is Intel Corporation Wireless 8265 / 8275 (rev 78) (Windstorm Peak) and firmware version 36.ca7b901d.0 8265-36.ucode. > > I'm attaching the dmesg output from 5.16.13 (with the TWT patch mentioned above applied) which includes a firmware crash. Could somebody take a look into this? Or was this discussed somewhere else already? Or even fixed? Anyway, to get this tracked: #regzbot introduced: v5.15..v5.16 #regzbot from: Udo Steinberg <udo@hypervisor.org> #regzbot title: wireless: iwlwifi: Firmware crash frequently with firmware 36.ca7b901d.0 (8265-36.ucode) #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215635 Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I'm getting a lot of reports on my table. I can only look briefly into most of them and lack knowledge about most of the areas they concern. I thus unfortunately will sometimes get things wrong or miss something important. I hope that's not the case here; if you think it is, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight. -- Additional information about regzbot: If you want to know more about regzbot, check out its web-interface, the getting start guide, and the references documentation: https://linux-regtracking.leemhuis.info/regzbot/ https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md The last two documents will explain how you can interact with regzbot yourself if your want to. Hint for reporters: when reporting a regression it's in your interest to CC the regression list and tell regzbot about the issue, as that ensures the regression makes it onto the radar of the Linux kernel's regression tracker -- that's in your interest, as it ensures your report won't fall through the cracks unnoticed. Hint for developers: you normally don't need to care about regzbot once it's involved. Fix the issue as you normally would, just remember to include 'Link:' tag in the patch descriptions pointing to all reports about the issue. This has been expected from developers even before regzbot showed up for reasons explained in 'Documentation/process/submitting-patches.rst' and 'Documentation/process/5.Posting.rst'. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bug 215635 - iwlwifi: Firmware crash with firmware 36.ca7b901d.0 (8265-36.ucode) 2022-03-14 11:51 Bug 215635 - iwlwifi: Firmware crash with firmware 36.ca7b901d.0 (8265-36.ucode) Thorsten Leemhuis @ 2022-06-16 18:58 ` Jakub Kicinski 2022-06-17 6:38 ` Thorsten Leemhuis 0 siblings, 1 reply; 5+ messages in thread From: Jakub Kicinski @ 2022-06-16 18:58 UTC (permalink / raw) To: golan.ben.ami, Luca Coelho, Johannes Berg Cc: Thorsten Leemhuis, Udo Steinberg, linux-wireless, regressions On Mon, 14 Mar 2022 12:51:38 +0100 Thorsten Leemhuis wrote: > Hi, this is your Linux kernel regression tracker. > > I noticed a regression report in bugzilla.kernel.org that afaics isn't > properly handled, that's why I decided to forward it to the lists and a > few relevant people to the CC. To quote from > https://bugzilla.kernel.org/show_bug.cgi?id=215635 : > > > Seeing the following firmware crash frequently with > > firmware-version: 36.ca7b901d.0 8265-36.ucode > > > > [...] > > > > Afterwards iwlwifi is entirely unusable, i.e. the hardware does not recover. > > > I have not been able to observe the problem with 5.15.x so far. > > > > The problem manifests either by Wi-Fi becoming entirely unresponsive (not even ping to gateway works anymore) or by producing a firmware crash. > > > > In response to #3, the problem was most recently observed as a firmware crash on Linux 5.16.13. HW is Intel Corporation Wireless 8265 / 8275 (rev 78) (Windstorm Peak) and firmware version 36.ca7b901d.0 8265-36.ucode. > > > > I'm attaching the dmesg output from 5.16.13 (with the TWT patch mentioned above applied) which includes a firmware crash. > > Could somebody take a look into this? Or was this discussed somewhere > else already? Or even fixed? Any progress / outputs on this one? Folks are reporting it's still happening on Fedora 36 w/ 5.17.13. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bug 215635 - iwlwifi: Firmware crash with firmware 36.ca7b901d.0 (8265-36.ucode) 2022-06-16 18:58 ` Jakub Kicinski @ 2022-06-17 6:38 ` Thorsten Leemhuis 2022-06-17 14:50 ` Jakub Kicinski 2022-07-14 7:37 ` Thorsten Leemhuis 0 siblings, 2 replies; 5+ messages in thread From: Thorsten Leemhuis @ 2022-06-17 6:38 UTC (permalink / raw) To: Jakub Kicinski, golan.ben.ami, Luca Coelho, Johannes Berg, Gregory Greenman Cc: Udo Steinberg, linux-wireless, regressions CCing Gregory, which became iwlwifi maintainer inbetween. On 16.06.22 20:58, Jakub Kicinski wrote: > On Mon, 14 Mar 2022 12:51:38 +0100 Thorsten Leemhuis wrote: >> Hi, this is your Linux kernel regression tracker. >> >> I noticed a regression report in bugzilla.kernel.org that afaics isn't >> properly handled, that's why I decided to forward it to the lists and a >> few relevant people to the CC. To quote from >> https://bugzilla.kernel.org/show_bug.cgi?id=215635 : BTW, Udo recently confirmed there that the issue still happens on 5.18. >>> Seeing the following firmware crash frequently with >>> firmware-version: 36.ca7b901d.0 8265-36.ucode >>> >>> [...] >>> >>> Afterwards iwlwifi is entirely unusable, i.e. the hardware does not recover. >> >>> I have not been able to observe the problem with 5.15.x so far. >>> >>> The problem manifests either by Wi-Fi becoming entirely unresponsive (not even ping to gateway works anymore) or by producing a firmware crash. >>> >>> In response to #3, the problem was most recently observed as a firmware crash on Linux 5.16.13. HW is Intel Corporation Wireless 8265 / 8275 (rev 78) (Windstorm Peak) and firmware version 36.ca7b901d.0 8265-36.ucode. >>> >>> I'm attaching the dmesg output from 5.16.13 (with the TWT patch mentioned above applied) which includes a firmware crash. >> >> Could somebody take a look into this? Or was this discussed somewhere >> else already? Or even fixed? > > Any progress / outputs on this one? Folks are reporting it's still > happening on Fedora 36 w/ 5.17.13. Jakub, thx for bringing this up, I had "look into this again" on my todo list for some time already. Out of interest: where where those reports? Besides the one the quoted mail is about (https://bugzilla.kernel.org/show_bug.cgi?id=215635 ) I'm aware of two other reports that look similar and might or might not be related (hard to tell without domain knowledge, I guess it might be just similar symptoms): https://bugzilla.kernel.org/show_bug.cgi?id=215697 https://bugzilla.kernel.org/show_bug.cgi?id=215789 Gregory, are you aware of these regressions? Is anyone working on them? Or is this faulty hw or something like that? Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bug 215635 - iwlwifi: Firmware crash with firmware 36.ca7b901d.0 (8265-36.ucode) 2022-06-17 6:38 ` Thorsten Leemhuis @ 2022-06-17 14:50 ` Jakub Kicinski 2022-07-14 7:37 ` Thorsten Leemhuis 1 sibling, 0 replies; 5+ messages in thread From: Jakub Kicinski @ 2022-06-17 14:50 UTC (permalink / raw) To: Thorsten Leemhuis Cc: golan.ben.ami, Luca Coelho, Johannes Berg, Gregory Greenman, Udo Steinberg, linux-wireless, regressions On Fri, 17 Jun 2022 08:38:55 +0200 Thorsten Leemhuis wrote: > > Any progress / outputs on this one? Folks are reporting it's still > > happening on Fedora 36 w/ 5.17.13. > > Jakub, thx for bringing this up, I had "look into this again" on my > todo list for some time already. Out of interest: where where those reports? The reports I was referring to are internal at Meta. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bug 215635 - iwlwifi: Firmware crash with firmware 36.ca7b901d.0 (8265-36.ucode) 2022-06-17 6:38 ` Thorsten Leemhuis 2022-06-17 14:50 ` Jakub Kicinski @ 2022-07-14 7:37 ` Thorsten Leemhuis 1 sibling, 0 replies; 5+ messages in thread From: Thorsten Leemhuis @ 2022-07-14 7:37 UTC (permalink / raw) To: Jakub Kicinski, golan.ben.ami, Luca Coelho, Johannes Berg, Gregory Greenman Cc: Udo Steinberg, linux-wireless, regressions Hi, this is your Linux kernel regression tracker. Top-posting for once, to make this easily accessible to everyone. Hey Iwlwifi maintainers, can you tell me why this regression report (https://bugzilla.kernel.org/show_bug.cgi?id=215635 ) and earlier mails in this thread seem to be ignored? Yes, sadly the issue was not bisected, but some help to track this down from your side would be really helpful to get to the root of the regression and fix it, as it'd expected due to Linus 'no regressions' policy. And yes, it seems the issue is still present, as Udo recently confirmed in a update comment to above ticket: """ BTW, I can confirm the issue is still present in 5.19.0-rc5 (which is the latest kernel as of today) and also with the new firmware (36.f82a4177.0). I've updated the bug title accordingly. """ Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) P.S.: As the Linux kernel's regression tracker I deal with a lot of reports and sometimes miss something important when writing mails like this. If that's the case here, don't hesitate to tell me in a public reply, it's in everyone's interest to set the public record straight. On 17.06.22 08:38, Thorsten Leemhuis wrote: > CCing Gregory, which became iwlwifi maintainer inbetween. > > On 16.06.22 20:58, Jakub Kicinski wrote: >> On Mon, 14 Mar 2022 12:51:38 +0100 Thorsten Leemhuis wrote: >>> Hi, this is your Linux kernel regression tracker. >>> >>> I noticed a regression report in bugzilla.kernel.org that afaics isn't >>> properly handled, that's why I decided to forward it to the lists and a >>> few relevant people to the CC. To quote from >>> https://bugzilla.kernel.org/show_bug.cgi?id=215635 : > > BTW, Udo recently confirmed there that the issue still happens on 5.18. > >>>> Seeing the following firmware crash frequently with >>>> firmware-version: 36.ca7b901d.0 8265-36.ucode >>>> >>>> [...] >>>> >>>> Afterwards iwlwifi is entirely unusable, i.e. the hardware does not recover. >>> >>>> I have not been able to observe the problem with 5.15.x so far. >>>> >>>> The problem manifests either by Wi-Fi becoming entirely unresponsive (not even ping to gateway works anymore) or by producing a firmware crash. >>>> >>>> In response to #3, the problem was most recently observed as a firmware crash on Linux 5.16.13. HW is Intel Corporation Wireless 8265 / 8275 (rev 78) (Windstorm Peak) and firmware version 36.ca7b901d.0 8265-36.ucode. >>>> >>>> I'm attaching the dmesg output from 5.16.13 (with the TWT patch mentioned above applied) which includes a firmware crash. >>> >>> Could somebody take a look into this? Or was this discussed somewhere >>> else already? Or even fixed? >> >> Any progress / outputs on this one? Folks are reporting it's still >> happening on Fedora 36 w/ 5.17.13. > > Jakub, thx for bringing this up, I had "look into this again" on my > todo list for some time already. Out of interest: where where those reports? > > Besides the one the quoted mail is about > (https://bugzilla.kernel.org/show_bug.cgi?id=215635 ) I'm aware of two > other reports that look similar and might or might not be related (hard > to tell without domain knowledge, I guess it might be just similar > symptoms): > > https://bugzilla.kernel.org/show_bug.cgi?id=215697 > https://bugzilla.kernel.org/show_bug.cgi?id=215789 > > Gregory, are you aware of these regressions? Is anyone working on them? > Or is this faulty hw or something like that? > > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) > > P.S.: As the Linux kernel's regression tracker I deal with a lot of > reports and sometimes miss something important when writing mails like > this. If that's the case here, don't hesitate to tell me in a public > reply, it's in everyone's interest to set the public record straight. ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-07-14 7:37 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-03-14 11:51 Bug 215635 - iwlwifi: Firmware crash with firmware 36.ca7b901d.0 (8265-36.ucode) Thorsten Leemhuis 2022-06-16 18:58 ` Jakub Kicinski 2022-06-17 6:38 ` Thorsten Leemhuis 2022-06-17 14:50 ` Jakub Kicinski 2022-07-14 7:37 ` Thorsten Leemhuis
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).