[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOf3c5dCsN2rDURv_Ct_K2agiFRe1zEjrQi1AM8LjTCfUYnLVw@mail.gmail.com>
Date: Tue, 27 Jan 2026 19:02:46 +0300
From: Ivan <kernvirt@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: linux-usb@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [BUG] r8152: Tx timeout and xHCI setup device timeout. RTL8153 31.00
Yes, the log is correct; during the time since boot, I had just
finished downloading those 900MB of packages. In this specific case,
the interface disappeared just before or during the reboot. After the
reboot, the interface did not reappear because the hub remained
powered, and a physical reconnect was required to initialize it again.
The previous log was short because it contained only kernel messages.
This time, I am attaching the full output of journalctl -b for more
context.
thanks
вт, 27 янв. 2026 г. в 18:09, Greg KH <gregkh@...uxfoundation.org>:
>
> On Tue, Jan 27, 2026 at 05:38:36PM +0300, Ivan wrote:
> > The USB hub is brand new. Honestly, I don't even know how to trigger
> > this bug; it happens completely randomly.
> > The chip does not overheat. I performed a stress test using iPerf,
> > where the router acted as the server and my machine as the client,
> > receiving traffic at 1 Gbps with 10 parallel streams. Simultaneously,
> > I kept a USB flash drive in the hub, continuously reading data from
> > it. The system remained stable for over 30 minutes without any issues,
> > then I terminated the test.
> > This specific crash today occurred right after downloading 900MB of
> > packages. Apologies for the previous log; this time I have attached
> > the full journalctl log for better context.
>
> Looks like the device disconnected right after booting, not after being
> used for a while. Are you sure that was the correct log?
>
> thanks,
>
> greg k-h
Download attachment "journalctl3" of type "application/octet-stream" (161577 bytes)
Powered by blists - more mailing lists