mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Wireless <linux-wireless@vger.kernel.org>
Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	Kalle Valo <kvalo@kernel.org>,
	Gregory Greenman <gregory.greenman@intel.com>,
	Pawel <pawel.veselov@gmail.com>
Subject: Fwd: 6.5.5 hardware access timeout / HW error / GPF in iwlwifi
Date: Thu, 5 Oct 2023 18:11:35 +0700	[thread overview]
Message-ID: <9fa3c04b-bd98-4fde-9bfd-27d83132e766@gmail.com> (raw)

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

> Hardware: Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x370
> Works just fine with 6.4.15 (and older)
> Using FC37, updated to the latest available kernel 6.5.5, can't use WiFi or even boot.
> Linux firmware package: linux-firmware-20230919-1 (latest available version for F37)
> 
> First boot:
> Timeout waiting for hardware access (CSR_GP_CNTRL 0xffffffff)
> at __iwl_trans_pcie_grab_nic_access+0x14a/0x150
> followed by HW error, resetting before reading at
> iwl_fwrt_dump_lmac_error_log+0x50c/0x600 
> The interface didn't ever plumb.
> 
> Second boot: GPF. I don't have the traces, but I swear it originated from iwlwifi module from what I saw on the console.
> 
> I've attached the traces for both the failed boots, and the normal boot from 6.4.15 for reference.

See Bugzilla for the full thread and attached dmesg logs.

Anyway, I'm adding this regression to regzbot:

#regzbot introduced: v6.4..v6.5 https://bugzilla.kernel.org/show_bug.cgi?id=217963

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217963

-- 
An old man doll... just what I always wanted! - Clara

             reply	other threads:[~2023-10-05 14:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 11:11 Bagas Sanjaya [this message]
2023-11-28 23:18 ` Bagas Sanjaya

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=9fa3c04b-bd98-4fde-9bfd-27d83132e766@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=gregory.greenman@intel.com \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pawel.veselov@gmail.com \
    --cc=regressions@lists.linux.dev \
    /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®