Re: [PATCH] usb: hub: Don't try to recover devices lost during warm reset.

["Michał Pecio" <michal.pecio@gmail.com>]

On Wed, 13 Aug 2025 12:05:16 +0200, Marcus Rückert wrote:
> On Wed, 2025-08-13 at 11:48 +0200, Michał Pecio wrote:
> > OK, three reset loops and three HC died in the last month, both at
> > the same time, about once a week. Possibly not a coincidence ;)
> >
> > Not sure if we can confidently say that reverting this patch helped,
> > because a week is just passing today. But the same hardware worked
> > fine for weeks/months/years? before a recent kernel upgrade, correct?  
> 
> From 2024-07 until end of July this year (when I upgraded to kernel
> 6.15.7) everything was working fine. Also since I run with the kernel
> where the patch is reverted the issue has not shown up again.

Considering rarity of those events I think you would need to run for
a few weeks to be sure that the problem is gone.

There is also a chance that some hardware change wich doesn't involve
the "usb 1-2" keyboard caused it. In bug 220069, another AMD chipset
was dying every few days if and only if two particular devices were
connected to the same USB controller (the chipset had two controllers).

> 
> > Random idea: would anything happen if you run 'usbreset' to manually
> > reset this device? Maybe a few times.  
> 
> How do I do that?

Run usbreset without arguments (as root) and it will print a small help
text and a list of devices it can reset. If you don't have usbreset,
ask Suse. Normally it should be in usbutils package like lsusb.

But I suspect nothing will happen (ie. the device will reset normally).
We tried it in bug 220069 as well.

So it will be waiting until it crashes spontaneously again.