Linux USB
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel.daenzer@mailbox.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Michal Pecio <michal.pecio@gmail.com>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	linux-usb@vger.kernel.org
Subject: Re: 7.1 regression bisected to "usb: core: Fix SuperSpeed root hub wMaxPacketSize"
Date: Thu, 2 Jul 2026 14:25:04 +0200	[thread overview]
Message-ID: <ee889a90-6ef3-4546-a05c-227ed3e742a7@mailbox.org> (raw)
In-Reply-To: <2026070255-rerun-unstable-a90a@gregkh>

On 7/2/26 14:22, Greg Kroah-Hartman wrote:
> On Thu, Jul 02, 2026 at 02:20:05PM +0200, Michel Dänzer wrote:
>> On 7/2/26 10:51, Michal Pecio wrote:
>>> On Thu, 2 Jul 2026 00:09:42 +0300, Mathias Nyman wrote:
>>>> On 7/1/26 19:02, Michel Dänzer wrote:
>>>>>
>>>>> The ethernet port of a Lenovo ThinkPad USB-C Dock Gen2 connected to
>>>>> a ThinkPad P14s Gen 5 AMD stopped working in 7.1.
>>>>>
>>>>>   ip addr show enx482ae347e7c3
>>>>>
>>>>> says the interface doesn't exist. The only thing about it in dmesg
>>>>> is:
>>>>>
>>>>>   r8152 8-1.1:1.0 enx482ae347e7c3: renamed from eth0
>>>>>
>>>>> In previous kernels, dmesg had more lines about it:
>>>>>
>>>>>   r8152 8-1.1:1.0 enx482ae347e7c3: renamed from eth0
>>>>>   r8152 8-1.1:1.0 enx482ae347e7c3: carrier on
>>>>>   r8152 8-1.1:1.0 enx482ae347e7c3: carrier off
>>>>>   r8152 8-1.1:1.0 enx482ae347e7c3: carrier on
>>>>>
>>>>>
>>>>> I bisected this to d1e280334b7f ("usb: core: Fix SuperSpeed root
>>>>> hub wMaxPacketSize"). Reverting that commit on top of 7.1.2 fixes
>>>>> the issue.
>>>
>>> Incredibly bizarre, I wonder if it's some userspace madness.
>>
>> That reminded me that I'm using (an older upstream version of) usbguard. Unfortunately its GUI notifications when it blocks a USB device aren't working reliably currently.
>>
>> Manually firing up its settings app revealed that it was indeed blocking the USB3 hub. Overriding it to be allowed fixed the issue with the bisected commit.
>>
>> Looks like a false alert after all, sorry for the noise, and thanks for the help.
> 
> Thanks for letting us know, and this isn't the first time that usbguard
> has caused a problem recently.  Did we change something that broke it's
> functionality?

My assumption is that this change results in usbguard considering the USB3 hub a different device, so the persistent settings to allow it no longer applied.


-- 
Earthling Michel Dänzer       \        GNOME / Xwayland / Mesa developer
https://redhat.com             \               Libre software enthusiast

  reply	other threads:[~2026-07-02 12:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 16:02 7.1 regression bisected to "usb: core: Fix SuperSpeed root hub wMaxPacketSize" Michel Dänzer
2026-07-01 21:09 ` Mathias Nyman
2026-07-02  8:51   ` Michal Pecio
2026-07-02 12:20     ` Michel Dänzer
2026-07-02 12:22       ` Greg Kroah-Hartman
2026-07-02 12:25         ` Michel Dänzer [this message]
2026-07-02 12:38           ` Greg Kroah-Hartman
2026-07-02 16:34             ` Michel Dänzer
2026-07-05  8:59         ` Michal Pecio

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=ee889a90-6ef3-4546-a05c-227ed3e742a7@mailbox.org \
    --to=michel.daenzer@mailbox.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=michal.pecio@gmail.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