From: Oliver Neukum <oneukum@suse.com>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>, linux-usb@vger.kernel.org
Subject: Re: USB hub problem
Date: Mon, 16 Aug 2021 12:30:47 +0200 [thread overview]
Message-ID: <00311c3e-9b32-792d-8320-d6080bc9585c@suse.com> (raw)
In-Reply-To: <3481f401-1d52-d5a1-d983-4b5f7046704b@eyal.emu.id.au>
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
next prev parent reply other threads:[~2021-08-16 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2021-08-16 12:25 ` Eyal Lebedinsky
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=00311c3e-9b32-792d-8320-d6080bc9585c@suse.com \
--to=oneukum@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox