All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: golan.ben.ami@intel.com, Luca Coelho <luciano.coelho@intel.com>,
	Johannes Berg <johannes@sipsolutions.net>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	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, 16 Jun 2022 11:58:08 -0700	[thread overview]
Message-ID: <20220616115808.141dec76@kernel.org> (raw)
In-Reply-To: <915d6d66-4e42-8cbf-76bc-0f2f72d5e7d6@leemhuis.info>

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.

  reply	other threads:[~2022-06-16 18:58 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 [this message]
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=20220616115808.141dec76@kernel.org \
    --to=kuba@kernel.org \
    --cc=golan.ben.ami@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@intel.com \
    --cc=regressions@leemhuis.info \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.