linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* USB hub problem
@ 2021-08-14 23:32 Eyal Lebedinsky
  2021-08-15  6:28 ` Greg KH
  2021-08-16 10:30 ` Oliver Neukum
  0 siblings, 2 replies; 7+ messages in thread
From: Eyal Lebedinsky @ 2021-08-14 23:32 UTC (permalink / raw)
  To: linux-usb

I have an external 4-way USB3.0 hub (I actually have two of them) That do not behave as expected.
It is an XCD XCDESSUSBH4BK. It is unpowered. I am on fedora 34, kernel 5.13.8-200.fc34.x86_64

For starters, I found that attaching a USB SSD does not allow booting from it.
I then found that when attaching my phone it is not recognized.

I searched the hub model and IDs but did not find relevant information.
Is there an official list of supported hubs (or devices)?

Here is what it looks like.

When the hub is attached (no phone) I see
         Bus 001 Device 048: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
and
         /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
             |__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
                 |__ Port 2: Dev 48, If 0, Class=Hub, Driver=hub/4p, 480M
Attaching the phone does not add a device.

Detaching/attaching the hub (with the phone already plugged in) I get
         Bus 001 Device 052: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy A5 (MTP)
         Bus 001 Device 051: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
and
         /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
             |__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
                 |__ Port 2: Dev 51, If 0, Class=Hub, Driver=hub/4p, 480M
                     |__ Port 1: Dev 52, If 1, Class=Communications, Driver=cdc_acm, 480M
                     |__ Port 1: Dev 52, If 2, Class=CDC Data, Driver=cdc_acm, 480M
                     |__ Port 1: Dev 52, If 0, Class=Imaging, Driver=, 480M
                     |__ Port 1: Dev 52, If 3, Class=Vendor Specific Class, Driver=, 480M
and the phone is recognized and accessible as MTP device.

Here are the logged messages for the two situations.

## attach hub (no phone):
Aug 15 09:05:31 e7 pipewire[97866]: 8 events suppressed
Aug 15 09:05:31 e7 kernel: usb 2-5.2: new SuperSpeed USB device number 12 using xhci_hcd
Aug 15 09:05:31 e7 kernel: usb 2-5.2: New USB device found, idVendor=0bda, idProduct=0411, bcdDevice= 1.04
Aug 15 09:05:31 e7 kernel: usb 2-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 15 09:05:31 e7 kernel: usb 2-5.2: Product: 4-Port USB 3.0 Hub
Aug 15 09:05:31 e7 kernel: usb 2-5.2: Manufacturer: Generic
Aug 15 09:05:31 e7 kernel: hub 2-5.2:1.0: USB hub found
Aug 15 09:05:31 e7 kernel: hub 2-5.2:1.0: 4 ports detected
Aug 15 09:05:31 e7 kernel: usb 1-5.2: new high-speed USB device number 55 using xhci_hcd
Aug 15 09:05:31 e7 kernel: usb 1-5.2: New USB device found, idVendor=0bda, idProduct=5411, bcdDevice= 1.04
Aug 15 09:05:31 e7 kernel: usb 1-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 15 09:05:31 e7 kernel: usb 1-5.2: Product: 4-Port USB 2.0 Hub
Aug 15 09:05:31 e7 kernel: usb 1-5.2: Manufacturer: Generic
Aug 15 09:05:31 e7 kernel: hub 1-5.2:1.0: USB hub found
Aug 15 09:05:31 e7 kernel: hub 1-5.2:1.0: 4 ports detected
Aug 15 09:05:31 e7 systemd-udevd[279738]: 2-5.2: Process '/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'' failed with exit code 1.
Aug 15 09:05:31 e7 journal[3313]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5.2
Aug 15 09:05:31 e7 systemd-udevd[279738]: 2-5.2:1.0: Process '/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'' failed with exit code 1.
Aug 15 09:05:31 e7 systemd-udevd[279741]: 1-5.2: Process '/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'' failed with exit code 1.
Aug 15 09:05:31 e7 journal[3313]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.2
Aug 15 09:05:31 e7 systemd-udevd[279738]: 1-5.2:1.0: Process '/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'' failed with exit code 1.
Aug 15 09:05:31 e7 Thunar[279748]: thunar-volman: Unsupported USB device type "usb".
Aug 15 09:05:31 e7 Thunar[279764]: thunar-volman: Unsupported USB device type "hub".
Aug 15 09:05:31 e7 Thunar[279768]: thunar-volman: Unsupported USB device type "usb".
Aug 15 09:05:31 e7 Thunar[279772]: thunar-volman: Unsupported USB device type "hub".

