From: Johan Hovold <johan@kernel.org>
To: Tung Pham <Tung.Pham@silabs.com>
Cc: Hung Nguyen <Hung.Nguyen@silabs.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
Pho Tran <Pho.Tran@silabs.com>
Subject: Re: Bugs: usb serial crash when close second comport
Date: Wed, 3 Feb 2021 09:49:24 +0100 [thread overview]
Message-ID: <YBpjlHNgzFA9aEAN@hovoldconsulting.com> (raw)
In-Reply-To: <CO1PR11MB4882F6F4F085A81470A34EE481B59@CO1PR11MB4882.namprd11.prod.outlook.com>
On Tue, Feb 02, 2021 at 09:48:01AM +0000, Tung Pham wrote:
> After the bug occur, when open or close device it show on log of system:
>
> failed set request 0x12 status: -110
> failed set request 0x00 status: -110
> failed set request 0x00 status: -110
>
> 0x00 = enable or disable serial device USB request.
> 0x12 = flush serial device USB request.
> -110 = time out.
>
> it means driver is not crashes but it can't open or close device any more.
Right, so the device just fails to respond. Can you communicate with
other devices connected to the same hub when this happens?
I found this note about "Interoperability between the Raspberry Pi and
USB 3.0 hubs" which appears to be related:
https://www.raspberrypi.org/documentation/hardware/raspberrypi/usb/README.md
Does connecting the device through an intermediary USB 2.0 hub make the
problem go away?
> We may find mainline kernel of raspberry if have, and find the driver
> of USB they use in next days.
Sounds good (even if this is starting to sound like a firmware issue).
Johan
prev parent reply other threads:[~2021-02-03 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PU1PR06MB2117988A6B7680CA1806DBE091B69@PU1PR06MB2117.apcprd06.prod.outlook.com>
2021-02-01 8:40 ` Bugs: usb serial crash when close second comport Johan Hovold
[not found] ` <CO1PR11MB48828958BDC51E796D37D63F81B69@CO1PR11MB4882.namprd11.prod.outlook.com>
2021-02-01 10:19 ` Johan Hovold
2021-02-02 3:50 ` Tung Pham
2021-02-02 8:32 ` Johan Hovold
2021-02-02 9:48 ` Tung Pham
2021-02-03 8:49 ` Johan Hovold [this message]
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=YBpjlHNgzFA9aEAN@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=Hung.Nguyen@silabs.com \
--cc=Pho.Tran@silabs.com \
--cc=Tung.Pham@silabs.com \
--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