linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: zaurus: mmcblk0: error -110
Date: Tue, 12 Apr 2011 23:17:47 +0800	[thread overview]
Message-ID: <BANLkTikNEJEwq4cfr6cmTcHqcRfyGLM6Ww@mail.gmail.com> (raw)
In-Reply-To: <20110412151547.GC20815@atrey.karlin.mff.cuni.cz>

Hi Cyril,

Which model do you have? And check the corresponding board file if
card detect GPIO handling is doing right.

- eric

On Tue, Apr 12, 2011 at 11:15 PM, Cyril Hrubis <metan@ucw.cz> wrote:
> Hi!
> When I insert the mmc card to zaurus, it gets properly detected and prints some
> info into console. Mounting reading/writing files works fine.
>
> However when the card is removed (doesn't need to be mounted before), the
> removal is most likely not detected, so when I insert it again, no info is
> printed into console and moreover when I try to mount it zaurus goes into
> infinite loop printing:
>
> Buffer I/O error on device mmcblk0p1, logical block 9
> mmcblk0: error -110 sending status command
> mmcblk0: error -110 sending read/write command, response 0xb00, card status 0xb00
> end_request: I/O error, dev mmcblk0, sector 257
> Buffer I/O error on device mmcblk0p1, logical block 10
> mmcblk0: error -110 sending status command
> mmcblk0: error -110 sending read/write command, response 0xb00, card status 0xb00
> end_request: I/O error, dev mmcblk0, sector 258
> Buffer I/O error on device mmcblk0p1, logical block 11
> mmcblk0: error -110 sending status command
> mmcblk0: error -110 sending read/write command, response 0xb00, card status 0xb00
> end_request: I/O error, dev mmcblk0, sector 259
> Buffer I/O error on device mmcblk0p1, logical block 12
> mmcblk0: error -110 sending status command
> mmcblk0: error -110 sending read/write command, response 0xb00, card status 0xb00
> ...
>
> Related part of the .config:
>
> #
> # OTG and related infrastructure
> #
> # CONFIG_USB_GPIO_VBUS is not set
> # CONFIG_USB_ULPI is not set
> # CONFIG_NOP_USB_XCEIV is not set
> CONFIG_MMC=y
> # CONFIG_MMC_DEBUG is not set
> CONFIG_MMC_UNSAFE_RESUME=y
> # CONFIG_MMC_CLKGATE is not set
>
> #
> # MMC/SD/SDIO Card Drivers
> #
> CONFIG_MMC_BLOCK=y
> CONFIG_MMC_BLOCK_MINORS=8
> CONFIG_MMC_BLOCK_BOUNCE=y
> # CONFIG_SDIO_UART is not set
> # CONFIG_MMC_TEST is not set
>
> #
> # MMC/SD/SDIO Host Controller Drivers
> #
> CONFIG_MMC_PXA=y
>
> --
> metan
>

  reply	other threads:[~2011-04-12 15:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 15:15 zaurus: mmcblk0: error -110 Cyril Hrubis
2011-04-12 15:17 ` Eric Miao [this message]
2011-04-12 15:23   ` Cyril Hrubis
2011-04-12 15:52     ` Cyril Hrubis
2011-04-12 18:04       ` Pavel Machek
2011-04-13 17:10         ` Marek Vasut
2011-04-13 17:12           ` Marek Vasut
2011-04-12 19:24 ` Chris Ball
2011-04-12 19:39   ` Cyril Hrubis
2011-04-12 19:47     ` Chris Ball
2011-04-12 20:54       ` Cyril Hrubis
2011-04-12 21:21         ` Chris Ball
2011-04-12 21:39           ` Chris Ball
2011-04-12 22:43           ` Cyril Hrubis
2011-04-12 22:53             ` Chris Ball
2011-04-15 21:33               ` Cyril Hrubis

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=BANLkTikNEJEwq4cfr6cmTcHqcRfyGLM6Ww@mail.gmail.com \
    --to=eric.y.miao@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).