From: Chris Kimber <chris.kimber@enatel.net>
To: "balbi@ti.com" <balbi@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: USB lockups on BeagleBone/AM335x
Date: Fri, 21 Feb 2014 15:27:09 +1300 [thread overview]
Message-ID: <5306B97D.8070306@enatel.net> (raw)
In-Reply-To: <20140221011405.GB19336@saruman.home>
Hey
On 21/02/2014 2:14 p.m., Felipe Balbi wrote:
> Hi,
>
> (please avoid top-posting)
>
> On Fri, Feb 21, 2014 at 12:11:40AM +0000, Chris Kimber wrote:
>> Hey,
>>
>> Thanks for the response.
>>
>> I've disabled the DMA (CONFIG_MUSB_PIO_ONLY=y) but the problem still
>> persists (for both USB sticks & USB serial ports).
> hmm, that's weird.
>
>> Now it looks like dsps_interrupt() never fires and causes the hang
>> up...
>>
>> [ 94.865635] tty ttyUSB0: serial_write - 11 byte(s)
>> [ 94.865656] cp210x ttyUSB0: usb_serial_generic_write_start - length = 11, data = 54 45 53 54 49 4e 47 20 34 32 0a
>> [ 94.865680] musb-hdrc musb-hdrc.1.auto: qh ce461a00 periodic slot 10
>> [ 94.865700] musb-hdrc musb-hdrc.1.auto: qh ce461a00 urb ce481e80 dev2 ep1out-bulk, hw_ep 10, ce43db00/11
>> [ 94.865721] musb-hdrc musb-hdrc.1.auto: --> hw10 urb ce481e80 spd2 dev2 ep1out h_addr00 h_port00 bytes 11
>> [ 94.865740] musb-hdrc musb-hdrc.1.auto: TX ep10 fifo d0832c48 count 11 buf ce43db00
>> [ 94.865755] musb-hdrc musb-hdrc.1.auto: Start TX10 pio
>> [ 94.865792] musb-hdrc musb-hdrc.1.auto: usbintr (0) epintr(400)
>> [ 94.865810] musb-hdrc musb-hdrc.1.auto: ** IRQ host usb0000 tx0400 rx0000
>> [ 94.865826] musb-hdrc musb-hdrc.1.auto: OUT/TX10 end, csr 2100
>> [ 94.865866] musb-hdrc musb-hdrc.1.auto: complete ce481e80 usb_serial_generic_write_bulk_callback+0x0/0xd4 [usbserial] (0), dev2 ep1out, 11/11
> so the first one completed just fine.
>
>> [ 94.865971] tty ttyUSB0: serial_write - 11 byte(s)
>> [ 94.865991] cp210x ttyUSB0: usb_serial_generic_write_start - length = 11, data = 54 45 53 54 49 4e 47 20 34 33 0a
>> [ 94.866015] musb-hdrc musb-hdrc.1.auto: qh ce461a00 periodic slot 10
>> [ 94.866035] musb-hdrc musb-hdrc.1.auto: qh ce461a00 urb ce481e80 dev2 ep1out-bulk, hw_ep 10, ce43db00/11
>> [ 94.866055] musb-hdrc musb-hdrc.1.auto: --> hw10 urb ce481e80 spd2 dev2 ep1out h_addr00 h_port00 bytes 11
>> [ 94.866075] musb-hdrc musb-hdrc.1.auto: TX ep10 fifo d0832c48 count 11 buf ce43db00
>> [ 94.866089] musb-hdrc musb-hdrc.1.auto: Start TX10 pio
> can you dump TXCSR, DEVCTL and IRQ registers when this happens ?
>
I added the IRQ registers to the debugfs interface..
IntrTX : 0000
IntrRX : 0000
IntrTXE : ffff
IntrRXE : fffe
IntrUSB : 08
IntrUSBE : f7
TxCSRp : 0000
DevCtl : 5d
Oddly the VBUSERR bit is set, if I disconnect the USB cable then it goes
to 0. I just tried plugging in via powered hub and that doesn't change
the status.
Chris
next prev parent reply other threads:[~2014-02-21 2:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 22:39 USB lockups on BeagleBone/AM335x Chris Kimber
2014-02-20 22:49 ` Felipe Balbi
2014-02-21 0:11 ` Chris Kimber
2014-02-21 1:14 ` Felipe Balbi
2014-02-21 2:27 ` Chris Kimber [this message]
2014-02-21 15:33 ` Felipe Balbi
2014-02-27 20:34 ` Chris Kimber
2014-02-27 20:52 ` Felipe Balbi
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=5306B97D.8070306@enatel.net \
--to=chris.kimber@enatel.net \
--cc=balbi@ti.com \
--cc=linux-omap@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;
as well as URLs for NNTP newsgroup(s).