From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Wolfgang Walter <linux@stwm.de>
Cc: Niklas Neronin <niklas.neronin@linux.intel.com>, stable@vger.kernel.org
Subject: Re: regression from 6.12.48 to 6.12.49: usb wlan adaptor stops working: bisected
Date: Mon, 29 Sep 2025 15:27:40 +0200 [thread overview]
Message-ID: <2025092930-manpower-flashily-e1fa@gregkh> (raw)
In-Reply-To: <01b8c8de46251cfaad1329a46b7e3738@stwm.de>
On Fri, Sep 26, 2025 at 05:54:00PM +0200, Wolfgang Walter wrote:
> Hello,o
> after upgrading to 6.12.49 my wlan adapter stops working. It is detected:
>
> kernel: mt76x2u 4-2:1.0: ASIC revision: 76120044
> kernel: mt76x2u 4-2:1.0: ROM patch build: 20141115060606a
> kernel: usb 3-4: reset high-speed USB device number 2 using xhci_hcd
> kernel: mt76x2u 4-2:1.0: Firmware Version: 0.0.00
> kernel: mt76x2u 4-2:1.0: Build: 1
> kernel: mt76x2u 4-2:1.0: Build Time: 201507311614____
>
> but does nor work. The following 2 messages probably are relevant:
>
> kernel: mt76x2u 4-2:1.0: MAC RX failed to stop
> kernel: mt76x2u 4-2:1.0: MAC RX failed to stop
>
> later I see a lot of
>
> kernel: mt76x2u 4-2:1.0: error: mt76x02u_mcu_wait_resp failed with -110
>
>
> I bisected it down to commit
>
> 9b28ef1e4cc07cdb35da257aa4358d0127168b68
> usb: xhci: remove option to change a default ring's TRB cycle bit
>
>
> 9b28ef1e4cc07cdb35da257aa4358d0127168b68 is the first bad commit
> commit 9b28ef1e4cc07cdb35da257aa4358d0127168b68
> Author: Niklas Neronin <niklas.neronin@linux.intel.com>
> Date: Wed Sep 17 08:39:07 2025 -0400
>
> usb: xhci: remove option to change a default ring's TRB cycle bit
>
> [ Upstream commit e1b0fa863907a61e86acc19ce2d0633941907c8e ]
>
> The TRB cycle bit indicates TRB ownership by the Host Controller (HC) or
> Host Controller Driver (HCD). New rings are initialized with
> 'cycle_state'
> equal to one, and all its TRBs' cycle bits are set to zero. When
> handling
> ring expansion, set the source ring cycle bits to the same value as the
> destination ring.
>
> Move the cycle bit setting from xhci_segment_alloc() to
> xhci_link_rings(),
> and remove the 'cycle_state' argument from xhci_initialize_ring_info().
> The xhci_segment_alloc() function uses kzalloc_node() to allocate
> segments,
> ensuring that all TRB cycle bits are initialized to zero.
>
> Signed-off-by: Niklas Neronin <niklas.neronin@linux.intel.com>
> Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
> Link: https://lore.kernel.org/r/20241106101459.775897-12-mathias.nyman@linux.intel.com
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Stable-dep-of: a5c98e8b1398 ("xhci: dbc: Fix full DbC transfer ring
> after several reconnects")
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
>
Does 6.17 also have this problem?
thanks,
greg k-h
next prev parent reply other threads:[~2025-09-29 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 15:54 regression from 6.12.48 to 6.12.49: usb wlan adaptor stops working: bisected Wolfgang Walter
2025-09-29 13:27 ` Greg Kroah-Hartman [this message]
2025-09-30 17:56 ` Wolfgang Walter
2025-09-29 14:08 ` Neronin, Niklas
2025-09-29 17:53 ` Wolfgang Walter
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=2025092930-manpower-flashily-e1fa@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux@stwm.de \
--cc=niklas.neronin@linux.intel.com \
--cc=stable@vger.kernel.org \
/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