## plug phone:
         (no new messages)

## attach hub with phone already plugged in:
Aug 15 09:07:06 e7 kernel: usb 2-5.2: new SuperSpeed USB device number 13 using xhci_hcd
Aug 15 09:07:06 e7 kernel: usb 2-5.2: New USB device found, idVendor=0bda, idProduct=0411, bcdDevice= 1.04
Aug 15 09:07:06 e7 kernel: usb 2-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 15 09:07:06 e7 kernel: usb 2-5.2: Product: 4-Port USB 3.0 Hub
Aug 15 09:07:06 e7 kernel: usb 2-5.2: Manufacturer: Generic
Aug 15 09:07:06 e7 kernel: hub 2-5.2:1.0: USB hub found
Aug 15 09:07:06 e7 kernel: hub 2-5.2:1.0: 4 ports detected
Aug 15 09:07:07 e7 kernel: usb 1-5.2: new high-speed USB device number 56 using xhci_hcd
Aug 15 09:07:07 e7 kernel: usb 1-5.2: New USB device found, idVendor=0bda, idProduct=5411, bcdDevice= 1.04
Aug 15 09:07:07 e7 kernel: usb 1-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Aug 15 09:07:07 e7 kernel: usb 1-5.2: Product: 4-Port USB 2.0 Hub
Aug 15 09:07:07 e7 kernel: usb 1-5.2: Manufacturer: Generic
Aug 15 09:07:07 e7 kernel: hub 1-5.2:1.0: USB hub found
Aug 15 09:07:07 e7 kernel: hub 1-5.2:1.0: 4 ports detected
Aug 15 09:07:07 e7 systemd-udevd[279927]: 2-5.2: Process '/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'' failed with exit code 1.
Aug 15 09:07:07 e7 journal[3313]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5.2
Aug 15 09:07:07 e7 systemd-udevd[279927]: 2-5.2:1.0: Process '/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'' failed with exit code 1.
Aug 15 09:07:07 e7 systemd-udevd[279930]: 1-5.2: Process '/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'' failed with exit code 1.
Aug 15 09:07:07 e7 journal[3313]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.2
Aug 15 09:07:07 e7 systemd-udevd[279927]: 1-5.2:1.0: Process '/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'' failed with exit code 1.
Aug 15 09:07:07 e7 Thunar[279937]: thunar-volman: Unsupported USB device type "usb".
Aug 15 09:07:07 e7 Thunar[279952]: thunar-volman: Unsupported USB device type "hub".
Aug 15 09:07:07 e7 Thunar[279956]: thunar-volman: Unsupported USB device type "usb".
Aug 15 09:07:07 e7 Thunar[279960]: thunar-volman: Unsupported USB device type "hub".
Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: new high-speed USB device number 57 using xhci_hcd
Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= 4.00
Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: Product: SAMSUNG_Android
Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: Manufacturer: SAMSUNG
Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: SerialNumber: 0019ae8070ad3f
Aug 15 09:07:07 e7 kernel: cdc_acm 1-5.2.1:1.1: ttyACM0: USB ACM device
Aug 15 09:07:07 e7 systemd-udevd[279927]: 1-5.2.1: Process '/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'' failed with exit code 1.
Aug 15 09:07:07 e7 systemd-udevd[279927]: 1-5.2.1:1.0: Process '/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'' failed with exit code 1.
Aug 15 09:07:07 e7 systemd-udevd[279930]: 1-5.2.1:1.1: Process '/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'' failed with exit code 1.
Aug 15 09:07:07 e7 systemd-udevd[279970]: 1-5.2.1:1.2: Process '/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'' failed with exit code 1.
Aug 15 09:07:07 e7 systemd-udevd[279971]: 1-5.2.1:1.3: Process '/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'' failed with exit code 1.
Aug 15 09:07:07 e7 journal[1648]: CdMain: failed to emit DeviceAdded: failed to register object: An object is already exported for the interface org.freedesktop.ColorManager.Device at /org/freedesktop/ColorManager/devices/sysfs__null_
Aug 15 09:07:07 e7 journal[1648]: CdMain: failed to emit DeviceAdded: failed to register object: An object is already exported for the interface org.freedesktop.ColorManager.Device at /org/freedesktop/ColorManager/devices/sysfs__null_
Aug 15 09:07:07 e7 journal[1648]: CdMain: failed to emit DeviceAdded: failed to register object: An object is already exported for the interface org.freedesktop.ColorManager.Device at /org/freedesktop/ColorManager/devices/sysfs__null_

