From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: "chris.bainbridge@gmail.com" <chris.bainbridge@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel.com>,
"Berg, Johannes" <johannes.berg@intel.com>,
"benjamin@sipsolutions.net" <benjamin@sipsolutions.net>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [REGRESSION] iwlwifi resume error, bisected
Date: Sun, 8 Sep 2024 08:53:01 +0000 [thread overview]
Message-ID: <d59125316423abd2f67e1c111eb54d083b7cc014.camel@intel.com> (raw)
In-Reply-To: <CAP-bSRZm4CyxY1VdtWvZRcfLMwc3njd3OTSd446Q5dcSfjJY=Q@mail.gmail.com>
On Sat, 2024-09-07 at 22:21 +0100, Chris Bainbridge wrote:
> On Sat, 7 Sept 2024 at 19:35, Grumbach, Emmanuel
> <emmanuel.grumbach@intel.com> wrote:
> >
> > Can you please try to add:
> > https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git/commit/?id=094513f8a2fbddee51b055d8035f995551f98fce
> > https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git/commit/?id=cb347bd29d0d106213a0cf4f86b72dffd08d3454
> >
> > and let me know if things work again for you?
>
> Both of those patches are already in v6.11-rc6 (which has the error).
Can you please try to apply this:
diff --git a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c
b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c
index 1822e22b7c0a..454eb1155881 100644
--- a/drivers/net/wireless/intel/iwlwifi/pcie/trans.c
+++ b/drivers/net/wireless/intel/iwlwifi/pcie/trans.c
@@ -1697,6 +1697,8 @@ int iwl_trans_pcie_d3_resume(struct iwl_trans *trans,
out:
if (*status == IWL_D3_STATUS_ALIVE)
ret = iwl_pcie_d3_handshake(trans, false);
+ else
+ trans->state = IWL_TRANS_NO_FW;
return ret;
}
It should fix the last part of the error you pasted:
[ 103.512122] iwlwifi 0000:01:00.0: Hardware error detected. Restarting.
[ 103.512330] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[ 103.512331] iwlwifi 0000:01:00.0: Transport status: 0x0000004B
You'll still have the first part but I expect WiFi to work.
I'm still checking internally what we need to do here.
Thanks for your report and bisection!
>
> > BTW - I assume that your system is configured not to power the WLAN device if the power cord is
> > not
> > connected and the system is suspended?
>
> This is a HP laptop with default BIOS settings. It's possible that the
> HP BIOS turns off the wifi when suspended on battery power, but I
> haven't explicitly configured anything related to WLAN power (I don't
> see any BIOS settings for that), and the kernel is running with
> default parameters.
I see. Thanks.
next prev parent reply other threads:[~2024-09-08 8:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 13:19 [REGRESSION] iwlwifi resume error, bisected Chris Bainbridge
2024-09-07 18:35 ` Grumbach, Emmanuel
2024-09-07 21:21 ` Chris Bainbridge
2024-09-08 8:53 ` Grumbach, Emmanuel [this message]
2024-09-08 10:54 ` Grumbach, Emmanuel
2024-09-08 20:55 ` Chris Bainbridge
2024-09-09 3:07 ` Grumbach, Emmanuel
2024-09-09 16:16 ` Chris Bainbridge
2024-09-09 19:39 ` Grumbach, Emmanuel
2024-09-09 21:03 ` Chris Bainbridge
2024-09-10 9:23 ` Chris Bainbridge
2024-09-10 10:26 ` Grumbach, Emmanuel
2025-03-26 14:54 ` Chris Bainbridge
2025-03-26 16:36 ` Grumbach, Emmanuel
2025-03-27 0:35 ` Chris Bainbridge
2025-03-27 0:58 ` Chris Bainbridge
2025-03-27 3:35 ` Grumbach, Emmanuel
2025-03-27 20:31 ` Grumbach, Emmanuel
2025-03-27 21:36 ` Chris Bainbridge
2025-03-28 4:24 ` Grumbach, Emmanuel
2025-05-31 21:24 ` Chris Bainbridge
2025-06-01 5:46 ` Grumbach, Emmanuel
2025-06-02 16:11 ` Chris Bainbridge
2025-06-03 9:19 ` Grumbach, Emmanuel
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=d59125316423abd2f67e1c111eb54d083b7cc014.camel@intel.com \
--to=emmanuel.grumbach@intel.com \
--cc=benjamin@sipsolutions.net \
--cc=chris.bainbridge@gmail.com \
--cc=johannes.berg@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.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