From: Greg KH <greg@kroah.com>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: linux-usb@vger.kernel.org
Subject: Re: Understanding 'lsusb -t'
Date: Fri, 30 Aug 2024 16:28:31 +0200 [thread overview]
Message-ID: <2024083025-sheath-joining-2aa4@gregkh> (raw)
In-Reply-To: <d46a455c-a17d-4775-81be-57a5224bc41a@eyal.emu.id.au>
On Sat, Aug 31, 2024 at 12:07:32AM +1000, Eyal Lebedinsky wrote:
> On 30/8/24 10:32 pm, Greg KH wrote:
> > On Fri, Aug 30, 2024 at 10:14:20PM +1000, Eyal Lebedinsky wrote:
> > > I assume that the generated list is a tree, so each leaf (Device/If) is on only one point.
> > >
> > > I note this output:
> > >
> > > $ lsusb -tv
> > > /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M
> > > ID 1d6b:0002 Linux Foundation 2.0 root hub
> > > [trimmed]
> > > |__ Port 004: Dev 004, If 0, Class=Hub, Driver=hub/4p, 480M
> > > [trimmed]
> > > |__ Port 005: Dev 006, If 0, Class=Hub, Driver=hub/4p, 480M
> > > [trimmed]
> > > |__ Port 006: Dev 019, If 0, Class=Hub, Driver=hub/4p, 480M
> > > ID 2109:2817 VIA Labs, Inc.
> > > /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 10000M
> > > [trimmed]
> > > |__ Port 006: Dev 006, If 0, Class=Hub, Driver=hub/4p, 5000M
> > > ID 2109:0817 VIA Labs, Inc.
> > >
> > > I removed some content that is not relevant to my question.
> > >
> > > Note the Bus 001.Port 006 and Bus 002.Port 006 entries.
> > >
> > > I verified that both are for the same (one) device. They do not show when I disconnect it.
> > > The device is an external 4-port USB3.0 hub. It is listed once as 480M and once as 5000M.
> > > Nothing is plugged into any of the four ports.
> > >
> > > Is this correct? Why does this device show twice in the list?
> >
> > That's odd, as the same device shouldn't be on multiple busses. Busses
> > are a "root port" on the system (i.e. a new PCI controller device), so
> > are you sure you just don't have multiple devices with the same
> > device/vendor id?
> >
> > What is the diff between running the command before and after removing a
> > single device?
> >
> > thanks,
> >
> > greg k-h
>
> BTW, I run a nightly log of system commands which includes lsusb.
> The first time the device is listed twice is:
>
> $ uname -a
> Linux e7.eyal.emu.id.au 6.9.11-200.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jul 25 18:17:34 UTC 2024 x86_64 GNU/Linux
Ah, something has changed, that's more interesting.
Any way you can use 'git bisect' to see where it changed?
> $ lsusb --version
> lsusb (usbutils) 017
Did this get upgraded from an older version?
Do you see the same thing if you run 'usb-devices' before and after
(i.e. 2 devices being added)? How about just a normal 'lsusb'?
thanks,
greg k-h
next prev parent reply other threads:[~2024-08-30 14:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 12:14 Understanding 'lsusb -t' Eyal Lebedinsky
2024-08-30 12:32 ` Greg KH
2024-08-30 13:41 ` Eyal Lebedinsky
2024-08-30 13:43 ` Eyal Lebedinsky
2024-08-30 14:27 ` Greg KH
2024-08-30 14:33 ` Eyal Lebedinsky
2024-08-30 13:55 ` Eyal Lebedinsky
2024-08-30 14:07 ` Eyal Lebedinsky
2024-08-30 14:28 ` Understanding 'lsusb -t' [correction] Eyal Lebedinsky
2024-08-30 14:28 ` Greg KH [this message]
2024-08-30 14:25 ` Understanding 'lsusb -t' Alan Stern
2024-08-30 14:49 ` Greg KH
2024-08-30 14:49 ` Eyal Lebedinsky
2024-08-30 14:31 ` Michał Pecio
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=2024083025-sheath-joining-2aa4@gregkh \
--to=greg@kroah.com \
--cc=eyal@eyal.emu.id.au \
--cc=linux-usb@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.