mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SDHCI: timeout during data transfer
Date: Thu, 2 Oct 2008 10:17:54 +0200	[thread overview]
Message-ID: <20081002101754.031d6710@mjolnir.drzeus.cx> (raw)
In-Reply-To: <20080923212459.GA13888@dreamland.darkstar.lan>

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.

> kernel in use is 2.6.27-rc6, and this is the controller:
> 
> 09:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
> 09:01.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12)
> 09:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
> 09:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)
> 
> Googling around I found a patch[1] that introduced a quirk to address an
> off-by-one issue for the timeout value in certain controllers.
> 
> With this patch:
> 

The patch doubles the timeout, so something is clearly broken if that
solves the issue. I'd like to identify if it's the driver, controller
or card first though.

Are you experiencing this with just this card, or with all?

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

  reply	other threads:[~2008-10-02  8:18 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 [this message]
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
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=20081002101754.031d6710@mjolnir.drzeus.cx \
    --to=drzeus-mmc@drzeus.cx \
    --cc=kronos.it@gmail.com \
    --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®