stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* 6.14.y regression in ath11k
@ 2025-04-15 22:11 Mario Limonciello
  2025-04-16  5:16 ` Jiri Slaby
  2025-04-17 14:06 ` Greg KH
  0 siblings, 2 replies; 3+ messages in thread
From: Mario Limonciello @ 2025-04-15 22:11 UTC (permalink / raw)
  To: stable@vger.kernel.org
  Cc: Matthew Schwartz, Linux kernel regressions list,
	linux-wireless@vger.kernel.org

Hello,

Matt Schwartz (cc) found a regression in 6.14.2 that the Steam Deck OLED 
took 45s to find a network after suspend/resume waiting for a timeout.
This was a regression from 6.14.1.

The regression happened because:

commit 933ab187e679 ("wifi: ath11k: update channel list in reg notifier 
instead reg worker")
was backported to 6.14.y without the other commit in the series:

commit 02aae8e2f957 ("wifi: ath11k: update channel list in worker when 
wait flag is set")

Backporting commit 02aae8e2f957 ("wifi: ath11k: update channel list in 
worker when wait flag is set") to 6.14.2 fixes the regression.

Can you please take this commit back to stable too?

Thanks!

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 6.14.y regression in ath11k
  2025-04-15 22:11 6.14.y regression in ath11k Mario Limonciello
@ 2025-04-16  5:16 ` Jiri Slaby
  2025-04-17 14:06 ` Greg KH
  1 sibling, 0 replies; 3+ messages in thread
From: Jiri Slaby @ 2025-04-16  5:16 UTC (permalink / raw)
  To: Mario Limonciello, stable@vger.kernel.org
  Cc: Matthew Schwartz, Linux kernel regressions list,
	linux-wireless@vger.kernel.org

On 16. 04. 25, 0:11, Mario Limonciello wrote:
> Hello,
> 
> Matt Schwartz (cc) found a regression in 6.14.2 that the Steam Deck OLED 
> took 45s to find a network after suspend/resume waiting for a timeout.
> This was a regression from 6.14.1.
> 
> The regression happened because:
> 
> commit 933ab187e679 ("wifi: ath11k: update channel list in reg notifier 
> instead reg worker")
> was backported to 6.14.y without the other commit in the series:
> 
> commit 02aae8e2f957 ("wifi: ath11k: update channel list in worker when 
> wait flag is set")
> 
> Backporting commit 02aae8e2f957 ("wifi: ath11k: update channel list in 
> worker when wait flag is set") to 6.14.2 fixes the regression.

Agreed, this is the same as:
https://lore.kernel.org/all/5cd9db3f-4abf-4b66-b401-633508e905ac@kernel.org/


-- 
js
suse labs


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: 6.14.y regression in ath11k
  2025-04-15 22:11 6.14.y regression in ath11k Mario Limonciello
  2025-04-16  5:16 ` Jiri Slaby
@ 2025-04-17 14:06 ` Greg KH
  1 sibling, 0 replies; 3+ messages in thread
From: Greg KH @ 2025-04-17 14:06 UTC (permalink / raw)
  To: Mario Limonciello
  Cc: stable@vger.kernel.org, Matthew Schwartz,
	Linux kernel regressions list, linux-wireless@vger.kernel.org

On Tue, Apr 15, 2025 at 05:11:04PM -0500, Mario Limonciello wrote:
> Hello,
> 
> Matt Schwartz (cc) found a regression in 6.14.2 that the Steam Deck OLED
> took 45s to find a network after suspend/resume waiting for a timeout.
> This was a regression from 6.14.1.
> 
> The regression happened because:
> 
> commit 933ab187e679 ("wifi: ath11k: update channel list in reg notifier
> instead reg worker")
> was backported to 6.14.y without the other commit in the series:
> 
> commit 02aae8e2f957 ("wifi: ath11k: update channel list in worker when wait
> flag is set")
> 
> Backporting commit 02aae8e2f957 ("wifi: ath11k: update channel list in
> worker when wait flag is set") to 6.14.2 fixes the regression.
> 
> Can you please take this commit back to stable too?

Now queued up, thanks.

greg k-h

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-04-17 14:06 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-04-15 22:11 6.14.y regression in ath11k Mario Limonciello
2025-04-16  5:16 ` Jiri Slaby
2025-04-17 14:06 ` Greg KH

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).