public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
Cc: linux-omap@vger.kernel.org, beagleboard@googlegroups.com
Subject: Re: OTG MUSB driver issue?
Date: Fri, 27 Feb 2009 19:56:39 +0200	[thread overview]
Message-ID: <20090227175638.GE16801@frodo> (raw)
In-Reply-To: <ac9c93b10902270952w37660667pece3640b0ba46ffc@mail.gmail.com>

On Fri, Feb 27, 2009 at 06:52:38PM +0100, Frans Meulenbroeks wrote:
> Hi,
> 
> Several times I encountered issues with devices connected to the
> beagle board's OTG port (through a powered hub).
> (kernel 2.6.28-omap1).
> Today this happened again and I was lucky enough to be able to find
> the symptoms.
> 
> Scenario: I had a file on a USB hard disk. This file was copied to an
> SD card. After copying the file was corrupted.
> Removing the card and hard disk and connecting them to my linux box
> allowed me to compare the SD and hard disk version (using cmp -l).
> There were differences on four places. Each difference was 4 bytes (32
> bits) and occurred on a 4 byte boundary.
> 
> I have no idea what causes it, but I strongly suspect the MUSB driver.
> A hauppauge usb tv card also does not work when connected to the hub,
> whereas the same card works without problem on a linksys NSLU2 (which
> also has an arm processor).
> 
> Anyone suggestions? Patches ??

I guess that should be already fixed with patches queued up in Greg's
queue, but then again, let me check more. Could you:

# echo 5 > /sys/modules/musb_hdrc/parameters/debug
# echo 8 > /proc/sysrq-trigger

then connect device and send me log output ?

-- 
balbi

  reply	other threads:[~2009-02-27 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27 17:52 OTG MUSB driver issue? Frans Meulenbroeks
2009-02-27 17:56 ` Felipe Balbi [this message]
2009-02-28 10:46   ` Frans Meulenbroeks
2009-03-02  8:34     ` Gadiyar, Anand
2009-03-02 21:10       ` Frans Meulenbroeks

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=20090227175638.GE16801@frodo \
    --to=me@felipebalbi.com \
    --cc=beagleboard@googlegroups.com \
    --cc=fransmeulenbroeks@gmail.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