public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Karsten Tausche <ktao.oss@posteo.org>
To: David Wang <00107082@163.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	miriam.rachel.korenblit@intel.com,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: IWL Error Log Dump since 6.17.0-rc5
Date: Sat, 20 Sep 2025 15:49:42 +0000	[thread overview]
Message-ID: <aM7NFYJJdGR1Hnfg@rakis> (raw)
In-Reply-To: <35b1fd7b.aa06.1993e2b7ce5.Coremail.00107082@163.com>

Hi,

I can confirm the same issue and resolution on a similar card "Intel
Corporation Wireless 7265 (rev 59)". I did not test rc5, but rc4 was
working and rc6 broken for me.

On Fri, Sep 12, 2025 at 09:44:21PM +0800, David Wang wrote:
> 
> At 2025-09-10 16:31:33, "Johannes Berg" <johannes@sipsolutions.net> wrote:
> >On Wed, 2025-09-10 at 15:47 +0800, David Wang wrote:
> >> Hi, 
> >> 
> >> I think those error dump is introduced by commit 586e3cb33ba6890054b95aa0ade0a165890efabd("wifi: iwlwifi: fix byte count table for old devices")
> >> 
> >> My wireless pcie card has device_family 15 which is less than IWL_DEVICE_FAMILY_9000, and the changes in the commit have changed the behavior for my devices.
> >> 
> >> -       if (trans->mac_cfg->device_family < IWL_DEVICE_FAMILY_AX210)
> >> +       if (trans->mac_cfg->device_family >= IWL_DEVICE_FAMILY_9000 &&
> >> +           trans->mac_cfg->device_family < IWL_DEVICE_FAMILY_AX210)
> >>                 len = DIV_ROUND_UP(len, 4);
> >
> >I think I just got confused, and that 9000 should be 7000. Presumably
> >that'd work for you, I'll send a patch.
> >
> >johannes
> 
> 
> Hi, 
> 
> My system has been run for days and no IWL error dumps & reset happened.
> I think I can confirm that my wireless card needs the length adjustment.
> 
> Some information about my cards:
> 
> [    5.067265] iwlwifi 0000:21:00.0: enabling device (0000 -> 0002)
> [    5.068798] iwlwifi 0000:21:00.0: Detected crf-id 0x0, cnv-id 0x0 wfpm id 0x0
> [    5.068809] iwlwifi 0000:21:00.0: PCI dev 08b1/c070, rev=0x144, rfid=0xd55555d5
> [    5.068813] iwlwifi 0000:21:00.0: device family: 15  <-- 
> [    5.068816] iwlwifi 0000:21:00.0: Detected Intel(R) Dual Band Wireless AC 7260
> [    5.075593] iwlwifi 0000:21:00.0: loaded firmware version 17.bfb58538.0 7260-17.ucode op_mode iwlmvm
> 
> $ lspci
> ...
> 21:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
> ...
> 
> 
> My device match the config in drivers/net/wireless/intel/iwlwifi/pcie/drv.c:
> 
> 263         {IWL_PCI_DEVICE(0x08B1, 0xC070, iwl7000_mac_cfg)},
> 
> iwl7000_mac_cfg is defined as:
> 
>  88 const struct iwl_mac_cfg iwl7000_mac_cfg = { 
>  89         .device_family = IWL_DEVICE_FAMILY_7000, 
>  90         .base = &iwl7000_base,
>  91 };
> 
> And indeed, it is IWL_DEVICE_FAMILY_7000
> 

Early kernel logs for my chip below. 095b/5210 is matching the same
config iwl7000_mac_cfg as above.

iwlwifi 0000:03:00.0: Detected crf-id 0x0, cnv-id 0x0 wfpm id 0x0
iwlwifi 0000:03:00.0: PCI dev 095b/5210, rev=0x210, rfid=0xd55555d5
iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless-AC 7265

Snippet of failure logs on v6.17-rc6:

iwlwifi 0000:03:00.0: Microcode SW error detected.  Restarting 0x2000000.
iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
iwlwifi 0000:03:00.0: Transport status: 0x0000004A, valid: 6
iwlwifi 0000:03:00.0: Loaded firmware version: 29.f2390aa8.0 7265D-29.ucode
iwlwifi 0000:03:00.0: 0x00001030 | ADVANCED_SYSASSERT
iwlwifi 0000:03:00.0: 0x00800233 | trm_hw_status0
iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
iwlwifi 0000:03:00.0: 0x00043D6C | branchlink2
iwlwifi 0000:03:00.0: 0x0004B002 | interruptlink1
...

$ lscpi
...
03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
...


Thanks,
Karsten


      reply	other threads:[~2025-09-20 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09 16:58 IWL Error Log Dump since 6.17.0-rc5 David Wang
2025-09-10  7:47 ` David Wang
2025-09-10  8:31   ` IWL " Johannes Berg
2025-09-12 13:44     ` David Wang
2025-09-20 15:49       ` Karsten Tausche [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=aM7NFYJJdGR1Hnfg@rakis \
    --to=ktao.oss@posteo.org \
    --cc=00107082@163.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=miriam.rachel.korenblit@intel.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