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: Mon, 20 Oct 2008 14:20:13 +0200 [thread overview]
Message-ID: <68676e00810200520n6d0fb283y2ae83a0048568017@mail.gmail.com> (raw)
In-Reply-To: <20081018224650.2edff23c@mjolnir.drzeus.cx>
On Sat, Oct 18, 2008 at 10:46 PM, Pierre Ossman <drzeus-mmc@drzeus.cx> wrote:
> On Tue, 14 Oct 2008 23:13:39 +0200
> "Luca Tettamanti" <kronos.it@gmail.com> wrote:
>>
>> I finally managed to capture a failure with debug enabled, I'm
>> attaching the log.
>
> It seems to be a transfer error at least as it is in a completely
> different area of the card compared to the first mail you sent.
>
>> To recap:
>> - heavy write loads sometimes result in a timeout
>> - reads seem unaffected (I read the card multiple times without errors)
>
> Looking at the dump, the controller seems to be doing the correct
> thing. The timeout mandated by the SD specification is 250 ms, and that
> time has passed if you look at the timestamps. If you look at some
> other writes further down, the card takes around 220 ms for the writes.
> IOW, it would seem that this card is cutting it a bit close and
> sometimes goes over the alloted time.
>
>> - doubling the timeout (as per my first patch) makes the timeout disappear
>
> Since it is the card that's the problem here, not the controller, we'd
> need to fix this in the core. Unfortunately the sdhci hardware is a bit
> inflexible so any change I make will result in a doubling of the
> timeout.
>
> Could you try modifying line 283 of drivers/mmc/core/core.c where it
> says "limit_us = 250000;" to 300000 instead?
300ms seems to be enough.
>> 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)
>
> What's the vendor and model of the failing card?
The card is from S3+, and it's branded "SD Excel" (el-cheapo 4GB card)
Luca
next prev parent reply other threads:[~2008-10-20 12:20 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
2008-10-14 21:21 ` Luca Tettamanti
2008-10-18 20:46 ` Pierre Ossman
2008-10-20 12:20 ` Luca Tettamanti [this message]
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=68676e00810200520n6d0fb283y2ae83a0048568017@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®