public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: "Diederik de Haas" <diederik@cknow-tech.com>
To: "Alan Stern" <stern@rowland.harvard.edu>
Cc: "USB mailing list" <linux-usb@vger.kernel.org>,
	<linux-rockchip@lists.infradead.org>
Subject: Re: Track down EHCI and companion errors on rk3xxx systems
Date: Tue, 13 Jan 2026 14:35:21 +0100	[thread overview]
Message-ID: <DFNI1Q9N7GC6.20PN0RG9LRAQF@cknow-tech.com> (raw)
In-Reply-To: <073879e4-aea8-4625-bc83-c4b6dd9c9231@rowland.harvard.edu>

On Sat Jan 3, 2026 at 5:52 PM CET, Alan Stern wrote:
> On Sat, Jan 03, 2026 at 12:00:13PM +0100, Diederik de Haas wrote:
>> On Wed Dec 31, 2025 at 7:09 PM CET, Alan Stern wrote:
>> > I can't say anything specific about your systems without a lot more 
>> > information.  However, I suspect that any problems you are running into 
>> > are not related to that warning.
>> 
>> What kind of information do you need?
>
> We can start with the output from "lsusb -t" as well as the dmesg log 
> from a boot in which something (a USB-2 port, for example) didn't work.  
> If the log shows something going wrong when you plugged in a device 
> after boot, explain what you did, what happened, and what was wrong.
>
> For now, concentrate on just a single system.

I was almost ready to declare 'issue fixed' when I actually did notice
the issue on a Quartz64-B (RK3566). For 'reasons', that may not be the
best test subject. Then I was preparing to test some media patches and
prepared my Quartz64-A (also RK3566), which is usually online 24/7.

Plugged in my keyboard adapter in the top USB2 port and that worked.
Installed some packages to make the graphical environment match that of
my other test devices and rebooted.
Got my (gtkgreet) login screen and plugged in my keyboard adapter in the
*bottom* USB2 port ... and that did NOT work.

Logged in via SSH and noticed it was indeed not listed in ``lsusb``.
Checked ``lsmod`` and ``dmesg | tail`` ... and noticed the kernel *did*
notice plugging in the keyboard adapter, so did ``lsusb`` *again* and
then it *did* list my keyboard adapter.
I did NOT employ my usual 'workaround' by plugging it into a USB3 port.

So it may be that it would have always worked ... eventually ... if I
had just waited long enough?
While 'dmesg' seems to suggest it took little over 0.5 seconds, I'm
really not that fast ;-P (or that impatient)

Full log:
https://paste.sr.ht/~diederik/34847f5c6873f1fc8d32eeb79f2bf2ff9dd4570c

Cheers,
  Diederik

  reply	other threads:[~2026-01-13 13:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-03 16:52 Track down EHCI and companion errors on rk3xxx systems Alan Stern
2026-01-13 13:35 ` Diederik de Haas [this message]
2026-01-13 15:47   ` Alan Stern
2026-01-13 16:16     ` Diederik de Haas
2026-01-13 16:22       ` Alan Stern
2026-01-13 21:15         ` Diederik de Haas
2026-01-14  3:20           ` Alan Stern
2026-01-14 14:59             ` Diederik de Haas
2026-01-14 15:19               ` Alan Stern
2026-01-14 15:41                 ` Diederik de Haas
2026-01-14 16:07                   ` Alan Stern
2026-01-14 17:31                     ` Diederik de Haas

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=DFNI1Q9N7GC6.20PN0RG9LRAQF@cknow-tech.com \
    --to=diederik@cknow-tech.com \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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