From: Bin Liu <b-liu@ti.com>
To: "Måns Rullgård" <mans@mansr.com>
Cc: linux-usb@vger.kernel.org
Subject: MUSB interrupt storm on device removal
Date: Mon, 17 Dec 2018 12:44:51 -0600 [thread overview]
Message-ID: <20181217184451.GA31211@uda0271908> (raw)
Hi,
On Mon, Dec 17, 2018 at 03:13:12PM +0000, Måns Rullgård wrote:
> I have a strange problem with the musb driver in host mode on AM3358
> (beaglebone) hardware. If I connect a multi-port serial adapter and
> open two or more of the ttys, then unplug the device, an interrupt storm
> ensues that makes the system completely unresponsive until the watchdog
> resets it. Enabling some debug messages, I get this repeated endlessly:
>
> musb-hdrc musb-hdrc.1: usbintr (0) epintr(1c0000)
> musb-hdrc musb-hdrc.1: end 2 RX proto error
> musb-hdrc musb-hdrc.1: ... next ep2 RX urb 72aabc13
> musb-hdrc musb-hdrc.1: <-- hw2 urb 72aabc13 spd3 dev4 ep3in h_addr02 h_port00 bytes 4096
> musb-hdrc musb-hdrc.1: RXCSR2 := 2020
> musb-hdrc musb-hdrc.1: end 3 RX proto error
> musb-hdrc musb-hdrc.1: ... next ep3 RX urb 94c2cc43
> musb-hdrc musb-hdrc.1: <-- hw3 urb 94c2cc43 spd3 dev4 ep2in h_addr02 h_port00 bytes 4096
> musb-hdrc musb-hdrc.1: RXCSR3 := 2020
> musb-hdrc musb-hdrc.1: end 4 RX proto error
> musb-hdrc musb-hdrc.1: ... next ep4 RX urb cbdc39c6
> musb-hdrc musb-hdrc.1: <-- hw4 urb cbdc39c6 spd3 dev4 ep5in h_addr02 h_port00 bytes 4096
> musb-hdrc musb-hdrc.1: RXCSR4 := 2020
>
> This happens with both a two-port FTDI serial adapter and a Simcom GSM
> modem (Qualcomm based) using the "option" driver. In both cases, the
> problem occurs only if two or more of the ttys are opened when the
> device is unplugged.
Please help me to understand the test case so that I can try to
replicate the issue - if I connect a multi-port FTDI adapter, use cat
command to open more than one port then unplug the adapter, I should
see the flooding debug messages?
On which kernel version do you see the problem?
Regards,
-Bin.
next reply other threads:[~2018-12-17 18:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 18:44 Bin Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-07 16:16 MUSB interrupt storm on device removal Bin Liu
2019-03-05 11:30 Måns Rullgård
2019-01-25 15:43 Bin Liu
2019-01-24 16:31 Måns Rullgård
2019-01-24 15:54 Bin Liu
2019-01-24 15:49 Alan Stern
2019-01-24 15:43 Bin Liu
2019-01-24 15:40 Bin Liu
2019-01-24 15:22 Alan Stern
2019-01-24 12:56 Måns Rullgård
2019-01-24 9:25 Johan Hovold
2019-01-24 9:22 Johan Hovold
2019-01-24 8:11 Greg Kroah-Hartman
2019-01-23 20:50 Måns Rullgård
2019-01-23 20:44 Alan Stern
2019-01-23 20:12 Bin Liu
2019-01-23 17:42 Alan Stern
2019-01-23 16:53 Bin Liu
2019-01-23 16:05 Alan Stern
2019-01-23 15:21 Bin Liu
2019-01-23 14:55 Johan Hovold
2019-01-23 14:09 Bin Liu
2019-01-23 8:55 Johan Hovold
2019-01-23 6:52 Greg KH
2019-01-22 20:52 Bin Liu
2019-01-22 20:16 Bin Liu
2019-01-22 17:19 Måns Rullgård
2019-01-22 14:57 Bin Liu
2019-01-21 21:20 Måns Rullgård
2019-01-21 16:31 Bin Liu
2019-01-18 20:15 Måns Rullgård
2019-01-10 3:07 Bin Liu
2019-01-09 13:19 Måns Rullgård
2018-12-17 21:36 Måns Rullgård
2018-12-17 20:56 Bin Liu
2018-12-17 19:16 Måns Rullgård
2018-12-17 15:13 Måns Rullgård
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=20181217184451.GA31211@uda0271908 \
--to=b-liu@ti.com \
--cc=linux-usb@vger.kernel.org \
--cc=mans@mansr.com \
/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;
as well as URLs for NNTP newsgroup(s).