-- 
Eyal Lebedinsky (eyal@eyal.emu.id.au)

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: USB hub problem
  2021-08-14 23:32 USB hub problem Eyal Lebedinsky
@ 2021-08-15  6:28 ` Greg KH
  2021-08-15  7:47   ` Eyal Lebedinsky
  2021-08-16 10:30 ` Oliver Neukum
  1 sibling, 1 reply; 7+ messages in thread
From: Greg KH @ 2021-08-15  6:28 UTC (permalink / raw)
  To: Eyal Lebedinsky; +Cc: linux-usb

On Sun, Aug 15, 2021 at 09:32:06AM +1000, Eyal Lebedinsky wrote:
> I have an external 4-way USB3.0 hub (I actually have two of them) That do not behave as expected.
> It is an XCD XCDESSUSBH4BK. It is unpowered. I am on fedora 34, kernel 5.13.8-200.fc34.x86_64
> 
> For starters, I found that attaching a USB SSD does not allow booting from it.

That is up to your BIOS, not Linux.

> I then found that when attaching my phone it is not recognized.

In what way?

> I searched the hub model and IDs but did not find relevant information.
> Is there an official list of supported hubs (or devices)?

No, as any list would instantly be out of date.

> Here is what it looks like.
> 
> When the hub is attached (no phone) I see
>         Bus 001 Device 048: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
> and
>         /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
>             |__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
>                 |__ Port 2: Dev 48, If 0, Class=Hub, Driver=hub/4p, 480M
> Attaching the phone does not add a device.
> 
> Detaching/attaching the hub (with the phone already plugged in) I get
>         Bus 001 Device 052: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy A5 (MTP)
>         Bus 001 Device 051: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
> and
>         /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
>             |__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
>                 |__ Port 2: Dev 51, If 0, Class=Hub, Driver=hub/4p, 480M
>                     |__ Port 1: Dev 52, If 1, Class=Communications, Driver=cdc_acm, 480M
>                     |__ Port 1: Dev 52, If 2, Class=CDC Data, Driver=cdc_acm, 480M
>                     |__ Port 1: Dev 52, If 0, Class=Imaging, Driver=, 480M
>                     |__ Port 1: Dev 52, If 3, Class=Vendor Specific Class, Driver=, 480M
> and the phone is recognized and accessible as MTP device.

Great, so when does this not work?  This shows a successful device
found.

thanks,

greg k-h

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: USB hub problem
  2021-08-15  6:28 ` Greg KH
@ 2021-08-15  7:47   ` Eyal Lebedinsky
  2021-08-15  8:54     ` Felipe Balbi
  0 siblings, 1 reply; 7+ messages in thread
From: Eyal Lebedinsky @ 2021-08-15  7:47 UTC (permalink / raw)
  To: linux-usb



