public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: Philip Balister <philip@balister.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	linux-usb@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: Kernel oops when shutting down program using usb device
Date: Thu, 17 Jul 2008 01:17:11 +0300	[thread overview]
Message-ID: <20080716221708.GA20951@frodo> (raw)
In-Reply-To: <487E6F25.3060801@balister.org>

On Wed, Jul 16, 2008 at 05:59:01PM -0400, Philip Balister wrote:
> Alan Stern wrote:
>> On Wed, 16 Jul 2008, Philip Balister wrote:
>>
>>> The program streams data from the USRP (Universal Software Radio  
>>> Peripheral) and calculates a transfer rate. It looks like the test  
>>> completes and the program ooops as it is exiting.
>>>
>>> Let me know if I can collect anything else. I am not much of a usb guy :(
>>>
>>> Philip
>>>
>>> root@beagleboard:~/gnuradio-3.1.2/usrp/host/apps#  
>>> ./test_usrp_standard_rx -D 200rx_overrun
>>> eth0: set allmulti
>>> eth0: set allmulti
>>> eth0: set allmulti
>>> eth0: set allmulti
>>> xfered 1.34e+08 bytes in 116 seconds.  1.159e+06 bytes/sec.  cpu time 
>>> = 1.633
>>> noverruns = 1
>>> ------------[ cut here ]------------
>>> WARNING: at lib/kref.c:43 kref_get+0x28/0x44()
>>
>> This is just a warning, not an oops.  Nevertheless, it should not  
>> happen.
>>
>> What version of the kernel were you running?  On what hardware and
>> using which USB host controller driver?  Is the problem reproducible?
>
> Doh, silly me for leaving out details ....
>
> Beagle Board, OMAP3 based. Kernel is a fairly recent git + some patches.  
> I can backtrack to an exact collection if necessary.
>
> I ran the test program several times and the system hangs when the  
> program ends. I do not think I get the warning message every time  
> though, the system does hang every time.

Hmm... so it's musb. Please, recompile your kernel with
CONFIG_USB_MUSB_LOGLEVEL set to 3 and enable also CONFIG_USB_DEBUG
and CONFIG_USB_GADGET_DEBUG.

Set sysrq-trigger to 8 (echo 8 > /proc/sysrq-trigger) and musb debug
messages will be written to you current console.

Send that output in next mail :-) I'll try to look at it tomorrow with
my beagle. Which gadget driver are you using ? Get me the output of
uname -r. Which test program is that ? Tell me how to reproduce the
WARNING if I don't have your test program.

-- 
balbi

  reply	other threads:[~2008-07-16 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 21:26 Kernel oops when shutting down program using usb device Philip Balister
2008-07-16 21:44 ` Alan Stern
2008-07-16 21:59   ` Philip Balister
2008-07-16 22:17     ` Felipe Balbi [this message]
2008-07-17  3:53       ` TI USB 3410 chipset download firmware amruth

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=20080716221708.GA20951@frodo \
    --to=me@felipebalbi.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=philip@balister.org \
    --cc=stern@rowland.harvard.edu \
    /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