Re: 7.1 regression bisected to "usb: core: Fix SuperSpeed root hub wMaxPacketSize"

["Michel Dänzer" <michel.daenzer@mailbox.org>]

On 7/2/26 14:38, Greg Kroah-Hartman wrote:
> On Thu, Jul 02, 2026 at 02:25:04PM +0200, Michel Dänzer wrote:
>> 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.
> 
> "different" in what way, because it is a different speed?  Why would
> usbguard be prohibiting hubs?

What I mean is that usbguard considers the hub two different devices with or without the bisected kernel commit. No idea what exactly makes the difference though.


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