mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Gabriel C <nix.or.die@googlemail.com>, linux-wireless@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	Luca Coelho <luciano.coelho@intel.com>,
	linux-firmware@vger.kernel.org
Subject: Re: AX200 cards broken after firmware cc-a0-67
Date: Thu, 03 Feb 2022 20:00:16 +0100	[thread overview]
Message-ID: <19ea449a9f772f12058785be873c7ea5504a0eb8.camel@sipsolutions.net> (raw)
In-Reply-To: <CAEJqkgiV1_jXhoxoxVG4EwV7t=cA=j1F+T-LCEuajJN8x25mtQ@mail.gmail.com>

On Thu, 2022-02-03 at 18:58 +0100, Gabriel C wrote:
> Hello,
> 
> I own 3 boxes with AX200 cards, one is a Killer AX1650x, the other two
> AX200 [8086:2723] (rev 1a).
> 
> After commit 4474519a1fd4e7167afae7c5ca2c1b93e17b4d8a in
> linux-firmware tree, which updates
> the firmware to cc-a0-67.ucode, all cards are crashing with microcode
> errors. Firmware  cc-a0-66.ucode
> is still fine. The kernel doesn't seem to matter, as soon I update the
> firmware to >=67 ( I tested 68 too ),
> everything crashes in an endless loop.
> 
> I'll attach a dmesg, from 5.17.0-rc2, the same crash happens with 5.16* etc.
> 

> [   18.453176] iwlwifi 0000:03:00.0: 0x00001062 | ADVANCED_SYSASSERT 

So I think this is broadcast filtering again, discussed previously on
the list. Turn off CONFIG_IWLWIFI_BCAST_FILTERING for now, a fix is in
the works.

johannes

      parent reply	other threads:[~2022-02-03 19:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 17:58 Gabriel C
2022-02-03 18:41 ` Gabriel C
2022-02-03 19:00 ` Johannes Berg [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=19ea449a9f772f12058785be873c7ea5504a0eb8.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-firmware@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@intel.com \
    --cc=nix.or.die@googlemail.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

all inboxes | Powered by JetHome®