On 15/08/2021 16.28, Greg KH wrote:
> On Sun, Aug 15, 2021 at 09:32:06AM +1000, Eyal Lebedinsky wrote:
>> I have an external 4-way USB3.0 hub (I actually have two of them) That do not behave as expected.
>> It is an XCD XCDESSUSBH4BK. It is unpowered. I am on fedora 34, kernel 5.13.8-200.fc34.x86_64
>>
>> For starters, I found that attaching a USB SSD does not allow booting from it.
> 
> That is up to your BIOS, not Linux.

Attaching the USB SSD directly to the PC does boot from it though.

>> I then found that when attaching my phone it is not recognized.
> 
> In what way?
> 
>> I searched the hub model and IDs but did not find relevant information.
>> Is there an official list of supported hubs (or devices)?
> 
> No, as any list would instantly be out of date.
> 
>> Here is what it looks like.
>>
>> When the hub is attached (no phone) I see
>>          Bus 001 Device 048: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
>> and
>>          /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
>>              |__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
>>                  |__ Port 2: Dev 48, If 0, Class=Hub, Driver=hub/4p, 480M
>> Attaching the phone does not add a device.
>>
>> Detaching/attaching the hub (with the phone already plugged in) I get
>>          Bus 001 Device 052: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy A5 (MTP)
>>          Bus 001 Device 051: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
>> and
>>          /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
>>              |__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
>>                  |__ Port 2: Dev 51, If 0, Class=Hub, Driver=hub/4p, 480M
>>                      |__ Port 1: Dev 52, If 1, Class=Communications, Driver=cdc_acm, 480M
>>                      |__ Port 1: Dev 52, If 2, Class=CDC Data, Driver=cdc_acm, 480M
>>                      |__ Port 1: Dev 52, If 0, Class=Imaging, Driver=, 480M
>>                      |__ Port 1: Dev 52, If 3, Class=Vendor Specific Class, Driver=, 480M
>> and the phone is recognized and accessible as MTP device.
> 
> Great, so when does this not work?  This shows a successful device
> found.

Yes, this does show success, but earlier there is this failure shown:
	## plug phone:
         	(no new messages)
In other words, the system did not notice the phone when it was plugged into that hub.

I then attached the hub to the machine with the phone already plugged into it and it was
noticed.

My suspicion is that the hub is at fault and it fails to report the (phone plugged in) event
so linux probably has no knowledge of this.

What I failed to mention is that plugging a USB disk into this hub IS recognized as expected.
Something is not happy between the phone and this hub.

Plugging the phone to other USB 3.0 ports on this machine is recognized properly.

Thanks,
	Eyal

> thanks,
> 
> greg k-h
> 

