All of lore.kernel.org
 help / color / mirror / Atom feed
From: tike64 <tike64@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] isp116x-hcd and usb_storage
Date: Thu, 20 Sep 2007 07:13:39 -0700 (PDT)	[thread overview]
Message-ID: <355489.19642.qm@web59211.mail.re1.yahoo.com> (raw)
In-Reply-To: <873ax98pbk.fsf@denx.de>

--- Markus Klotzb?cher wrote:
> tike64 <tike64@yahoo.com> writes:
> > At least one problem remains, though. I have tested it with a 165KB
> > file and one out of about five fatloads fails. Completion codes of
> > the first failed PTDs are 6 (PIDCheckFailure), 5
> > (DeviceNotResponding) and then always 0xf (propably device NAKing).
> > After 'usb reset' it works again for a while.
> >
> > Now I don't understand how transactions can fail with 6 or 5
> > occasionally. Are sticks known to be unreliable or should I suspect
> > my hardware? What should be done after that kind of failure?
> 
> Hard to say. Maybe it's a different timing issue, but could also be
> the stick misbehaving. Yes indeed some (usually noname) sticks have
> failed to work. Although you can never be sure I wouldn't suspect
your
> hardware if the stick is working properly under Linux.

Maybe Linux recovers gracefully somehow. The stick is Kingston.

> Can you test different sticks to see if that makes any difference?

Good idea, must dig other sticks from somewhere.

Meanwhile, I added retries also in case of those errors. I do the retry
with the remaining data of the transaction. Now it seems to pass over
the original error with a couple of retries but then fails with 8 (data
overrun) permanently ... to-be-continued-tomorrow

--

Timo



      ____________________________________________________________________________________
Don't let your dream ride pass you by. Make it a reality with Yahoo! Autos.
http://autos.yahoo.com/index.html
 

  reply	other threads:[~2007-09-20 14:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18  7:59 [U-Boot-Users] isp116x-hcd and usb_storage tike64
2007-09-18 10:39 ` Markus Klotzbücher
2007-09-18 11:14   ` tike64
2007-09-18 11:54     ` tike64
2007-09-18 14:56       ` Markus Klotzbücher
2007-09-19  5:46         ` tike64
2007-09-19  8:17           ` Markus Klotzbücher
2007-09-20 11:51             ` tike64
2007-09-20 12:59               ` Markus Klotzbücher
2007-09-20 14:13                 ` tike64 [this message]
2007-09-21 13:02                   ` tike64
2007-09-24  6:44                     ` Markus Klotzbücher
2007-09-24 12:01                       ` tike64

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=355489.19642.qm@web59211.mail.re1.yahoo.com \
    --to=tike64@yahoo.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.