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: Fri, 3 Oct 2008 13:27:52 +0200	[thread overview]
Message-ID: <68676e00810030427g63c07643rf637ca894df795b2@mail.gmail.com> (raw)
In-Reply-To: <20081002101754.031d6710@mjolnir.drzeus.cx>

On Thu, Oct 2, 2008 at 10:17 AM, Pierre Ossman <drzeus-mmc@drzeus.cx> wrote:
> On Tue, 23 Sep 2008 23:24:59 +0200
> Luca Tettamanti <kronos.it@gmail.com> wrote:
>
>> Hi,
>> I'm seeing timeout errors when transfering "big" (over 1MB or so) files to a SD
>> card (small files are ok):
>>
>> [  251.956666] mmcblk0: error -110 transferring data
>> [  251.979810] end_request: I/O error, dev mmcblk0, sector 1572758
>
> Looks like the card died on you there. Did you build the kernel
> yourself? If so, it would be helpful if you could enable
> CONFIG_MMC_DEBUG and give me a complete dmesg dump from when this
> happens.

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:

[  187.158063] sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00000040
[  187.656190] mmc0: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 21 width
0 timing 0
[  187.658366] mmc0: clock 128906Hz busmode 1 powermode 2 cs 0 Vdd 21
width 0 timing 0
[  187.660500] mmc0: clock 128906Hz busmode 1 powermode 2 cs 1 Vdd 21
width 0 timing 0
[  187.661634] mmc0: starting CMD0 arg 00000000 flags 000000c0
[  187.662265] sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00000001
[  187.662283] mmc0: req done (CMD0): 0: 00000000 00000000 00000000 00000000
[  187.663461] mmc0: clock 128906Hz busmode 1 powermode 2 cs 0 Vdd 21
width 0 timing 0
[  187.664473] mmc0: starting CMD8 arg 000001aa flags 000002f5
[  187.665423] sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00000001
[  187.665439] mmc0: req done (CMD8): 0: 000001aa 00000000 00000000 00000000
[  187.665474] mmc0: starting CMD5 arg 00000000 flags 000002e1
[  187.666423] sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00018000
[  187.668435] mmc0: req failed (CMD5): -110, retrying...
[  187.669423] sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00018000
[  187.671424] mmc0: req failed (CMD5): -110, retrying...
[  187.672422] sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00018000
[  187.674423] mmc0: req failed (CMD5): -110, retrying...
[  187.675425] sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00018000
[  187.677436] mmc0: req done (CMD5): -110: 00000000 00000000 00000000 00000000
[  187.677683] mmc0: starting CMD55 arg 00000000 flags 000000f5
[  187.678754] sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00000001
[  187.678770] mmc0: req done (CMD55): 0: 00000120 00000000 00000000 00000000
[  187.678808] mmc0: starting CMD41 arg 00000000 flags 000000e1
[  187.679877] sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00000001
[  187.679893] mmc0: req done (CMD41): 0: 00ff8000 00000000 00000000 00000000
[  187.679995] mmc0: clock 128906Hz busmode 1 powermode 2 cs 0 Vdd 20
width 0 timing 0
[  187.680021] mmc0: clock 128906Hz busmode 1 powermode 2 cs 1 Vdd 20
width 0 timing 0
[cut 80MB of logs]

Is it possible that the error was generated by a faulty flash block?

Luca

  parent reply	other threads:[~2008-10-03 11:28 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 [this message]
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
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=68676e00810030427g63c07643rf637ca894df795b2@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®