-- 
Eyal Lebedinsky (eyal@eyal.emu.id.au)

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: USB hub problem
  2021-08-15  7:47   ` Eyal Lebedinsky
@ 2021-08-15  8:54     ` Felipe Balbi
  2021-08-15 10:35       ` Eyal Lebedinsky
  0 siblings, 1 reply; 7+ messages in thread
From: Felipe Balbi @ 2021-08-15  8:54 UTC (permalink / raw)
  To: Eyal Lebedinsky; +Cc: linux-usb


Hi,

Eyal Lebedinsky <eyal@eyal.emu.id.au> writes:
> On 15/08/2021 16.28, Greg KH wrote:
>> On Sun, Aug 15, 2021 at 09:32:06AM +1000, Eyal Lebedinsky wrote:
>>> I have an external 4-way USB3.0 hub (I actually have two of them) That do not behave as expected.
>>> It is an XCD XCDESSUSBH4BK. It is unpowered. I am on fedora 34, kernel 5.13.8-200.fc34.x86_64
>>>
>>> For starters, I found that attaching a USB SSD does not allow booting from it.
>> That is up to your BIOS, not Linux.
>
> Attaching the USB SSD directly to the PC does boot from it though.

right, booting happens way before the OS gets a chance to run. Sounds
like a BIOS issue.

>>> I then found that when attaching my phone it is not recognized.
>> In what way?
>> 
>>> I searched the hub model and IDs but did not find relevant information.
>>> Is there an official list of supported hubs (or devices)?
>> No, as any list would instantly be out of date.
>> 
>>> Here is what it looks like.
>>>
>>> When the hub is attached (no phone) I see
>>>          Bus 001 Device 048: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
>>> and
>>>          /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
>>>              |__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
>>>                  |__ Port 2: Dev 48, If 0, Class=Hub, Driver=hub/4p, 480M
>>> Attaching the phone does not add a device.
>>>
>>> Detaching/attaching the hub (with the phone already plugged in) I get
>>>          Bus 001 Device 052: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy A5 (MTP)
>>>          Bus 001 Device 051: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
>>> and
>>>          /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
>>>              |__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
>>>                  |__ Port 2: Dev 51, If 0, Class=Hub, Driver=hub/4p, 480M
>>>                      |__ Port 1: Dev 52, If 1, Class=Communications, Driver=cdc_acm, 480M
>>>                      |__ Port 1: Dev 52, If 2, Class=CDC Data, Driver=cdc_acm, 480M
>>>                      |__ Port 1: Dev 52, If 0, Class=Imaging, Driver=, 480M
>>>                      |__ Port 1: Dev 52, If 3, Class=Vendor Specific Class, Driver=, 480M
>>> and the phone is recognized and accessible as MTP device.
>> Great, so when does this not work?  This shows a successful device
>> found.
>
> Yes, this does show success, but earlier there is this failure shown:
> 	## plug phone:
>         	(no new messages)
>
> In other words, the system did not notice the phone when it was
> plugged into that hub.

does anything work when plugged to that hub? Is the hub self-powered or
bus powered?

> I then attached the hub to the machine with the phone already plugged
> into it and it was noticed.
>
> My suspicion is that the hub is at fault and it fails to report the
> (phone plugged in) event so linux probably has no knowledge of this.
>
> What I failed to mention is that plugging a USB disk into this hub IS
> recognized as expected.  Something is not happy between the phone and
> this hub.
>
> Plugging the phone to other USB 3.0 ports on this machine is
> recognized properly.

do you have other hubs around to test?

-- 
balbi

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: USB hub problem
  2021-08-15  8:54     ` Felipe Balbi
