linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Jakub Kicinski <kuba@kernel.org>,
	golan.ben.ami@intel.com, Luca Coelho <luciano.coelho@intel.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Gregory Greenman <gregory.greenman@intel.com>
Cc: Udo Steinberg <udo@hypervisor.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Bug 215635 - iwlwifi: Firmware crash with firmware 36.ca7b901d.0 (8265-36.ucode)
Date: Thu, 14 Jul 2022 09:37:08 +0200	[thread overview]
Message-ID: <6654209a-9d94-440e-bea0-65a473195c0f@leemhuis.info> (raw)
In-Reply-To: <28d2123f-65ce-f69c-12e1-f672b26225f4@leemhuis.info>

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.

      parent reply	other threads:[~2022-07-14  7:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 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=6654209a-9d94-440e-bea0-65a473195c0f@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=golan.ben.ami@intel.com \
    --cc=gregory.greenman@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=udo@hypervisor.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).