mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luca Tettamanti" <kronos.it@gmail.com>
To: "Pierre Ossman" <drzeus-mmc@drzeus.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SDHCI: timeout during data transfer
Date: Tue, 14 Oct 2008 23:13:39 +0200	[thread overview]
Message-ID: <68676e00810141413w384882dbg53af93a1b522e0d3@mail.gmail.com> (raw)
In-Reply-To: <68676e00810140234o5e85f438l18058c907a7c6260@mail.gmail.com>

On Tue, Oct 14, 2008 at 11:34 AM, Luca Tettamanti <kronos.it@gmail.com> wrote:
> On Sun, Oct 12, 2008 at 10:52 AM, Pierre Ossman <drzeus-mmc@drzeus.cx> wrote:
>> On Fri, 3 Oct 2008 13:27:52 +0200
>> "Luca Tettamanti" <kronos.it@gmail.com> wrote:
>>>
>>> Hum, cannot reproduce (but it was consistently failing when I tested
>>> the patch... the only difference is a mkfs in between). I just got a
>>> few retries:
>>
>> A silly question, but did you also try disabling the debugging? Since
>> this is a timing issue, the debugging output could be just enough to
>> make the problem go away.
>
> Ok, I managed to reproduce without the debugging, but this time it
> took over a couple of GB before it started failing. Block numbers
> differ from the previous failures (so maybe it's not a cluster of
> broken blocks).
> Will go back and test with debugging enabled.

I finally managed to capture a failure with debug enabled, I'm
attaching the log.
To recap:
- heavy write loads sometimes result in a timeout
- reads seem unaffected (I read the card multiple times without errors)
- doubling the timeout (as per my first patch) makes the timeout disappear
- windows doesn't suffer from the issue

I've tested two other cards that do not show the problem, but they are
not "high speed":

mmc0: new high speed SD card at address 0002 (troubles)
vs:
mmc0: new SD card at address e624 (OK)

Luca

  reply	other threads:[~2008-10-14 21:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 21:24 Luca Tettamanti
2008-10-02  8:17 ` Pierre Ossman
2008-10-02  9:11   ` Luca Tettamanti
2008-10-03 11:27   ` Luca Tettamanti
2008-10-12  8:52     ` Pierre Ossman
2008-10-14  9:34       ` Luca Tettamanti
2008-10-14 21:13         ` Luca Tettamanti [this message]
2008-10-14 21:21           ` Luca Tettamanti
2008-10-18 20:46           ` Pierre Ossman
2008-10-20 12:20             ` Luca Tettamanti
2008-10-26 11:35               ` Pierre Ossman

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=68676e00810141413w384882dbg53af93a1b522e0d3@mail.gmail.com \
    --to=kronos.it@gmail.com \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®