@ 2021-08-15 10:35       ` Eyal Lebedinsky
  0 siblings, 0 replies; 7+ messages in thread
From: Eyal Lebedinsky @ 2021-08-15 10:35 UTC (permalink / raw)
  To: linux-usb



On 15/08/2021 18.54, Felipe Balbi wrote:
> 
> Hi,
> 
> Eyal Lebedinsky <eyal@eyal.emu.id.au> writes:
>> On 15/08/2021 16.28, Greg KH wrote:
>>> On Sun, Aug 15, 2021 at 09:32:06AM +1000, Eyal Lebedinsky wrote:
>>>> I have an external 4-way USB3.0 hub (I actually have two of them) That do not behave as expected.
>>>> It is an XCD XCDESSUSBH4BK. It is unpowered. I am on fedora 34, kernel 5.13.8-200.fc34.x86_64
>>>>
>>>> For starters, I found that attaching a USB SSD does not allow booting from it.
>>> That is up to your BIOS, not Linux.
>>
>> Attaching the USB SSD directly to the PC does boot from it though.
> 
> right, booting happens way before the OS gets a chance to run. Sounds
> like a BIOS issue.
> 
>>>> I then found that when attaching my phone it is not recognized.
>>> In what way?
>>>
>>>> I searched the hub model and IDs but did not find relevant information.
>>>> Is there an official list of supported hubs (or devices)?
>>> No, as any list would instantly be out of date.
>>>
>>>> Here is what it looks like.
>>>>
>>>> When the hub is attached (no phone) I see
>>>>           Bus 001 Device 048: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
>>>> and
>>>>           /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
>>>>               |__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
>>>>                   |__ Port 2: Dev 48, If 0, Class=Hub, Driver=hub/4p, 480M
>>>> Attaching the phone does not add a device.
>>>>
>>>> Detaching/attaching the hub (with the phone already plugged in) I get
>>>>           Bus 001 Device 052: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy A5 (MTP)
>>>>           Bus 001 Device 051: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
>>>> and
>>>>           /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
>>>>               |__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
>>>>                   |__ Port 2: Dev 51, If 0, Class=Hub, Driver=hub/4p, 480M
>>>>                       |__ Port 1: Dev 52, If 1, Class=Communications, Driver=cdc_acm, 480M
>>>>                       |__ Port 1: Dev 52, If 2, Class=CDC Data, Driver=cdc_acm, 480M
>>>>                       |__ Port 1: Dev 52, If 0, Class=Imaging, Driver=, 480M
>>>>                       |__ Port 1: Dev 52, If 3, Class=Vendor Specific Class, Driver=, 480M
>>>> and the phone is recognized and accessible as MTP device.
>>> Great, so when does this not work?  This shows a successful device
>>> found.
>>
>> Yes, this does show success, but earlier there is this failure shown:
>> 	## plug phone:
>>          	(no new messages)
>>
>> In other words, the system did not notice the phone when it was
>> plugged into that hub.
> 
> does anything work when plugged to that hub? Is the hub self-powered or
> bus powered?

A USB disk is seen from this hub.
It is not powered.

>> I then attached the hub to the machine with the phone already plugged
>> into it and it was noticed.
>>
>> My suspicion is that the hub is at fault and it fails to report the
>> (phone plugged in) event so linux probably has no knowledge of this.
>>
>> What I failed to mention is that plugging a USB disk into this hub IS
>> recognized as expected.  Something is not happy between the phone and
>> this hub.
>>
>> Plugging the phone to other USB 3.0 ports on this machine is
>> recognized properly.
> 
> do you have other hubs around to test?

I just connected another hub to the same port and the phone shows up OK.

I have two identical hubs like the one failing and both fail in the same way. This issue is specific to these hubs.

TA

-- 
Eyal Lebedinsky (eyal@eyal.emu.id.au)

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: USB hub problem
  2021-08-14 23:32 USB hub problem Eyal Lebedinsky
  2021-08-15  6:28 ` Greg KH
@ 2021-08-16 10:30 ` Oliver Neukum
  2021-08-16 12:25   ` Eyal Lebedinsky
  1 sibling, 1 reply; 7+ messages in thread
From: Oliver Neukum @ 2021-08-16 10:30 UTC (permalink / raw)
  To: Eyal Lebedinsky, linux-usb


On 15.08.21 01:32, Eyal Lebedinsky wrote:
> I searched the hub model and IDs but did not find relevant information.
> Is there an official list of supported hubs (or devices)?

No, any hub by implementing the hub specification is supported.

> Attaching the phone does not add a device.

Just for the sake of completeness, could you post 'lsusb -v'
for that hub?

> ## plug phone:
>         (no new messages)
That suggests a bug in the hub firmware. specifically that
under unknown circumstances it fails to generate events
for connection changes.
> Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: new high-speed USB device
> number 57 using xhci_hcd
> Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: New USB device found,
> idVendor=04e8, idProduct=6860, bcdDevice= 4.00
> Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: New USB device strings: Mfr=2,
> Product=3, SerialNumber=4
> Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: Product: SAMSUNG_Android

In other respects it does work.

Based on a hunch, could you test whether the circumstances
this device fails under is related to runtime PM?

In order to do so you boot with

usbcore.autosuspend=-1

on the kernel command line.

    Regards
        Oliver


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: USB hub problem
  2021-08-16 10:30 ` Oliver Neukum
@ 2021-08-16 12:25   ` Eyal Lebedinsky
  0 siblings, 0 replies; 7+ messages in thread
