From: Alan Stern <stern@rowland.harvard.edu>
To: Alberto Sentieri <22t@tripolho.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org
Subject: Re: kernel locks due to USB I/O
Date: Thu, 19 Nov 2020 14:43:00 -0500 [thread overview]
Message-ID: <20201119194300.GA582614@rowland.harvard.edu> (raw)
In-Reply-To: <427818cf-aa35-54d3-83cf-02529a0ab5aa@tripolho.com>
On Thu, Nov 19, 2020 at 02:21:47PM -0500, Alberto Sentieri wrote:
> lsusb -t in a similar configuration I use for development (it has just 6
> device, and not 36):
>
> $ lsusb -t
> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M
> |__ Port 3: Dev 5, If 0, Class=Hub, Driver=hub/7p, 480M
> |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/2p, 480M
> |__ Port 1: Dev 8, If 0, Class=Human Interface Device,
> Driver=usbhid, 12M
> |__ Port 2: Dev 7, If 0, Class=Hub, Driver=hub/2p, 480M
> |__ Port 1: Dev 10, If 0, Class=Human Interface Device,
> Driver=usbhid, 12M
> |__ Port 4: Dev 9, If 0, Class=Hub, Driver=hub/2p, 480M
> |__ Port 1: Dev 12, If 0, Class=Human Interface Device,
> Driver=usbhid, 12M
> |__ Port 5: Dev 11, If 0, Class=Hub, Driver=hub/7p, 480M
> |__ Port 6: Dev 13, If 0, Class=Hub, Driver=hub/7p, 480M
> |__ Port 6: Dev 15, If 0, Class=Hub, Driver=hub/2p, 480M
> |__ Port 1: Dev 17, If 0, Class=Human Interface Device,
> Driver=usbhid, 12M
> |__ Port 7: Dev 16, If 0, Class=Hub, Driver=hub/2p, 480M
> |__ Port 1: Dev 18, If 0, Class=Human Interface Device,
> Driver=usbhid, 12M
> |__ Port 7: Dev 14, If 0, Class=Human Interface Device,
> Driver=usbhid, 12M
Previously you said that each HID microcontroller is connected to port 1
of a two-port hub. But that clearly isn't true for device 14 in the
listing above. What happened there?
Alan Stern
next prev parent reply other threads:[~2020-11-19 19:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 19:20 kernel locks due to USB I/O Alberto Sentieri
2020-11-10 20:51 ` Alan Stern
2020-11-10 23:42 ` Alberto Sentieri
2020-11-11 7:51 ` Greg Kroah-Hartman
2020-11-11 15:51 ` Alan Stern
2020-11-11 19:31 ` Alberto Sentieri
2020-11-16 16:53 ` Alberto Sentieri
2020-11-16 17:06 ` Alan Stern
2020-11-16 18:42 ` Alberto Sentieri
2020-11-19 17:22 ` Alan Stern
2020-11-19 18:50 ` Alberto Sentieri
2020-11-19 20:01 ` Alan Stern
[not found] ` <4f8f545e-4846-45e0-b8f8-5c73876b150a@tripolho.com>
[not found] ` <20201119225144.GA590990@rowland.harvard.edu>
[not found] ` <3df90f9d-0af2-2aaa-9853-966f99e961a4@tripolho.com>
2020-12-14 17:18 ` Alan Stern
2020-12-16 22:14 ` Alberto Sentieri
2020-11-19 19:21 ` Alberto Sentieri
2020-11-19 19:43 ` Alan Stern [this message]
2020-11-19 22:14 ` Alberto Sentieri
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=20201119194300.GA582614@rowland.harvard.edu \
--to=stern@rowland.harvard.edu \
--cc=22t@tripolho.com \
--cc=gregkh@linuxfoundation.org \
--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.