linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: golan.ben.ami@intel.com, Luca Coelho <luciano.coelho@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: Bug 215635 - iwlwifi: Firmware crash with firmware 36.ca7b901d.0 (8265-36.ucode)
Date: Mon, 14 Mar 2022 12:51:38 +0100	[thread overview]
Message-ID: <915d6d66-4e42-8cbf-76bc-0f2f72d5e7d6@leemhuis.info> (raw)

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'.



             reply	other threads:[~2022-03-14 11:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 11:51 Thorsten Leemhuis [this message]
2022-06-16 18:58 ` Bug 215635 - iwlwifi: Firmware crash with firmware 36.ca7b901d.0 (8265-36.ucode) Jakub Kicinski
2022-06-17  6:38   ` Thorsten Leemhuis
2022-06-17 14:50     ` Jakub Kicinski
2022-07-14  7:37     ` 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=915d6d66-4e42-8cbf-76bc-0f2f72d5e7d6@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=golan.ben.ami@intel.com \
    --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).