From: Eyal Lebedinsky @ 2021-08-16 12:25 UTC (permalink / raw)
  To: linux-usb



On 16/08/2021 20.30, Oliver Neukum wrote:
> 
> On 15.08.21 01:32, Eyal Lebedinsky wrote:
>> I searched the hub model and IDs but did not find relevant information.
>> Is there an official list of supported hubs (or devices)?
> 
> No, any hub by implementing the hub specification is supported.
> 
>> Attaching the phone does not add a device.
> 
> Just for the sake of completeness, could you post 'lsusb -v'
> for that hub?

Bus 001 Device 095: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Device Descriptor:
   bLength                18
   bDescriptorType         1
   bcdUSB               2.10
   bDeviceClass            9 Hub
   bDeviceSubClass         0
   bDeviceProtocol         2 TT per port
   bMaxPacketSize0        64
   idVendor           0x0bda Realtek Semiconductor Corp.
   idProduct          0x5411 RTS5411 Hub
   bcdDevice            1.04
   iManufacturer           1 Generic
   iProduct                2 4-Port USB 2.0 Hub
   iSerial                 0
   bNumConfigurations      1
   Configuration Descriptor:
     bLength                 9
     bDescriptorType         2
     wTotalLength       0x0029
     bNumInterfaces          1
     bConfigurationValue     1
     iConfiguration          0
     bmAttributes         0xe0
       Self Powered
       Remote Wakeup
     MaxPower                0mA
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        0
       bAlternateSetting       0
       bNumEndpoints           1
       bInterfaceClass         9 Hub
       bInterfaceSubClass      0
       bInterfaceProtocol      1 Single TT
       iInterface              0
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x81  EP 1 IN
         bmAttributes            3
           Transfer Type            Interrupt
           Synch Type               None
           Usage Type               Data
         wMaxPacketSize     0x0001  1x 1 bytes
         bInterval              12
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        0
       bAlternateSetting       1
       bNumEndpoints           1
       bInterfaceClass         9 Hub
       bInterfaceSubClass      0
       bInterfaceProtocol      2 TT per port
       iInterface              0
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x81  EP 1 IN
         bmAttributes            3
           Transfer Type            Interrupt
           Synch Type               None
           Usage Type               Data
         wMaxPacketSize     0x0001  1x 1 bytes
         bInterval              12

>> ## plug phone:
>>          (no new messages)
> That suggests a bug in the hub firmware. specifically that
> under unknown circumstances it fails to generate events
> for connection changes.

I do not know it it is of value, but when the phone is not detected, it also does not
indicate that it is connected using MTP. It thinks it is only being charged only.

>> Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: new high-speed USB device
>> number 57 using xhci_hcd
>> Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: New USB device found,
>> idVendor=04e8, idProduct=6860, bcdDevice= 4.00
>> Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: New USB device strings: Mfr=2,
>> Product=3, SerialNumber=4
>> Aug 15 09:07:07 e7 kernel: usb 1-5.2.1: Product: SAMSUNG_Android
> 
> In other respects it does work.
> 
> Based on a hunch, could you test whether the circumstances
> this device fails under is related to runtime PM?
> 
> In order to do so you boot with
> 
> usbcore.autosuspend=-1
 >
> 
> on the kernel command line.

Well I can do better. I use USB TV tuners and in /etc/modprobe.d/dvb.conf I see
	options usbcore autosuspend=-1
It is a leftover from using an old tuner.

>      Regards
>          Oliver

Thanks

-- 
Eyal Lebedinsky (eyal@eyal.emu.id.au)

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2021-08-16 12:31 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-14 23:32 USB hub problem Eyal Lebedinsky
2021-08-15  6:28 ` Greg KH
2021-08-15  7:47   ` Eyal Lebedinsky
2021-08-15  8:54     ` Felipe Balbi
2021-08-15 10:35       ` Eyal Lebedinsky
2021-08-16 10:30 ` Oliver Neukum
2021-08-16 12:25   ` Eyal Lebedinsky

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).