linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Chua <jeff.chua.linux@gmail.com>
To: Adrian Hunter <adrian.hunter@nokia.com>,
	Chris Ball <cjb@laptop.org>, Pierre Ossman <pierre@ossman.eu>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: mmc sdhci mmcblk0: error -110 sending status command, retrying
Date: Tue, 7 Feb 2012 11:34:21 +0800	[thread overview]
Message-ID: <CAAJw_ZsryUFFFRCKdd9sQ7_38hjpVq37b6hhZDX5=qz8x1B+EQ@mail.gmail.com> (raw)

The SD slot on the Lenovo X220 is doesn't seems to work on
Linux-3.3.0-rc2. I haven't use SD for a while, so don't know which
linux version will work on the X220.


# cat .config
CONFIG_MMC=m
CONFIG_MMC_DEBUG=y
CONFIG_MMC_CLKGATE=y
CONFIG_MMC_BLOCK=m
CONFIG_MMC_BLOCK_MINORS=8
CONFIG_MMC_BLOCK_BOUNCE=y
CONFIG_MMC_SDHCI=m
CONFIG_MMC_SDHCI_PCI=m
CONFIG_MMC_RICOH_MMC=y


# lspcpi -v

0d:00.0 System peripheral: Ricoh Co Ltd Device e823 (rev 04) (prog-if 01)
        Subsystem: Lenovo Device 21da
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at f1500000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [78] Power Management version 3
        Capabilities: [80] Express Endpoint, MSI 00
        Kernel driver in use: sdhci-pci
        Kernel modules: sdhci-pci


# dmesg
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pci 0000:0d:00.0: SDHCI controller found [1180:e823] (rev 4)
sdhci-pci 0000:0d:00.0: found 1 slot(s)
sdhci [sdhci_add_host()]: mmc0: Auto-CMD23 unavailable
sdhci: =========== REGISTER DUMP (mmc0)===========
sdhci: Sys addr: 0x00000000 | Version:  0x00000502
sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
sdhci: Present:  0x01f70000 | Host ctl: 0x00000000
sdhci: Power:    0x00000000 | Blk gap:  0x00000000
sdhci: Wake-up:  0x00000000 | Clock:    0x00000000
sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
sdhci: Int enab: 0x00ff0003 | Sig enab: 0x00ff0003
sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
sdhci: Caps:     0x21e832b2 | Caps_1:   0x00008073
sdhci: Cmd:      0x00000000 | Max curr: 0x00000040
sdhci: Host ctl2: 0x00000000
sdhci: ===========================================

mmc0: req done (CMD18): 0: 00000900 00000000 00000000 00000000
mmc0:     0 bytes transferred: -84
mmc0:     (CMD12): -110: 00000000 00000000 00000000 00000000
mmc0: starting CMD13 arg b3680000 flags 00000195
sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00018000
mmc0: req done (CMD13): -110: 00000000 00000000 00000000 00000000
mmcblk0: error -110 sending status command, retrying
mmc0: starting CMD13 arg b3680000 flags 00000195
sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00018000
mmc0: req done (CMD13): -110: 00000000 00000000 00000000 00000000
mmcblk0: error -110 sending status command, retrying
mmc0: starting CMD13 arg b3680000 flags 00000195
sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00000001
mmc0: req done (CMD13): 0: 00800b00 00000000 00000000 00000000
mmc0: starting CMD12 arg 00000000 flags 0000049d
sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00000003
mmc0: req done (CMD12): 0: 00000b00 00000000 00000000 00000000
mmcblk0: error -110 sending stop command, original cmd response 0x900,
card status 0x800b00
mmcblk0: error -84 transferring data, sector 0, nr 32, cmd response
0x900, card status 0xb00
mmcblk0: retrying using single block read
mmc0: starting CMD17 arg 00000000 flags 000000b5
mmc0:     blksz 512 blocks 1 flags 00000200 tsac 100 ms nsac 0
sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00000001
sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00000002
mmc0: req done (CMD17): 0: 00000900 00000000 00000000 00000000
mmc0:     512 bytes transferred: 0
mmc0: starting CMD17 arg 00000001 flags 000000b5
mmc0:     blksz 512 blocks 1 flags 00000200 tsac 100 ms nsac 0
sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00000001
sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x00000002


Any help will be very much appreciated.

Thanks,
Jeff

             reply	other threads:[~2012-02-07  3:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07  3:34 Jeff Chua [this message]
2012-02-07  3:38 ` mmc sdhci mmcblk0: error -110 sending status command, retrying Chris Ball
2012-02-07  4:37   ` Jeff Chua
2012-02-07  8:32     ` Adrian Hunter
2012-02-07 10:40       ` Jeff Chua
2012-02-07 11:04         ` Adrian Hunter
2012-02-07 16:01           ` Jeff Chua
2012-02-07 16:04             ` Jeff Chua
2012-02-07 16:07               ` Jeff Chua
2012-02-07 18:33                 ` Jeff Chua
2012-02-07 23:45                   ` Jaehoon Chung
2012-02-08  1:09                     ` Jeff Chua
2012-02-08 19:09                       ` Philip Rakity
2012-02-10 16:18                         ` Jeff Chua
2012-02-10 20:28                           ` Philip Rakity
2012-02-11 10:55                             ` Jeff Chua
2012-02-13  4:41                               ` Jeff Chua
2012-02-13  5:16                                 ` Jeff Chua
2012-02-13  5:20                                   ` Jeff Chua
2012-02-15  4:41                                     ` Jeff Chua

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='CAAJw_ZsryUFFFRCKdd9sQ7_38hjpVq37b6hhZDX5=qz8x1B+EQ@mail.gmail.com' \
    --to=jeff.chua.linux@gmail.com \
    --cc=adrian.hunter@nokia.com \
    --cc=cjb@laptop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre@ossman.eu \
    /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).