All of lore.kernel.org
 help / color / mirror / Atom feed
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:27:08 +0200	[thread overview]
Message-ID: <2024083013-rentable-matador-050b@gregkh> (raw)
In-Reply-To: <4e3c79f0-9f06-4da2-b479-1300d4890786@eyal.emu.id.au>

On Fri, Aug 30, 2024 at 11:43:39PM +1000, Eyal Lebedinsky wrote:
> On 30/8/24 11:41 pm, 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?
> > 
> > The hub is on an extension cable, and I just unplug it the hub.
> > 
> > > What is the diff between running the command before and after removing a
> > > single device?
> > 
> > $ lsusb -tv >lsusb-all.log
> > $ lsusb -tv >lsusb-less.log
> > $ diff -u lsusb-all.log lsusb-less.log
> > --- lsusb-all.log       2024-08-30 23:39:09.782062079 +1000
> > +++ lsusb-less.log      2024-08-30 23:39:22.608987407 +1000
> > @@ -48,8 +48,6 @@
> >               ID 0c45:7401 Microdia TEMPer Temperature Sensor
> >           |__ Port 004: Dev 018, If 1, Class=Human Interface Device, Driver=[none], 1.5M
> >               ID 0c45:7401 Microdia TEMPer Temperature Sensor
> > -    |__ 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
> >       ID 1d6b:0003 Linux Foundation 3.0 root hub
> >       |__ Port 004: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M
> > @@ -58,5 +56,3 @@
> >               ID 0bda:0411 Realtek Semiconductor Corp. Hub
> >       |__ Port 005: Dev 003, If 0, Class=Hub, Driver=hub/4p, 5000M
> >           ID 05e3:0612 Genesys Logic, Inc. Hub
> > -    |__ Port 006: Dev 006, If 0, Class=Hub, Driver=hub/4p, 5000M
> > -        ID 2109:0817 VIA Labs, Inc.
> 
> Also, here these the log messages when I reconnect the hub:
> 
> 2024-08-30T23:41:52+10:00 e7.eyal.emu.id.au kernel: usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> 2024-08-30T23:41:52+10:00 e7.eyal.emu.id.au kernel: usb 1-6: Product: USB2.0 Hub
> 2024-08-30T23:41:52+10:00 e7.eyal.emu.id.au kernel: usb 1-6: Manufacturer: VIA Labs, Inc.
> 2024-08-30T23:41:52+10:00 e7.eyal.emu.id.au kernel: hub 1-6:1.0: USB hub found
> 2024-08-30T23:41:52+10:00 e7.eyal.emu.id.au kernel: hub 1-6:1.0: 4 ports detected
> 2024-08-30T23:41:52+10:00 e7.eyal.emu.id.au kernel: usb 2-6: new SuperSpeed USB device number 7 using xhci_hcd
> 2024-08-30T23:41:52+10:00 e7.eyal.emu.id.au kernel: usb 2-6: New USB device found, idVendor=2109, idProduct=0817, bcdDevice= 0.50
> 2024-08-30T23:41:52+10:00 e7.eyal.emu.id.au kernel: usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> 2024-08-30T23:41:52+10:00 e7.eyal.emu.id.au kernel: usb 2-6: Product: USB3.0 Hub
> 2024-08-30T23:41:52+10:00 e7.eyal.emu.id.au kernel: usb 2-6: Manufacturer: VIA Labs, Inc.
> 2024-08-30T23:41:52+10:00 e7.eyal.emu.id.au kernel: hub 2-6:1.0: USB hub found
> 2024-08-30T23:41:52+10:00 e7.eyal.emu.id.au kernel: hub 2-6:1.0: 4 ports detected

Extension cables are very wierd, and you are right, this is two
different hubs on two ports.  Is this a thunderbolt device somehow?

Anyway, as long as everything is working properly, all should be good.

What happens when you plug a device into this cable at the other end,
does it show up twice?  Or just once?

thanks,

greg k-h

  reply	other threads:[~2024-08-30 14:27 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 [this message]
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     ` Understanding 'lsusb -t' Greg KH
2024-08-30 14:25 ` 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=2024083013-rentable-matador-050b@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.