netdev - Re: [BUG] r8152: Tx timeout and xHCI setup device timeout. RTL8153 31.00

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2026012811-sepia-aeration-0238@gregkh>
Date: Wed, 28 Jan 2026 07:11:45 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Ivan <kernvirt@...il.com>
Cc: linux-usb@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [BUG] r8152: Tx timeout and xHCI setup device timeout. RTL8153
 31.00

A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top

On Tue, Jan 27, 2026 at 07:02:46PM +0300, Ivan wrote:
> 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, but it looks identical to the previous log, the device, at boot,
didn't want to talk to the USB host (i.e. your computer), and so
disconnected itself.  It must have gotten "confused" and so a physical
disconnect from power fixed it.

That's a lot different from "it was working and then it stopped", so it
might be a firmware bug in the device?  I don't know, sorry.

If you plug it in, after the system has been booted, does it always work
properly then?

thanks,

greg k-h