A MMC card transfer issue

public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed

* A MMC card transfer issue
@ 2010-11-09  5:39 Tomoya MORINAGA
  2010-11-09  5:53 ` Kyungmin Park
  0 siblings, 1 reply; 26+ messages in thread
From: Tomoya MORINAGA @ 2010-11-09  5:39 UTC (permalink / raw)
  To: linux-mmc, linux-kernel; +Cc: Andrew", kok.howg.ewe

I am facing the issue about some MMC cards on Intel EG20T PCH (Platform Controller Hub).
The linux version is 2.6.36.
I can not transfer data the MMC cards (e.g. Transcned MMC card).
The card is 1 bit bus width. And the card is according to MMC specification V3.x.
And the EG20T has a 4 bit bus width capability 
Linux MMC standard driver decides the card bus width as 4 bit,
if the MMC specification version is larger than or equal to V4.0 like below.

linux/drivers/mmc/core/mmc.c

 505        /*
 506         * Activate wide bus (if supported).
 507         */
 508        if ((card->csd.mmca_vsn >= CSD_SPEC_VER_4) &&
 509            (host->caps & (MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA))) {
 510                unsigned ext_csd_bit, bus_width;
 511
 512                if (host->caps & MMC_CAP_8_BIT_DATA) {
 513                        ext_csd_bit = EXT_CSD_BUS_WIDTH_8;
 514                        bus_width = MMC_BUS_WIDTH_8;
 515                } else {
 516                        ext_csd_bit = EXT_CSD_BUS_WIDTH_4;
 517                        bus_width = MMC_BUS_WIDTH_4;
 518                }
 519
 520                err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
 521                                 EXT_CSD_BUS_WIDTH, ext_csd_bit);
 522
 523                if (err && err != -EBADMSG)
 524                        goto free_card;
 525
 526                if (err) {
 527                        printk(KERN_WARNING "%s: switch to bus width %d "
 528                               "failed\n", mmc_hostname(card->host),
 529                               1 << bus_width);
 530                        err = 0;
 531                } else {
 532                        mmc_set_bus_width(card->host, bus_width);
 533                }
 534        }
 535

However the MMC specification version id is the same as V3.x and V4.0.
Therefore the driver uses the 4 bit bus width for the MMC card 
even if the card has only 1 bit bus width.
I modified the driver to use 1 bit bus width only tentatively and confirmed that
we can mount the card and R/W correctly.

I think we can not support MMC_CAP_4_BIT_DATA or MMC_CAP_8_BIT_DATA in MMC V4.0.

How do you think ?

-- 
Thanks,
Tomoya MORINAGA(OKI SEMICONDUCTOR CO., LTD.)

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: A MMC card transfer issue
  2010-11-09  5:39 A MMC card transfer issue Tomoya MORINAGA
@ 2010-11-09  5:53 ` Kyungmin Park
  2010-11-09  7:29   ` Tomoya MORINAGA
  2010-11-11  2:59   ` Tomoya MORINAGA
  0 siblings, 2 replies; 26+ messages in thread
From: Kyungmin Park @ 2010-11-09  5:53 UTC (permalink / raw)
  To: Tomoya MORINAGA; +Cc: linux-mmc, linux-kernel, Andrew", kok.howg.ewe

2010/11/9 Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>:
> I am facing the issue about some MMC cards on Intel EG20T PCH (Platform Controller Hub).
> The linux version is 2.6.36.
> I can not transfer data the MMC cards (e.g. Transcned MMC card).
> The card is 1 bit bus width. And the card is according to MMC specification V3.x.
> And the EG20T has a 4 bit bus width capability
> Linux MMC standard driver decides the card bus width as 4 bit,
> if the MMC specification version is larger than or equal to V4.0 like below.
>
> linux/drivers/mmc/core/mmc.c
>
>  505        /*
>  506         * Activate wide bus (if supported).
>  507         */
>  508        if ((card->csd.mmca_vsn >= CSD_SPEC_VER_4) &&
>  509            (host->caps & (MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA))) {
>  510                unsigned ext_csd_bit, bus_width;
>  511
>  512                if (host->caps & MMC_CAP_8_BIT_DATA) {
>  513                        ext_csd_bit = EXT_CSD_BUS_WIDTH_8;
>  514                        bus_width = MMC_BUS_WIDTH_8;
>  515                } else {
>  516                        ext_csd_bit = EXT_CSD_BUS_WIDTH_4;
>  517                        bus_width = MMC_BUS_WIDTH_4;
>  518                }
>  519
>  520                err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
>  521                                 EXT_CSD_BUS_WIDTH, ext_csd_bit);
>  522
>  523                if (err && err != -EBADMSG)
>  524                        goto free_card;
>  525
>  526                if (err) {
>  527                        printk(KERN_WARNING "%s: switch to bus width %d "
>  528                               "failed\n", mmc_hostname(card->host),
>  529                               1 << bus_width);
>  530                        err = 0;
>  531                } else {
>  532                        mmc_set_bus_width(card->host, bus_width);
>  533                }
>  534        }
>  535
>
> However the MMC specification version id is the same as V3.x and V4.0.
> Therefore the driver uses the 4 bit bus width for the MMC card
> even if the card has only 1 bit bus width.
> I modified the driver to use 1 bit bus width only tentatively and confirmed that
> we can mount the card and R/W correctly.
>
> I think we can not support MMC_CAP_4_BIT_DATA or MMC_CAP_8_BIT_DATA in MMC V4.0.
>
> How do you think ?

You can find a patch for 4-bit support. the problem is there's some
bug related so it set the 4 & 8 bit support both.
So line 512 is always true. you can just remove the one line like this.

It's quirk-and-dirty patch. now we try to find a generic solution to
solve this issue.
--- a/drivers/mmc/host/sdhci.c
+++ b/drivers/mmc/host/sdhci.c
@@ -1849,7 +1849,7 @@ int sdhci_add_host(struct sdhci_host *host)
        mmc->caps |= MMC_CAP_SDIO_IRQ;

        if (!(host->quirks & SDHCI_QUIRK_FORCE_1_BIT_DATA))
-               mmc->caps |= MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA;
+               mmc->caps |= MMC_CAP_4_BIT_DATA;

        if (caps & SDHCI_CAN_DO_HISPD)
                mmc->caps |= MMC_CAP_SD_HIGHSPEED | MMC_CAP_MMC_HIGHSPEED;

Thank you,
Kyungmin Park
>
> --
> Thanks,
> Tomoya MORINAGA(OKI SEMICONDUCTOR CO., LTD.)
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: A MMC card transfer issue
  2010-11-09  5:53 ` Kyungmin Park
@ 2010-11-09  7:29   ` Tomoya MORINAGA
  2010-11-11  2:59   ` Tomoya MORINAGA
  1 sibling, 0 replies; 26+ messages in thread
From: Tomoya MORINAGA @ 2010-11-09  7:29 UTC (permalink / raw)
  To: Kyungmin Park; +Cc: linux-mmc, linux-kernel, Andrew", kok.howg.ewe

Hi Park,

Thank you for your information.
I will try it soon.

Thanks,
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.
----- Original Message ----- 
From: "Kyungmin Park" <kmpark@infradead.org>
To: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
Cc: <linux-mmc@vger.kernel.org>; <linux-kernel@vger.kernel.org>; "Andrew"" <andrew.chih.howe.khor@intel.com>;
<kok.howg.ewe@intel.com>
Sent: Tuesday, November 09, 2010 2:53 PM
Subject: Re: A MMC card transfer issue


> 2010/11/9 Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>:
> > I am facing the issue about some MMC cards on Intel EG20T PCH (Platform Controller Hub).
> > The linux version is 2.6.36.
> > I can not transfer data the MMC cards (e.g. Transcned MMC card).
> > The card is 1 bit bus width. And the card is according to MMC specification V3.x.
> > And the EG20T has a 4 bit bus width capability
> > Linux MMC standard driver decides the card bus width as 4 bit,
> > if the MMC specification version is larger than or equal to V4.0 like below.
> >
> > linux/drivers/mmc/core/mmc.c
> >
> > 505 /*
> > 506 * Activate wide bus (if supported).
> > 507 */
> > 508 if ((card->csd.mmca_vsn >= CSD_SPEC_VER_4) &&
> > 509 (host->caps & (MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA))) {
> > 510 unsigned ext_csd_bit, bus_width;
> > 511
> > 512 if (host->caps & MMC_CAP_8_BIT_DATA) {
> > 513 ext_csd_bit = EXT_CSD_BUS_WIDTH_8;
> > 514 bus_width = MMC_BUS_WIDTH_8;
> > 515 } else {
> > 516 ext_csd_bit = EXT_CSD_BUS_WIDTH_4;
> > 517 bus_width = MMC_BUS_WIDTH_4;
> > 518 }
> > 519
> > 520 err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
> > 521 EXT_CSD_BUS_WIDTH, ext_csd_bit);
> > 522
> > 523 if (err && err != -EBADMSG)
> > 524 goto free_card;
> > 525
> > 526 if (err) {
> > 527 printk(KERN_WARNING "%s: switch to bus width %d "
> > 528 "failed\n", mmc_hostname(card->host),
> > 529 1 << bus_width);
> > 530 err = 0;
> > 531 } else {
> > 532 mmc_set_bus_width(card->host, bus_width);
> > 533 }
> > 534 }
> > 535
> >
> > However the MMC specification version id is the same as V3.x and V4.0.
> > Therefore the driver uses the 4 bit bus width for the MMC card
> > even if the card has only 1 bit bus width.
> > I modified the driver to use 1 bit bus width only tentatively and confirmed that
> > we can mount the card and R/W correctly.
> >
> > I think we can not support MMC_CAP_4_BIT_DATA or MMC_CAP_8_BIT_DATA in MMC V4.0.
> >
> > How do you think ?
>
> You can find a patch for 4-bit support. the problem is there's some
> bug related so it set the 4 & 8 bit support both.
> So line 512 is always true. you can just remove the one line like this.
>
> It's quirk-and-dirty patch. now we try to find a generic solution to
> solve this issue.
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
> @@ -1849,7 +1849,7 @@ int sdhci_add_host(struct sdhci_host *host)
>         mmc->caps |= MMC_CAP_SDIO_IRQ;
>
>         if (!(host->quirks & SDHCI_QUIRK_FORCE_1_BIT_DATA))
> -               mmc->caps |= MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA;
> +               mmc->caps |= MMC_CAP_4_BIT_DATA;
>
>         if (caps & SDHCI_CAN_DO_HISPD)
>                 mmc->caps |= MMC_CAP_SD_HIGHSPEED | MMC_CAP_MMC_HIGHSPEED;
>
> Thank you,
> Kyungmin Park
> >
> > --
> > Thanks,
> > Tomoya MORINAGA(OKI SEMICONDUCTOR CO., LTD.)
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: A MMC card transfer issue
  2010-11-09  5:53 ` Kyungmin Park
  2010-11-09  7:29   ` Tomoya MORINAGA
@ 2010-11-11  2:59   ` Tomoya MORINAGA
  2010-12-01  1:08     ` Tomoya MORINAGA
  1 sibling, 1 reply; 26+ messages in thread
From: Tomoya MORINAGA @ 2010-11-11  2:59 UTC (permalink / raw)
  To: Kyungmin Park; +Cc: kok.howg.ewe, Andrew", linux-kernel, linux-mmc

Hi Park,

Though I  tried to patch yours to "sdhci.c" of linux-2.6.36,
but it seems your patch has already patched in linux-2.6.36.

Using this linux, MMC card is not recognized.
Inserting the MMC card, I saw the following erro message.

[   11.035441] sdhci: Secure Digital Host Controller Interface driver
[   11.035450] sdhci: Copyright(c) Pierre Ossman
[   11.058295] sdhci-pci 0000:02:04.0: SDHCI controller found [8086:8809] (rev 1)
[   11.058342]   alloc irq_desc for 18 on node -1
[   11.058350]   alloc kstat_irqs on node -1
[   11.058373] sdhci-pci 0000:02:04.0: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[   11.058385] sdhci-pci 0000:02:04.0: Invalid iomem size. You may experience problems.
[   11.058487] sdhci-pci 0000:02:04.0: setting latency timer to 64
[   11.058623] Registered led device: mmc0::
[   11.058736] mmc0: SDHCI controller on PCI [0000:02:04.0] using DMA
[   11.058774] sdhci-pci 0000:02:04.1: SDHCI controller found [8086:880a] (rev 1)
[   11.058816] sdhci-pci 0000:02:04.1: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[   11.058828] sdhci-pci 0000:02:04.1: Invalid iomem size. You may experience problems.
[   11.058904] sdhci-pci 0000:02:04.1: setting latency timer to 64
[   11.059047] Registered led device: mmc1::
[   11.059153] mmc1: SDHCI controller on PCI [0000:02:04.1] using DMA
[   11.547645] mmc1: new high speed SD card at address 0ec7
[   11.629400] mmcblk0: mmc1:0ec7 SV02G 1.87 GiB (ro)
[   11.630314]  mmcblk0: p1
[   12.076459] gzip used greatest stack depth: 6008 bytes left
[   12.321795] ip used greatest stack depth: 5724 bytes left
[   13.786510] EXT3-fs (dm-0): using internal journal
[   13.887463] EXT3-fs: barriers not enabled
[   13.887872] kjournald starting.  Commit interval 5 seconds
[   13.888154] EXT3-fs (sda1): using internal journal
[   13.888178] EXT3-fs (sda1): mounted filesystem with writeback data mode
[   23.183874] Adding 2064380k swap on /dev/mapper/VolGroup00-LogVol01.  Priority:-1 extents:1 across:2064380k
[   39.171225] gconfd-2 used greatest stack depth: 5692 bytes left
[   86.545435] metacity[2318]: segfault at 0 ip 080aa093 sp bfd899a0 error 4 in metacity[8048000+82000]
[  115.124784] hda-intel: Invalid position buffer, using LPIB read method instead.
[  115.124821] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
[  346.630117] mmc1: card 0ec7 removed
[  408.266730] mmc1: new MMC card at address 0001
[  408.268142] mmcblk0: mmc1:0001 MMC    1.87 GiB
[  408.275970] mmcblk0: retrying using single block read
[  408.278451] mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
[  408.278464] end_request: I/O error, dev mmcblk0, sector 0
[  408.280966] mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
[  408.280978] end_request: I/O error, dev mmcblk0, sector 1


I have suspected mmc.c is buggy.
I tried to disable like the following in "mmc_init_card".
As a result, the MMC card to be recognized correctly.
What's do you think ?

 */
static int mmc_init_card(struct mmc_host *host, u32 ocr,
 struct mmc_card *oldcard)
{
......

 /*
  * Activate wide bus (if supported).
  */
#if 0 //101111
 if ((card->csd.mmca_vsn >= CSD_SPEC_VER_4) &&
     (host->caps & (MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA))) {
  unsigned ext_csd_bit, bus_width;

  if (host->caps & MMC_CAP_8_BIT_DATA) {
   ext_csd_bit = EXT_CSD_BUS_WIDTH_8;
   bus_width = MMC_BUS_WIDTH_8;
  } else {
   ext_csd_bit = EXT_CSD_BUS_WIDTH_4;
   bus_width = MMC_BUS_WIDTH_4;
  }

  err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
     EXT_CSD_BUS_WIDTH, ext_csd_bit);

  if (err && err != -EBADMSG)
   goto free_card;

  if (err) {
   printk(KERN_WARNING "%s: switch to bus width %d "
          "failed\n", mmc_hostname(card->host),
          1 << bus_width);
   err = 0;
  } else {
   mmc_set_bus_width(card->host, bus_width);
  }
 }
#endif //101111




------
Thanks,

Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.


----- Original Message ----- 
From: "Kyungmin Park" <kmpark@infradead.org>
To: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
Cc: <linux-mmc@vger.kernel.org>; <linux-kernel@vger.kernel.org>; "Andrew"" <andrew.chih.howe.khor@intel.com>;
<kok.howg.ewe@intel.com>
Sent: Tuesday, November 09, 2010 2:53 PM
Subject: Re: A MMC card transfer issue


> 2010/11/9 Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>:
> > I am facing the issue about some MMC cards on Intel EG20T PCH (Platform Controller Hub).
> > The linux version is 2.6.36.
> > I can not transfer data the MMC cards (e.g. Transcned MMC card).
> > The card is 1 bit bus width. And the card is according to MMC specification V3.x.
> > And the EG20T has a 4 bit bus width capability
> > Linux MMC standard driver decides the card bus width as 4 bit,
> > if the MMC specification version is larger than or equal to V4.0 like below.
> >
> > linux/drivers/mmc/core/mmc.c
> >
> > 505 /*
> > 506 * Activate wide bus (if supported).
> > 507 */
> > 508 if ((card->csd.mmca_vsn >= CSD_SPEC_VER_4) &&
> > 509 (host->caps & (MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA))) {
> > 510 unsigned ext_csd_bit, bus_width;
> > 511
> > 512 if (host->caps & MMC_CAP_8_BIT_DATA) {
> > 513 ext_csd_bit = EXT_CSD_BUS_WIDTH_8;
> > 514 bus_width = MMC_BUS_WIDTH_8;
> > 515 } else {
> > 516 ext_csd_bit = EXT_CSD_BUS_WIDTH_4;
> > 517 bus_width = MMC_BUS_WIDTH_4;
> > 518 }
> > 519
> > 520 err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
> > 521 EXT_CSD_BUS_WIDTH, ext_csd_bit);
> > 522
> > 523 if (err && err != -EBADMSG)
> > 524 goto free_card;
> > 525
> > 526 if (err) {
> > 527 printk(KERN_WARNING "%s: switch to bus width %d "
> > 528 "failed\n", mmc_hostname(card->host),
> > 529 1 << bus_width);
> > 530 err = 0;
> > 531 } else {
> > 532 mmc_set_bus_width(card->host, bus_width);
> > 533 }
> > 534 }
> > 535
> >
> > However the MMC specification version id is the same as V3.x and V4.0.
> > Therefore the driver uses the 4 bit bus width for the MMC card
> > even if the card has only 1 bit bus width.
> > I modified the driver to use 1 bit bus width only tentatively and confirmed that
> > we can mount the card and R/W correctly.
> >
> > I think we can not support MMC_CAP_4_BIT_DATA or MMC_CAP_8_BIT_DATA in MMC V4.0.
> >
> > How do you think ?
>
> You can find a patch for 4-bit support. the problem is there's some
> bug related so it set the 4 & 8 bit support both.
> So line 512 is always true. you can just remove the one line like this.
>
> It's quirk-and-dirty patch. now we try to find a generic solution to
> solve this issue.
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
> @@ -1849,7 +1849,7 @@ int sdhci_add_host(struct sdhci_host *host)
>         mmc->caps |= MMC_CAP_SDIO_IRQ;
>
>         if (!(host->quirks & SDHCI_QUIRK_FORCE_1_BIT_DATA))
> -               mmc->caps |= MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA;
> +               mmc->caps |= MMC_CAP_4_BIT_DATA;
>
>         if (caps & SDHCI_CAN_DO_HISPD)
>                 mmc->caps |= MMC_CAP_SD_HIGHSPEED | MMC_CAP_MMC_HIGHSPEED;
>
> Thank you,
> Kyungmin Park
> >
> > --
> > Thanks,
> > Tomoya MORINAGA(OKI SEMICONDUCTOR CO., LTD.)
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: A MMC card transfer issue
  2010-11-11  2:59   ` Tomoya MORINAGA
@ 2010-12-01  1:08     ` Tomoya MORINAGA
       [not found]       ` <2D50F985-2383-4406-8514-DFE462A5F546@marvell.com>
  0 siblings, 1 reply; 26+ messages in thread
From: Tomoya MORINAGA @ 2010-12-01  1:08 UTC (permalink / raw)
  To: Kyungmin Park; +Cc: linux-mmc, linux-kernel, Andrew", kok.howg.ewe

Hi Park,

How's the issue going ?

With best regards.
---
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.
----- Original Message ----- 
From: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
To: "Kyungmin Park" <kmpark@infradead.org>
Cc: <kok.howg.ewe@intel.com>; "Andrew"" <andrew.chih.howe.khor@intel.com>; <linux-kernel@vger.kernel.org>;
<linux-mmc@vger.kernel.org>
Sent: Thursday, November 11, 2010 11:59 AM
Subject: Re: A MMC card transfer issue


> Hi Park,
>
> Though I  tried to patch yours to "sdhci.c" of linux-2.6.36,
> but it seems your patch has already patched in linux-2.6.36.
>
> Using this linux, MMC card is not recognized.
> Inserting the MMC card, I saw the following erro message.
>
> [   11.035441] sdhci: Secure Digital Host Controller Interface driver
> [   11.035450] sdhci: Copyright(c) Pierre Ossman
> [   11.058295] sdhci-pci 0000:02:04.0: SDHCI controller found [8086:8809] (rev 1)
> [   11.058342]   alloc irq_desc for 18 on node -1
> [   11.058350]   alloc kstat_irqs on node -1
> [   11.058373] sdhci-pci 0000:02:04.0: PCI INT C -> GSI 18 (level, low) -> IRQ 18
> [   11.058385] sdhci-pci 0000:02:04.0: Invalid iomem size. You may experience problems.
> [   11.058487] sdhci-pci 0000:02:04.0: setting latency timer to 64
> [   11.058623] Registered led device: mmc0::
> [   11.058736] mmc0: SDHCI controller on PCI [0000:02:04.0] using DMA
> [   11.058774] sdhci-pci 0000:02:04.1: SDHCI controller found [8086:880a] (rev 1)
> [   11.058816] sdhci-pci 0000:02:04.1: PCI INT C -> GSI 18 (level, low) -> IRQ 18
> [   11.058828] sdhci-pci 0000:02:04.1: Invalid iomem size. You may experience problems.
> [   11.058904] sdhci-pci 0000:02:04.1: setting latency timer to 64
> [   11.059047] Registered led device: mmc1::
> [   11.059153] mmc1: SDHCI controller on PCI [0000:02:04.1] using DMA
> [   11.547645] mmc1: new high speed SD card at address 0ec7
> [   11.629400] mmcblk0: mmc1:0ec7 SV02G 1.87 GiB (ro)
> [   11.630314]  mmcblk0: p1
> [   12.076459] gzip used greatest stack depth: 6008 bytes left
> [   12.321795] ip used greatest stack depth: 5724 bytes left
> [   13.786510] EXT3-fs (dm-0): using internal journal
> [   13.887463] EXT3-fs: barriers not enabled
> [   13.887872] kjournald starting.  Commit interval 5 seconds
> [   13.888154] EXT3-fs (sda1): using internal journal
> [   13.888178] EXT3-fs (sda1): mounted filesystem with writeback data mode
> [   23.183874] Adding 2064380k swap on /dev/mapper/VolGroup00-LogVol01.  Priority:-1 extents:1 across:2064380k
> [   39.171225] gconfd-2 used greatest stack depth: 5692 bytes left
> [   86.545435] metacity[2318]: segfault at 0 ip 080aa093 sp bfd899a0 error 4 in metacity[8048000+82000]
> [  115.124784] hda-intel: Invalid position buffer, using LPIB read method instead.
> [  115.124821] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
> [  346.630117] mmc1: card 0ec7 removed
> [  408.266730] mmc1: new MMC card at address 0001
> [  408.268142] mmcblk0: mmc1:0001 MMC    1.87 GiB
> [  408.275970] mmcblk0: retrying using single block read
> [  408.278451] mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
> [  408.278464] end_request: I/O error, dev mmcblk0, sector 0
> [  408.280966] mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
> [  408.280978] end_request: I/O error, dev mmcblk0, sector 1
>
>
> I have suspected mmc.c is buggy.
> I tried to disable like the following in "mmc_init_card".
> As a result, the MMC card to be recognized correctly.
> What's do you think ?
>
>  */
> static int mmc_init_card(struct mmc_host *host, u32 ocr,
>  struct mmc_card *oldcard)
> {
> ......
>
>  /*
>   * Activate wide bus (if supported).
>   */
> #if 0 //101111
>  if ((card->csd.mmca_vsn >= CSD_SPEC_VER_4) &&
>      (host->caps & (MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA))) {
>   unsigned ext_csd_bit, bus_width;
>
>   if (host->caps & MMC_CAP_8_BIT_DATA) {
>    ext_csd_bit = EXT_CSD_BUS_WIDTH_8;
>    bus_width = MMC_BUS_WIDTH_8;
>   } else {
>    ext_csd_bit = EXT_CSD_BUS_WIDTH_4;
>    bus_width = MMC_BUS_WIDTH_4;
>   }
>
>   err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
>      EXT_CSD_BUS_WIDTH, ext_csd_bit);
>
>   if (err && err != -EBADMSG)
>    goto free_card;
>
>   if (err) {
>    printk(KERN_WARNING "%s: switch to bus width %d "
>           "failed\n", mmc_hostname(card->host),
>           1 << bus_width);
>    err = 0;
>   } else {
>    mmc_set_bus_width(card->host, bus_width);
>   }
>  }
> #endif //101111
>
>
>
>
> ------
> Thanks,
>
> Tomoya MORINAGA
> OKI SEMICONDUCTOR CO., LTD.
>
>
> ----- Original Message ----- 
> From: "Kyungmin Park" <kmpark@infradead.org>
> To: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
> Cc: <linux-mmc@vger.kernel.org>; <linux-kernel@vger.kernel.org>; "Andrew"" <andrew.chih.howe.khor@intel.com>;
> <kok.howg.ewe@intel.com>
> Sent: Tuesday, November 09, 2010 2:53 PM
> Subject: Re: A MMC card transfer issue
>
>
> > 2010/11/9 Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>:
> > > I am facing the issue about some MMC cards on Intel EG20T PCH (Platform Controller Hub).
> > > The linux version is 2.6.36.
> > > I can not transfer data the MMC cards (e.g. Transcned MMC card).
> > > The card is 1 bit bus width. And the card is according to MMC specification V3.x.
> > > And the EG20T has a 4 bit bus width capability
> > > Linux MMC standard driver decides the card bus width as 4 bit,
> > > if the MMC specification version is larger than or equal to V4.0 like below.
> > >
> > > linux/drivers/mmc/core/mmc.c
> > >
> > > 505 /*
> > > 506 * Activate wide bus (if supported).
> > > 507 */
> > > 508 if ((card->csd.mmca_vsn >= CSD_SPEC_VER_4) &&
> > > 509 (host->caps & (MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA))) {
> > > 510 unsigned ext_csd_bit, bus_width;
> > > 511
> > > 512 if (host->caps & MMC_CAP_8_BIT_DATA) {
> > > 513 ext_csd_bit = EXT_CSD_BUS_WIDTH_8;
> > > 514 bus_width = MMC_BUS_WIDTH_8;
> > > 515 } else {
> > > 516 ext_csd_bit = EXT_CSD_BUS_WIDTH_4;
> > > 517 bus_width = MMC_BUS_WIDTH_4;
> > > 518 }
> > > 519
> > > 520 err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
> > > 521 EXT_CSD_BUS_WIDTH, ext_csd_bit);
> > > 522
> > > 523 if (err && err != -EBADMSG)
> > > 524 goto free_card;
> > > 525
> > > 526 if (err) {
> > > 527 printk(KERN_WARNING "%s: switch to bus width %d "
> > > 528 "failed\n", mmc_hostname(card->host),
> > > 529 1 << bus_width);
> > > 530 err = 0;
> > > 531 } else {
> > > 532 mmc_set_bus_width(card->host, bus_width);
> > > 533 }
> > > 534 }
> > > 535
> > >
> > > However the MMC specification version id is the same as V3.x and V4.0.
> > > Therefore the driver uses the 4 bit bus width for the MMC card
> > > even if the card has only 1 bit bus width.
> > > I modified the driver to use 1 bit bus width only tentatively and confirmed that
> > > we can mount the card and R/W correctly.
> > >
> > > I think we can not support MMC_CAP_4_BIT_DATA or MMC_CAP_8_BIT_DATA in MMC V4.0.
> > >
> > > How do you think ?
> >
> > You can find a patch for 4-bit support. the problem is there's some
> > bug related so it set the 4 & 8 bit support both.
> > So line 512 is always true. you can just remove the one line like this.
> >
> > It's quirk-and-dirty patch. now we try to find a generic solution to
> > solve this issue.
> > --- a/drivers/mmc/host/sdhci.c
> > +++ b/drivers/mmc/host/sdhci.c
> > @@ -1849,7 +1849,7 @@ int sdhci_add_host(struct sdhci_host *host)
> >         mmc->caps |= MMC_CAP_SDIO_IRQ;
> >
> >         if (!(host->quirks & SDHCI_QUIRK_FORCE_1_BIT_DATA))
> > -               mmc->caps |= MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA;
> > +               mmc->caps |= MMC_CAP_4_BIT_DATA;
> >
> >         if (caps & SDHCI_CAN_DO_HISPD)
> >                 mmc->caps |= MMC_CAP_SD_HIGHSPEED | MMC_CAP_MMC_HIGHSPEED;
> >
> > Thank you,
> > Kyungmin Park
> > >
> > > --
> > > Thanks,
> > > Tomoya MORINAGA(OKI SEMICONDUCTOR CO., LTD.)
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> >
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

^ permalink raw reply	[flat|nested] 26+ messages in thread

[parent not found: <2D50F985-2383-4406-8514-DFE462A5F546@marvell.com>]

* Re: A MMC card transfer issue
       [not found]       ` <2D50F985-2383-4406-8514-DFE462A5F546@marvell.com>
@ 2010-12-01  3:15         ` Philip Rakity
       [not found]         ` <4D2E0464ABB54FFF9C10583336E27879@hacdom.okisemi.com>
  1 sibling, 0 replies; 26+ messages in thread
From: Philip Rakity @ 2010-12-01  3:15 UTC (permalink / raw)
  To: Kyungmin Park
  Cc: Tomoya MORINAGA, linux-mmc@vger.kernel.org,
	"\"\\\"Andrew\\\\\\\"\\\" <andrew.chih.howe.khor@intel.com>\" <andrew.chih.howe.khor@intel.com>" <andrew.chih.howe.khor@intel.com>,
	kok.howg.ewe@intel.com


resend as plain text

On Nov 30, 2010, at 5:31 PM, Philip Rakity wrote:

> 
> take the 8 bit patch that chris put on the mailing list.  It may fix this.
> 
> Hi Philip,
> 
> On Sun, Nov 21, 2010 at 11:17:09AM -0800, Philip Rakity wrote:
>> a) QUIRK removed for 8 bit support since platform issue - not quirk
>> b) platform Flag defined for sdhci-pxa.c and plat-pxa
>> c) comments added to sdhci.c on usage
> 
> Thanks very much, I'll plan on sending this to Linus tomorrow, along
> with the rest of my .37 queue, unless there are any more review
> comments from anyone.
> 
> http://git.kernel.org/?p=linux/kernel/git/cjb/mmc.git;a=commit;h=15ec44611904be0dcc97b84c29fbf964e5e2b36f
> 
> -- 
> Chris Ball   <cjb@laptop.org>   <http://printf.net/>
> One Laptop Per Child
> 
> On Nov 30, 2010, at 5:08 PM, Tomoya MORINAGA wrote:
> 
>> Hi Park,
>> 
>> How's the issue going ?
>> 
>> With best regards.
>> ---
>> Tomoya MORINAGA
>> OKI SEMICONDUCTOR CO., LTD.
>> ----- Original Message ----- 
>> From: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
>> To: "Kyungmin Park" <kmpark@infradead.org>
>> Cc: <kok.howg.ewe@intel.com>; "Andrew"" <andrew.chih.howe.khor@intel.com>; <linux-kernel@vger.kernel.org>;
>> <linux-mmc@vger.kernel.org>
>> Sent: Thursday, November 11, 2010 11:59 AM
>> Subject: Re: A MMC card transfer issue
>> 
>> 
>>> Hi Park,
>>> 
>>> Though I  tried to patch yours to "sdhci.c" of linux-2.6.36,
>>> but it seems your patch has already patched in linux-2.6.36.
>>> 
>>> Using this linux, MMC card is not recognized.
>>> Inserting the MMC card, I saw the following erro message.
>>> 
>>> [   11.035441] sdhci: Secure Digital Host Controller Interface driver
>>> [   11.035450] sdhci: Copyright(c) Pierre Ossman
>>> [   11.058295] sdhci-pci 0000:02:04.0: SDHCI controller found [8086:8809] (rev 1)
>>> [   11.058342]   alloc irq_desc for 18 on node -1
>>> [   11.058350]   alloc kstat_irqs on node -1
>>> [   11.058373] sdhci-pci 0000:02:04.0: PCI INT C -> GSI 18 (level, low) -> IRQ 18
>>> [   11.058385] sdhci-pci 0000:02:04.0: Invalid iomem size. You may experience problems.
>>> [   11.058487] sdhci-pci 0000:02:04.0: setting latency timer to 64
>>> [   11.058623] Registered led device: mmc0::
>>> [   11.058736] mmc0: SDHCI controller on PCI [0000:02:04.0] using DMA
>>> [   11.058774] sdhci-pci 0000:02:04.1: SDHCI controller found [8086:880a] (rev 1)
>>> [   11.058816] sdhci-pci 0000:02:04.1: PCI INT C -> GSI 18 (level, low) -> IRQ 18
>>> [   11.058828] sdhci-pci 0000:02:04.1: Invalid iomem size. You may experience problems.
>>> [   11.058904] sdhci-pci 0000:02:04.1: setting latency timer to 64
>>> [   11.059047] Registered led device: mmc1::
>>> [   11.059153] mmc1: SDHCI controller on PCI [0000:02:04.1] using DMA
>>> [   11.547645] mmc1: new high speed SD card at address 0ec7
>>> [   11.629400] mmcblk0: mmc1:0ec7 SV02G 1.87 GiB (ro)
>>> [   11.630314]  mmcblk0: p1
>>> [   12.076459] gzip used greatest stack depth: 6008 bytes left
>>> [   12.321795] ip used greatest stack depth: 5724 bytes left
>>> [   13.786510] EXT3-fs (dm-0): using internal journal
>>> [   13.887463] EXT3-fs: barriers not enabled
>>> [   13.887872] kjournald starting.  Commit interval 5 seconds
>>> [   13.888154] EXT3-fs (sda1): using internal journal
>>> [   13.888178] EXT3-fs (sda1): mounted filesystem with writeback data mode
>>> [   23.183874] Adding 2064380k swap on /dev/mapper/VolGroup00-LogVol01.  Priority:-1 extents:1 across:2064380k
>>> [   39.171225] gconfd-2 used greatest stack depth: 5692 bytes left
>>> [   86.545435] metacity[2318]: segfault at 0 ip 080aa093 sp bfd899a0 error 4 in metacity[8048000+82000]
>>> [  115.124784] hda-intel: Invalid position buffer, using LPIB read method instead.
>>> [  115.124821] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
>>> [  346.630117] mmc1: card 0ec7 removed
>>> [  408.266730] mmc1: new MMC card at address 0001
>>> [  408.268142] mmcblk0: mmc1:0001 MMC    1.87 GiB
>>> [  408.275970] mmcblk0: retrying using single block read
>>> [  408.278451] mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
>>> [  408.278464] end_request: I/O error, dev mmcblk0, sector 0
>>> [  408.280966] mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
>>> [  408.280978] end_request: I/O error, dev mmcblk0, sector 1
>>> 
>>> 
>>> I have suspected mmc.c is buggy.
>>> I tried to disable like the following in "mmc_init_card".
>>> As a result, the MMC card to be recognized correctly.
>>> What's do you think ?
>>> 
>>> */
>>> static int mmc_init_card(struct mmc_host *host, u32 ocr,
>>> struct mmc_card *oldcard)
>>> {
>>> ......
>>> 
>>> /*
>>>  * Activate wide bus (if supported).
>>>  */
>>> #if 0 //101111
>>> if ((card->csd.mmca_vsn >= CSD_SPEC_VER_4) &&
>>>     (host->caps & (MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA))) {
>>>  unsigned ext_csd_bit, bus_width;
>>> 
>>>  if (host->caps & MMC_CAP_8_BIT_DATA) {
>>>   ext_csd_bit = EXT_CSD_BUS_WIDTH_8;
>>>   bus_width = MMC_BUS_WIDTH_8;
>>>  } else {
>>>   ext_csd_bit = EXT_CSD_BUS_WIDTH_4;
>>>   bus_width = MMC_BUS_WIDTH_4;
>>>  }
>>> 
>>>  err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
>>>     EXT_CSD_BUS_WIDTH, ext_csd_bit);
>>> 
>>>  if (err && err != -EBADMSG)
>>>   goto free_card;
>>> 
>>>  if (err) {
>>>   printk(KERN_WARNING "%s: switch to bus width %d "
>>>          "failed\n", mmc_hostname(card->host),
>>>          1 << bus_width);
>>>   err = 0;
>>>  } else {
>>>   mmc_set_bus_width(card->host, bus_width);
>>>  }
>>> }
>>> #endif //101111
>>> 
>>> 
>>> 
>>> 
>>> ------
>>> Thanks,
>>> 
>>> Tomoya MORINAGA
>>> OKI SEMICONDUCTOR CO., LTD.
>>> 
>>> 
>>> ----- Original Message ----- 
>>> From: "Kyungmin Park" <kmpark@infradead.org>
>>> To: "Tomoya MORINAGA" <tomoya-linux@dsn.okisemi.com>
>>> Cc: <linux-mmc@vger.kernel.org>; <linux-kernel@vger.kernel.org>; "Andrew"" <andrew.chih.howe.khor@intel.com>;
>>> <kok.howg.ewe@intel.com>
>>> Sent: Tuesday, November 09, 2010 2:53 PM
>>> Subject: Re: A MMC card transfer issue
>>> 
>>> 
>>>> 2010/11/9 Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>:
>>>>> I am facing the issue about some MMC cards on Intel EG20T PCH (Platform Controller Hub).
>>>>> The linux version is 2.6.36.
>>>>> I can not transfer data the MMC cards (e.g. Transcned MMC card).
>>>>> The card is 1 bit bus width. And the card is according to MMC specification V3.x.
>>>>> And the EG20T has a 4 bit bus width capability
>>>>> Linux MMC standard driver decides the card bus width as 4 bit,
>>>>> if the MMC specification version is larger than or equal to V4.0 like below.
>>>>> 
>>>>> linux/drivers/mmc/core/mmc.c
>>>>> 
>>>>> 505 /*
>>>>> 506 * Activate wide bus (if supported).
>>>>> 507 */
>>>>> 508 if ((card->csd.mmca_vsn >= CSD_SPEC_VER_4) &&
>>>>> 509 (host->caps & (MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA))) {
>>>>> 510 unsigned ext_csd_bit, bus_width;
>>>>> 511
>>>>> 512 if (host->caps & MMC_CAP_8_BIT_DATA) {
>>>>> 513 ext_csd_bit = EXT_CSD_BUS_WIDTH_8;
>>>>> 514 bus_width = MMC_BUS_WIDTH_8;
>>>>> 515 } else {
>>>>> 516 ext_csd_bit = EXT_CSD_BUS_WIDTH_4;
>>>>> 517 bus_width = MMC_BUS_WIDTH_4;
>>>>> 518 }
>>>>> 519
>>>>> 520 err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
>>>>> 521 EXT_CSD_BUS_WIDTH, ext_csd_bit);
>>>>> 522
>>>>> 523 if (err && err != -EBADMSG)
>>>>> 524 goto free_card;
>>>>> 525
>>>>> 526 if (err) {
>>>>> 527 printk(KERN_WARNING "%s: switch to bus width %d "
>>>>> 528 "failed\n", mmc_hostname(card->host),
>>>>> 529 1 << bus_width);
>>>>> 530 err = 0;
>>>>> 531 } else {
>>>>> 532 mmc_set_bus_width(card->host, bus_width);
>>>>> 533 }
>>>>> 534 }
>>>>> 535
>>>>> 
>>>>> However the MMC specification version id is the same as V3.x and V4.0.
>>>>> Therefore the driver uses the 4 bit bus width for the MMC card
>>>>> even if the card has only 1 bit bus width.
>>>>> I modified the driver to use 1 bit bus width only tentatively and confirmed that
>>>>> we can mount the card and R/W correctly.
>>>>> 
>>>>> I think we can not support MMC_CAP_4_BIT_DATA or MMC_CAP_8_BIT_DATA in MMC V4.0.
>>>>> 
>>>>> How do you think ?
>>>> 
>>>> You can find a patch for 4-bit support. the problem is there's some
>>>> bug related so it set the 4 & 8 bit support both.
>>>> So line 512 is always true. you can just remove the one line like this.
>>>> 
>>>> It's quirk-and-dirty patch. now we try to find a generic solution to
>>>> solve this issue.
>>>> --- a/drivers/mmc/host/sdhci.c
>>>> +++ b/drivers/mmc/host/sdhci.c
>>>> @@ -1849,7 +1849,7 @@ int sdhci_add_host(struct sdhci_host *host)
>>>>        mmc->caps |= MMC_CAP_SDIO_IRQ;
>>>> 
>>>>        if (!(host->quirks & SDHCI_QUIRK_FORCE_1_BIT_DATA))
>>>> -               mmc->caps |= MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA;
>>>> +               mmc->caps |= MMC_CAP_4_BIT_DATA;
>>>> 
>>>>        if (caps & SDHCI_CAN_DO_HISPD)
>>>>                mmc->caps |= MMC_CAP_SD_HIGHSPEED | MMC_CAP_MMC_HIGHSPEED;
>>>> 
>>>> Thank you,
>>>> Kyungmin Park
>>>>> 
>>>>> --
>>>>> Thanks,
>>>>> Tomoya MORINAGA(OKI SEMICONDUCTOR CO., LTD.)
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>>>>> the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>> 
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>> Please read the FAQ at  http://www.tux.org/lkml/
>>>> 
>>> 
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>> Please read the FAQ at  http://www.tux.org/lkml/
>>> 
>> 
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


^ permalink raw reply	[flat|nested] 26+ messages in thread

[parent not found: <4D2E0464ABB54FFF9C10583336E27879@hacdom.okisemi.com>]

* Re: A MMC card transfer issue
       [not found]         ` <4D2E0464ABB54FFF9C10583336E27879@hacdom.okisemi.com>
@ 2011-01-19  0:59           ` Philip Rakity
  2011-01-19  1:29             ` Tomoya MORINAGA
  2011-01-19  6:05           ` Philip Rakity
  1 sibling, 1 reply; 26+ messages in thread
From: Philip Rakity @ 2011-01-19  0:59 UTC (permalink / raw)
  To: Tomoya MORINAGA
  Cc: Kyungmin Park, linux-mmc@vger.kernel.org,
	linux-kernel@vger.kernel.org, andrew.chih.howe.khor@intel.com,
	kok.howg.ewe@intel.com


I just looked in the 2.6.37 code and the fix is not there.  It is in the 2.6.37 linus  tree.  

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/mmc/core/mmc.c;h=16006ef153fe081c2f0f0a09cd4443ce7f3c49a1;hb=a25cecce88194b2edf38b8c3b1665e9318eb2d22

Chris Ball who maintains this should know when it will be pushed upwards.

Philip 
On Jan 18, 2011, at 4:36 PM, Tomoya MORINAGA wrote:

> Hi Philip,
>  
> On Wednesday, December 01, 2010 10:31 AM, Philip Rakity wrote:
> > Thanks very much, I'll plan on sending this to Linus tomorrow, along
> > with the rest of my .37 queue, unless there are any more review
> > comments from anyone.
>  
> We tried to use the MMC card like the following on kernel-2.6.37.
>  
> On Tuesday, November 09, 2010 2:40 PM, Tomoya MORINAGA wrote:
> > I am facing the issue about some MMC cards on Intel EG20T PCH 
> > (Platform Controller Hub).
> > The linux version is 2.6.36.
> > I can not transfer data the MMC cards (e.g. Transcned MMC card).
> > The card is 1 bit bus width. And the card is according to MMC 
> > specification V3.x.
> > And the EG20T has a 4 bit bus width capability Linux MMC 
> > standard driver decides the card bus width as 4 bit, if the 
> > MMC specification version is larger than or equal to V4.0 like below.
>  
> However it seems the issue remains to be seen.
> Have you fixed the MMC unrecognized issue in kernel-2.6.37?
>  
> Thanks,
> -----------------------------------------
> Tomoya MORINAGA
> OKI SEMICONDUCTOR CO., LTD.


^ permalink raw reply	[flat|nested] 26+ messages in thread

* RE: A MMC card transfer issue
  2011-01-19  0:59           ` Philip Rakity
@ 2011-01-19  1:29             ` Tomoya MORINAGA
  2011-01-19  1:41               ` Chris Ball
  0 siblings, 1 reply; 26+ messages in thread
From: Tomoya MORINAGA @ 2011-01-19  1:29 UTC (permalink / raw)
  To: 'Philip Rakity', cjb
  Cc: 'Kyungmin Park', linux-mmc, linux-kernel,
	andrew.chih.howe.khor, kok.howg.ewe, Toshiharu Okada

Hi Chris,

On Wednesday, January 19, 2011 10:00 AM, Philip Rakity wrote:
> I just looked in the 2.6.37 code and the fix is not there.  
> It is in the 2.6.37 linus  tree.  
> 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.g
> it;a=blob;f=drivers/mmc/core/mmc.c;h=16006ef153fe081c2f0f0a09c
> d4443ce7f3c49a1;hb=a25cecce88194b2edf38b8c3b1665e9318eb2d22
> 
> Chris Ball who maintains this should know when it will be 
> pushed upwards.

Do you know when the above patch will be integrated to kernel ?

Thanks,
-----------------------------------------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.


^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: A MMC card transfer issue
  2011-01-19  1:29             ` Tomoya MORINAGA
@ 2011-01-19  1:41               ` Chris Ball
  2011-01-19  3:12                 ` Philip Rakity
  0 siblings, 1 reply; 26+ messages in thread
From: Chris Ball @ 2011-01-19  1:41 UTC (permalink / raw)
  To: Tomoya MORINAGA
  Cc: 'Philip Rakity', 'Kyungmin Park', linux-mmc,
	linux-kernel, andrew.chih.howe.khor, kok.howg.ewe,
	Toshiharu Okada

On Wed, Jan 19, 2011 at 10:29:21AM +0900, Tomoya MORINAGA wrote:
> On Wednesday, January 19, 2011 10:00 AM, Philip Rakity wrote:
> > I just looked in the 2.6.37 code and the fix is not there.  
> > It is in the 2.6.37 linus  tree.  
> > 
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.g
> > it;a=blob;f=drivers/mmc/core/mmc.c;h=16006ef153fe081c2f0f0a09c
> > d4443ce7f3c49a1;hb=a25cecce88194b2edf38b8c3b1665e9318eb2d22
> 
> Do you know when the above patch will be integrated to kernel ?

I don't understand, sorry.  The link is to a file, not a patch, and
Philip's statement above talks about a patch being in 2.6.37 but not
being in 2.6.37, which I don't understand either.

Looking back farther in the thread, I think you're both talking about:
http://git.kernel.org/?p=linux/kernel/git/cjb/mmc.git;a=commit;h=15ec44611904be0dcc97b84c29fbf964e5e2b36f

This patch was merged into Linus' 2.6.37-rc4 on Nov 27 2010, and
released as part of 2.6.37.

Can you elaborate on your question, if it's still outstanding?

Thanks,

-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: A MMC card transfer issue
  2011-01-19  1:41               ` Chris Ball
@ 2011-01-19  3:12                 ` Philip Rakity
  0 siblings, 0 replies; 26+ messages in thread
From: Philip Rakity @ 2011-01-19  3:12 UTC (permalink / raw)
  To: Chris Ball
  Cc: Tomoya MORINAGA, Kyungmin Park, linux-mmc@vger.kernel.org,
	linux-kernel@vger.kernel.org, andrew.chih.howe.khor@intel.com,
	kok.howg.ewe@intel.com, Toshiharu Okada


Chris,

transcend card is 1 bit card.  Requires bus_width patches.

Philip

On Jan 18, 2011, at 5:41 PM, Chris Ball wrote:

> On Wed, Jan 19, 2011 at 10:29:21AM +0900, Tomoya MORINAGA wrote:
>> On Wednesday, January 19, 2011 10:00 AM, Philip Rakity wrote:
>>> I just looked in the 2.6.37 code and the fix is not there.  
>>> It is in the 2.6.37 linus  tree.  
>>> 
>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.g
>>> it;a=blob;f=drivers/mmc/core/mmc.c;h=16006ef153fe081c2f0f0a09c
>>> d4443ce7f3c49a1;hb=a25cecce88194b2edf38b8c3b1665e9318eb2d22
>> 
>> Do you know when the above patch will be integrated to kernel ?
> 
> I don't understand, sorry.  The link is to a file, not a patch, and
> Philip's statement above talks about a patch being in 2.6.37 but not
> being in 2.6.37, which I don't understand either.
> 
> Looking back farther in the thread, I think you're both talking about:
> http://git.kernel.org/?p=linux/kernel/git/cjb/mmc.git;a=commit;h=15ec44611904be0dcc97b84c29fbf964e5e2b36f
> 
> This patch was merged into Linus' 2.6.37-rc4 on Nov 27 2010, and
> released as part of 2.6.37.
> 
> Can you elaborate on your question, if it's still outstanding?
> 
> Thanks,
> 
> -- 
> Chris Ball   <cjb@laptop.org>   <http://printf.net/>
> One Laptop Per Child


^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: A MMC card transfer issue
       [not found]         ` <4D2E0464ABB54FFF9C10583336E27879@hacdom.okisemi.com>
  2011-01-19  0:59           ` Philip Rakity
@ 2011-01-19  6:05           ` Philip Rakity
  2011-01-19  6:30             ` Tomoya MORINAGA
  2011-01-19 17:42             ` Chris Ball
  1 sibling, 2 replies; 26+ messages in thread
From: Philip Rakity @ 2011-01-19  6:05 UTC (permalink / raw)
  To: Tomoya MORINAGA
  Cc: Kyungmin Park, linux-mmc@vger.kernel.org,
	linux-kernel@vger.kernel.org, andrew.chih.howe.khor@intel.com,
	kok.howg.ewe@intel.com


For 1 bit transcend cards you need these 2 patches.


>From 22113efd00491310da802f3b1a9a66cfcf415fac Mon Sep 17 00:00:00 2001
From: Aries Lee <arieslee@jmicron.com>
Date: Wed, 15 Dec 2010 08:14:24 +0100
Subject: [PATCH] mmc: Test bus-width for old MMC devices

Some old MMC devices fail with the 4/8 bits the driver tries to use
exclusively.  This patch adds a test for the given bus setup and falls
back to the lower bit mode (until 1-bit mode) when the test fails.

[Major rework and refactoring by tiwai]
[Quirk addition and many fixes by prakity]

Signed-off-by: Aries Lee <arieslee@jmicron.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Philip Rakity <prakity@marvell.com>
Tested-by: Philip Rakity <prakity@marvell.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
---
 drivers/mmc/core/mmc.c     |   76 ++++++++++++++++++++-------------
 drivers/mmc/core/mmc_ops.c |  101 ++++++++++++++++++++++++++++++++++++++++++++
 drivers/mmc/core/mmc_ops.h |    1 +
 drivers/mmc/host/sdhci.c   |    7 +++-
 drivers/mmc/host/sdhci.h   |    1 +
 include/linux/mmc/host.h   |    1 +
 include/linux/mmc/mmc.h    |    2 +
 7 files changed, 159 insertions(+), 30 deletions(-)

diff --git a/drivers/mmc/core/mmc.c b/drivers/mmc/core/mmc.c
index 76bb621..1d8409f 100644
--- a/drivers/mmc/core/mmc.c
+++ b/drivers/mmc/core/mmc.c
@@ -534,39 +534,57 @@ static int mmc_init_card(struct mmc_host *host, u32 ocr,
 	 */
 	if ((card->csd.mmca_vsn >= CSD_SPEC_VER_4) &&
 	    (host->caps & (MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA))) {
-		unsigned ext_csd_bit, bus_width;
-
-		if (host->caps & MMC_CAP_8_BIT_DATA) {
-			if (ddr)
-				ext_csd_bit = EXT_CSD_DDR_BUS_WIDTH_8;
-			else
-				ext_csd_bit = EXT_CSD_BUS_WIDTH_8;
-			bus_width = MMC_BUS_WIDTH_8;
-		} else {
-			if (ddr)
-				ext_csd_bit = EXT_CSD_DDR_BUS_WIDTH_4;
-			else
-				ext_csd_bit = EXT_CSD_BUS_WIDTH_4;
-			bus_width = MMC_BUS_WIDTH_4;
+		static unsigned ext_csd_bits[][2] = {
+			{ EXT_CSD_BUS_WIDTH_8, EXT_CSD_DDR_BUS_WIDTH_8 },
+			{ EXT_CSD_BUS_WIDTH_4, EXT_CSD_DDR_BUS_WIDTH_4 },
+			{ EXT_CSD_BUS_WIDTH_1, EXT_CSD_BUS_WIDTH_1 },
+		};
+		static unsigned bus_widths[] = {
+			MMC_BUS_WIDTH_8,
+			MMC_BUS_WIDTH_4,
+			MMC_BUS_WIDTH_1
+		};
+		unsigned idx, bus_width = 0;
+
+		if (host->caps & MMC_CAP_8_BIT_DATA)
+			idx = 0;
+		else
+			idx = 1;
+		for (; idx < ARRAY_SIZE(bus_widths); idx++) {
+			bus_width = bus_widths[idx];
+			if (bus_width == MMC_BUS_WIDTH_1)
+				ddr = 0; /* no DDR for 1-bit width */
+			err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
+					 EXT_CSD_BUS_WIDTH,
+					 ext_csd_bits[idx][0]);
+			if (!err) {
+				/*
+				 * If controller can't handle bus width test,
+				 * use the highest bus width to maintain
+				 * compatibility with previous MMC behavior.
+				 */
+				if (!(host->caps & MMC_CAP_BUS_WIDTH_TEST))
+					break;
+				mmc_set_bus_width_ddr(card->host,
+						      bus_width, MMC_SDR_MODE);
+				err = mmc_bus_test(card, bus_width);
+				if (!err)
+					break;
+			}
 		}
 
-		err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
-				 EXT_CSD_BUS_WIDTH, ext_csd_bit);
-
-		if (err && err != -EBADMSG)
-			goto free_card;
-
+		if (!err && ddr) {
+			err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
+					EXT_CSD_BUS_WIDTH,
+					ext_csd_bits[idx][1]);
+		}
 		if (err) {
 			printk(KERN_WARNING "%s: switch to bus width %d ddr %d "
-			       "failed\n", mmc_hostname(card->host),
-			       1 << bus_width, ddr);
-			err = 0;
-		} else {
-			if (ddr)
-				mmc_card_set_ddr_mode(card);
-			else
-				ddr = MMC_SDR_MODE;
-
+				"failed\n", mmc_hostname(card->host),
+				1 << bus_width, ddr);
+			goto free_card;
+		} else if (ddr) {
+			mmc_card_set_ddr_mode(card);
 			mmc_set_bus_width_ddr(card->host, bus_width, ddr);
 		}
 	}
diff --git a/drivers/mmc/core/mmc_ops.c b/drivers/mmc/core/mmc_ops.c
index 326447c..60842f8 100644
--- a/drivers/mmc/core/mmc_ops.c
+++ b/drivers/mmc/core/mmc_ops.c
@@ -462,3 +462,104 @@ int mmc_send_status(struct mmc_card *card, u32 *status)
 	return 0;
 }
 
+static int
+mmc_send_bus_test(struct mmc_card *card, struct mmc_host *host, u8 opcode,
+		  u8 len)
+{
+	struct mmc_request mrq;
+	struct mmc_command cmd;
+	struct mmc_data data;
+	struct scatterlist sg;
+	u8 *data_buf;
+	u8 *test_buf;
+	int i, err;
+	static u8 testdata_8bit[8] = { 0x55, 0xaa, 0, 0, 0, 0, 0, 0 };
+	static u8 testdata_4bit[4] = { 0x5a, 0, 0, 0 };
+
+	/* dma onto stack is unsafe/nonportable, but callers to this
+	 * routine normally provide temporary on-stack buffers ...
+	 */
+	data_buf = kmalloc(len, GFP_KERNEL);
+	if (!data_buf)
+		return -ENOMEM;
+
+	if (len == 8)
+		test_buf = testdata_8bit;
+	else if (len == 4)
+		test_buf = testdata_4bit;
+	else {
+		printk(KERN_ERR "%s: Invalid bus_width %d\n",
+		       mmc_hostname(host), len);
+		kfree(data_buf);
+		return -EINVAL;
+	}
+
+	if (opcode == MMC_BUS_TEST_W)
+		memcpy(data_buf, test_buf, len);
+
+	memset(&mrq, 0, sizeof(struct mmc_request));
+	memset(&cmd, 0, sizeof(struct mmc_command));
+	memset(&data, 0, sizeof(struct mmc_data));
+
+	mrq.cmd = &cmd;
+	mrq.data = &data;
+	cmd.opcode = opcode;
+	cmd.arg = 0;
+
+	/* NOTE HACK:  the MMC_RSP_SPI_R1 is always correct here, but we
+	 * rely on callers to never use this with "native" calls for reading
+	 * CSD or CID.  Native versions of those commands use the R2 type,
+	 * not R1 plus a data block.
+	 */
+	cmd.flags = MMC_RSP_SPI_R1 | MMC_RSP_R1 | MMC_CMD_ADTC;
+
+	data.blksz = len;
+	data.blocks = 1;
+	if (opcode == MMC_BUS_TEST_R)
+		data.flags = MMC_DATA_READ;
+	else
+		data.flags = MMC_DATA_WRITE;
+
+	data.sg = &sg;
+	data.sg_len = 1;
+	sg_init_one(&sg, data_buf, len);
+	mmc_wait_for_req(host, &mrq);
+	err = 0;
+	if (opcode == MMC_BUS_TEST_R) {
+		for (i = 0; i < len / 4; i++)
+			if ((test_buf[i] ^ data_buf[i]) != 0xff) {
+				err = -EIO;
+				break;
+			}
+	}
+	kfree(data_buf);
+
+	if (cmd.error)
+		return cmd.error;
+	if (data.error)
+		return data.error;
+
+	return err;
+}
+
+int mmc_bus_test(struct mmc_card *card, u8 bus_width)
+{
+	int err, width;
+
+	if (bus_width == MMC_BUS_WIDTH_8)
+		width = 8;
+	else if (bus_width == MMC_BUS_WIDTH_4)
+		width = 4;
+	else if (bus_width == MMC_BUS_WIDTH_1)
+		return 0; /* no need for test */
+	else
+		return -EINVAL;
+
+	/*
+	 * Ignore errors from BUS_TEST_W.  BUS_TEST_R will fail if there
+	 * is a problem.  This improves chances that the test will work.
+	 */
+	mmc_send_bus_test(card, card->host, MMC_BUS_TEST_W, width);
+	err = mmc_send_bus_test(card, card->host, MMC_BUS_TEST_R, width);
+	return err;
+}
diff --git a/drivers/mmc/core/mmc_ops.h b/drivers/mmc/core/mmc_ops.h
index 653eb8e..e6d44b8 100644
--- a/drivers/mmc/core/mmc_ops.h
+++ b/drivers/mmc/core/mmc_ops.h
@@ -26,6 +26,7 @@ int mmc_send_cid(struct mmc_host *host, u32 *cid);
 int mmc_spi_read_ocr(struct mmc_host *host, int highcap, u32 *ocrp);
 int mmc_spi_set_crc(struct mmc_host *host, int use_crc);
 int mmc_card_sleepawake(struct mmc_host *host, int sleep);
+int mmc_bus_test(struct mmc_card *card, u8 bus_width);
 
 #endif
 
diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
index 5569886..d5febe5 100644
--- a/drivers/mmc/host/sdhci.c
+++ b/drivers/mmc/host/sdhci.c
@@ -23,6 +23,7 @@
 
 #include <linux/leds.h>
 
+#include <linux/mmc/mmc.h>
 #include <linux/mmc/host.h>
 
 #include "sdhci.h"
@@ -1521,7 +1522,11 @@ static void sdhci_data_irq(struct sdhci_host *host, u32 intmask)
 
 	if (intmask & SDHCI_INT_DATA_TIMEOUT)
 		host->data->error = -ETIMEDOUT;
-	else if (intmask & (SDHCI_INT_DATA_CRC | SDHCI_INT_DATA_END_BIT))
+	else if (intmask & SDHCI_INT_DATA_END_BIT)
+		host->data->error = -EILSEQ;
+	else if ((intmask & SDHCI_INT_DATA_CRC) &&
+		SDHCI_GET_CMD(sdhci_readw(host, SDHCI_COMMAND))
+			!= MMC_BUS_TEST_R)
 		host->data->error = -EILSEQ;
 	else if (intmask & SDHCI_INT_ADMA_ERROR) {
 		printk(KERN_ERR "%s: ADMA error\n", mmc_hostname(host->mmc));
diff --git a/drivers/mmc/host/sdhci.h b/drivers/mmc/host/sdhci.h
index 1efe7dc..6e0969e 100644
--- a/drivers/mmc/host/sdhci.h
+++ b/drivers/mmc/host/sdhci.h
@@ -52,6 +52,7 @@
 #define  SDHCI_CMD_RESP_SHORT_BUSY 0x03
 
 #define SDHCI_MAKE_CMD(c, f) (((c & 0xff) << 8) | (f & 0xff))
+#define SDHCI_GET_CMD(c) ((c>>8) & 0x3f)
 
 #define SDHCI_RESPONSE		0x10
 
diff --git a/include/linux/mmc/host.h b/include/linux/mmc/host.h
index 3a85e73..bcb793e 100644
--- a/include/linux/mmc/host.h
+++ b/include/linux/mmc/host.h
@@ -172,6 +172,7 @@ struct mmc_host {
 #define MMC_CAP_1_2V_DDR	(1 << 12)	/* can support */
 						/* DDR mode at 1.2V */
 #define MMC_CAP_POWER_OFF_CARD	(1 << 13)	/* Can power off after boot */
+#define MMC_CAP_BUS_WIDTH_TEST	(1 << 14)	/* CMD14/CMD19 bus width ok */
 
 	mmc_pm_flag_t		pm_caps;	/* supported pm features */
 
diff --git a/include/linux/mmc/mmc.h b/include/linux/mmc/mmc.h
index 956fbd87..612301f 100644
--- a/include/linux/mmc/mmc.h
+++ b/include/linux/mmc/mmc.h
@@ -40,7 +40,9 @@
 #define MMC_READ_DAT_UNTIL_STOP  11   /* adtc [31:0] dadr        R1  */
 #define MMC_STOP_TRANSMISSION    12   /* ac                      R1b */
 #define MMC_SEND_STATUS          13   /* ac   [31:16] RCA        R1  */
+#define MMC_BUS_TEST_R           14   /* adtc                    R1  */
 #define MMC_GO_INACTIVE_STATE    15   /* ac   [31:16] RCA            */
+#define MMC_BUS_TEST_W           19   /* adtc                    R1  */
 #define MMC_SPI_READ_OCR         58   /* spi                  spi_R3 */
 #define MMC_SPI_CRC_ON_OFF       59   /* spi  [0:0] flag      spi_R1 */
 
-- 
1.7.3.5



>From 08c82dfad2458f8f9b83126224a85e7ea9e2b046 Mon Sep 17 00:00:00 2001
From: Takashi Iwai <tiwai@suse.de>
Date: Wed, 22 Dec 2010 09:59:44 +0100
Subject: [PATCH] mmc: fix mmc_set_bus_width_ddr() call without bus-width-test cap

With the bus-width test patch, mmc_set_bus_width*() isn't called properly
when the driver doesn't set MMC_CAP_BUS_WIDTH and no DDR mode.
This patch fixes the regression by moving the call up before the cap test.

Signed-off-by: Takashi Iwai <tiwai@suse.de>
Reviewed-by: Chris Ball <cjb@laptop.org>
Signed-off-by: Chris Ball <cjb@laptop.org>
---
 drivers/mmc/core/mmc.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/mmc/core/mmc.c b/drivers/mmc/core/mmc.c
index 1d8409f..c86dd73 100644
--- a/drivers/mmc/core/mmc.c
+++ b/drivers/mmc/core/mmc.c
@@ -558,6 +558,8 @@ static int mmc_init_card(struct mmc_host *host, u32 ocr,
 					 EXT_CSD_BUS_WIDTH,
 					 ext_csd_bits[idx][0]);
 			if (!err) {
+				mmc_set_bus_width_ddr(card->host,
+						      bus_width, MMC_SDR_MODE);
 				/*
 				 * If controller can't handle bus width test,
 				 * use the highest bus width to maintain
@@ -565,8 +567,6 @@ static int mmc_init_card(struct mmc_host *host, u32 ocr,
 				 */
 				if (!(host->caps & MMC_CAP_BUS_WIDTH_TEST))
 					break;
-				mmc_set_bus_width_ddr(card->host,
-						      bus_width, MMC_SDR_MODE);
 				err = mmc_bus_test(card, bus_width);
 				if (!err)
 					break;
-- 
1.7.3.5



On Jan 18, 2011, at 4:36 PM, Tomoya MORINAGA wrote:

> Hi Philip,
>  
> On Wednesday, December 01, 2010 10:31 AM, Philip Rakity wrote:
> > Thanks very much, I'll plan on sending this to Linus tomorrow, along
> > with the rest of my .37 queue, unless there are any more review
> > comments from anyone.
>  
> We tried to use the MMC card like the following on kernel-2.6.37.
>  
> On Tuesday, November 09, 2010 2:40 PM, Tomoya MORINAGA wrote:
> > I am facing the issue about some MMC cards on Intel EG20T PCH 
> > (Platform Controller Hub).
> > The linux version is 2.6.36.
> > I can not transfer data the MMC cards (e.g. Transcned MMC card).
> > The card is 1 bit bus width. And the card is according to MMC 
> > specification V3.x.
> > And the EG20T has a 4 bit bus width capability Linux MMC 
> > standard driver decides the card bus width as 4 bit, if the 
> > MMC specification version is larger than or equal to V4.0 like below.
>  
> However it seems the issue remains to be seen.
> Have you fixed the MMC unrecognized issue in kernel-2.6.37?
>  
> Thanks,
> -----------------------------------------
> Tomoya MORINAGA
> OKI SEMICONDUCTOR CO., LTD.

^ permalink raw reply related	[flat|nested] 26+ messages in thread

* RE: A MMC card transfer issue
  2011-01-19  6:05           ` Philip Rakity
@ 2011-01-19  6:30             ` Tomoya MORINAGA
  2011-01-19 17:42             ` Chris Ball
  1 sibling, 0 replies; 26+ messages in thread
From: Tomoya MORINAGA @ 2011-01-19  6:30 UTC (permalink / raw)
  To: 'Philip Rakity', cjb
  Cc: 'Kyungmin Park', linux-mmc, linux-kernel,
	andrew.chih.howe.khor, kok.howg.ewe, Toshiharu Okada

[-- Attachment #1: Type: text/plain, Size: 13692 bytes --]

Hi Philip, Chris

> For 1 bit transcend cards you need these 2 patches.
Thank you for your information.
It seems these patches aren't applied for kernel-2.6.37, right ?

Will you apply these patches for kernel-2.6.38?

BTW, I attached dmesg log when inserts MMC card with kernel-2.6.37.

Thanks,
-----------------------------------------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.
 

> -----Original Message-----
> From: Philip Rakity [mailto:prakity@marvell.com] 
> Sent: Wednesday, January 19, 2011 3:05 PM
> To: Tomoya MORINAGA
> Cc: Kyungmin Park; linux-mmc@vger.kernel.org; 
> linux-kernel@vger.kernel.org; 
> andrew.chih.howe.khor@intel.com; kok.howg.ewe@intel.com
> Subject: Re: A MMC card transfer issue
> 
> 
> For 1 bit transcend cards you need these 2 patches.
> 
> 
> From 22113efd00491310da802f3b1a9a66cfcf415fac Mon Sep 17 00:00:00 2001
> From: Aries Lee <arieslee@jmicron.com>
> Date: Wed, 15 Dec 2010 08:14:24 +0100
> Subject: [PATCH] mmc: Test bus-width for old MMC devices
> 
> Some old MMC devices fail with the 4/8 bits the driver tries 
> to use exclusively.  This patch adds a test for the given bus 
> setup and falls back to the lower bit mode (until 1-bit mode) 
> when the test fails.
> 
> [Major rework and refactoring by tiwai]
> [Quirk addition and many fixes by prakity]
> 
> Signed-off-by: Aries Lee <arieslee@jmicron.com>
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> Signed-off-by: Philip Rakity <prakity@marvell.com>
> Tested-by: Philip Rakity <prakity@marvell.com>
> Signed-off-by: Chris Ball <cjb@laptop.org>
> ---
>  drivers/mmc/core/mmc.c     |   76 ++++++++++++++++++++-------------
>  drivers/mmc/core/mmc_ops.c |  101 
> ++++++++++++++++++++++++++++++++++++++++++++
>  drivers/mmc/core/mmc_ops.h |    1 +
>  drivers/mmc/host/sdhci.c   |    7 +++-
>  drivers/mmc/host/sdhci.h   |    1 +
>  include/linux/mmc/host.h   |    1 +
>  include/linux/mmc/mmc.h    |    2 +
>  7 files changed, 159 insertions(+), 30 deletions(-)
> 
> diff --git a/drivers/mmc/core/mmc.c b/drivers/mmc/core/mmc.c 
> index 76bb621..1d8409f 100644
> --- a/drivers/mmc/core/mmc.c
> +++ b/drivers/mmc/core/mmc.c
> @@ -534,39 +534,57 @@ static int mmc_init_card(struct 
> mmc_host *host, u32 ocr,
>  	 */
>  	if ((card->csd.mmca_vsn >= CSD_SPEC_VER_4) &&
>  	    (host->caps & (MMC_CAP_4_BIT_DATA | MMC_CAP_8_BIT_DATA))) {
> -		unsigned ext_csd_bit, bus_width;
> -
> -		if (host->caps & MMC_CAP_8_BIT_DATA) {
> -			if (ddr)
> -				ext_csd_bit = EXT_CSD_DDR_BUS_WIDTH_8;
> -			else
> -				ext_csd_bit = EXT_CSD_BUS_WIDTH_8;
> -			bus_width = MMC_BUS_WIDTH_8;
> -		} else {
> -			if (ddr)
> -				ext_csd_bit = EXT_CSD_DDR_BUS_WIDTH_4;
> -			else
> -				ext_csd_bit = EXT_CSD_BUS_WIDTH_4;
> -			bus_width = MMC_BUS_WIDTH_4;
> +		static unsigned ext_csd_bits[][2] = {
> +			{ EXT_CSD_BUS_WIDTH_8, 
> EXT_CSD_DDR_BUS_WIDTH_8 },
> +			{ EXT_CSD_BUS_WIDTH_4, 
> EXT_CSD_DDR_BUS_WIDTH_4 },
> +			{ EXT_CSD_BUS_WIDTH_1, EXT_CSD_BUS_WIDTH_1 },
> +		};
> +		static unsigned bus_widths[] = {
> +			MMC_BUS_WIDTH_8,
> +			MMC_BUS_WIDTH_4,
> +			MMC_BUS_WIDTH_1
> +		};
> +		unsigned idx, bus_width = 0;
> +
> +		if (host->caps & MMC_CAP_8_BIT_DATA)
> +			idx = 0;
> +		else
> +			idx = 1;
> +		for (; idx < ARRAY_SIZE(bus_widths); idx++) {
> +			bus_width = bus_widths[idx];
> +			if (bus_width == MMC_BUS_WIDTH_1)
> +				ddr = 0; /* no DDR for 1-bit width */
> +			err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
> +					 EXT_CSD_BUS_WIDTH,
> +					 ext_csd_bits[idx][0]);
> +			if (!err) {
> +				/*
> +				 * If controller can't handle 
> bus width test,
> +				 * use the highest bus width to maintain
> +				 * compatibility with previous 
> MMC behavior.
> +				 */
> +				if (!(host->caps & 
> MMC_CAP_BUS_WIDTH_TEST))
> +					break;
> +				mmc_set_bus_width_ddr(card->host,
> +						      
> bus_width, MMC_SDR_MODE);
> +				err = mmc_bus_test(card, bus_width);
> +				if (!err)
> +					break;
> +			}
>  		}
>  
> -		err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
> -				 EXT_CSD_BUS_WIDTH, ext_csd_bit);
> -
> -		if (err && err != -EBADMSG)
> -			goto free_card;
> -
> +		if (!err && ddr) {
> +			err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
> +					EXT_CSD_BUS_WIDTH,
> +					ext_csd_bits[idx][1]);
> +		}
>  		if (err) {
>  			printk(KERN_WARNING "%s: switch to bus 
> width %d ddr %d "
> -			       "failed\n", mmc_hostname(card->host),
> -			       1 << bus_width, ddr);
> -			err = 0;
> -		} else {
> -			if (ddr)
> -				mmc_card_set_ddr_mode(card);
> -			else
> -				ddr = MMC_SDR_MODE;
> -
> +				"failed\n", mmc_hostname(card->host),
> +				1 << bus_width, ddr);
> +			goto free_card;
> +		} else if (ddr) {
> +			mmc_card_set_ddr_mode(card);
>  			mmc_set_bus_width_ddr(card->host, 
> bus_width, ddr);
>  		}
>  	}
> diff --git a/drivers/mmc/core/mmc_ops.c 
> b/drivers/mmc/core/mmc_ops.c index 326447c..60842f8 100644
> --- a/drivers/mmc/core/mmc_ops.c
> +++ b/drivers/mmc/core/mmc_ops.c
> @@ -462,3 +462,104 @@ int mmc_send_status(struct mmc_card 
> *card, u32 *status)
>  	return 0;
>  }
>  
> +static int
> +mmc_send_bus_test(struct mmc_card *card, struct mmc_host 
> *host, u8 opcode,
> +		  u8 len)
> +{
> +	struct mmc_request mrq;
> +	struct mmc_command cmd;
> +	struct mmc_data data;
> +	struct scatterlist sg;
> +	u8 *data_buf;
> +	u8 *test_buf;
> +	int i, err;
> +	static u8 testdata_8bit[8] = { 0x55, 0xaa, 0, 0, 0, 0, 0, 0 };
> +	static u8 testdata_4bit[4] = { 0x5a, 0, 0, 0 };
> +
> +	/* dma onto stack is unsafe/nonportable, but callers to this
> +	 * routine normally provide temporary on-stack buffers ...
> +	 */
> +	data_buf = kmalloc(len, GFP_KERNEL);
> +	if (!data_buf)
> +		return -ENOMEM;
> +
> +	if (len == 8)
> +		test_buf = testdata_8bit;
> +	else if (len == 4)
> +		test_buf = testdata_4bit;
> +	else {
> +		printk(KERN_ERR "%s: Invalid bus_width %d\n",
> +		       mmc_hostname(host), len);
> +		kfree(data_buf);
> +		return -EINVAL;
> +	}
> +
> +	if (opcode == MMC_BUS_TEST_W)
> +		memcpy(data_buf, test_buf, len);
> +
> +	memset(&mrq, 0, sizeof(struct mmc_request));
> +	memset(&cmd, 0, sizeof(struct mmc_command));
> +	memset(&data, 0, sizeof(struct mmc_data));
> +
> +	mrq.cmd = &cmd;
> +	mrq.data = &data;
> +	cmd.opcode = opcode;
> +	cmd.arg = 0;
> +
> +	/* NOTE HACK:  the MMC_RSP_SPI_R1 is always correct here, but we
> +	 * rely on callers to never use this with "native" 
> calls for reading
> +	 * CSD or CID.  Native versions of those commands use 
> the R2 type,
> +	 * not R1 plus a data block.
> +	 */
> +	cmd.flags = MMC_RSP_SPI_R1 | MMC_RSP_R1 | MMC_CMD_ADTC;
> +
> +	data.blksz = len;
> +	data.blocks = 1;
> +	if (opcode == MMC_BUS_TEST_R)
> +		data.flags = MMC_DATA_READ;
> +	else
> +		data.flags = MMC_DATA_WRITE;
> +
> +	data.sg = &sg;
> +	data.sg_len = 1;
> +	sg_init_one(&sg, data_buf, len);
> +	mmc_wait_for_req(host, &mrq);
> +	err = 0;
> +	if (opcode == MMC_BUS_TEST_R) {
> +		for (i = 0; i < len / 4; i++)
> +			if ((test_buf[i] ^ data_buf[i]) != 0xff) {
> +				err = -EIO;
> +				break;
> +			}
> +	}
> +	kfree(data_buf);
> +
> +	if (cmd.error)
> +		return cmd.error;
> +	if (data.error)
> +		return data.error;
> +
> +	return err;
> +}
> +
> +int mmc_bus_test(struct mmc_card *card, u8 bus_width) {
> +	int err, width;
> +
> +	if (bus_width == MMC_BUS_WIDTH_8)
> +		width = 8;
> +	else if (bus_width == MMC_BUS_WIDTH_4)
> +		width = 4;
> +	else if (bus_width == MMC_BUS_WIDTH_1)
> +		return 0; /* no need for test */
> +	else
> +		return -EINVAL;
> +
> +	/*
> +	 * Ignore errors from BUS_TEST_W.  BUS_TEST_R will fail if there
> +	 * is a problem.  This improves chances that the test will work.
> +	 */
> +	mmc_send_bus_test(card, card->host, MMC_BUS_TEST_W, width);
> +	err = mmc_send_bus_test(card, card->host, 
> MMC_BUS_TEST_R, width);
> +	return err;
> +}
> diff --git a/drivers/mmc/core/mmc_ops.h 
> b/drivers/mmc/core/mmc_ops.h index 653eb8e..e6d44b8 100644
> --- a/drivers/mmc/core/mmc_ops.h
> +++ b/drivers/mmc/core/mmc_ops.h
> @@ -26,6 +26,7 @@ int mmc_send_cid(struct mmc_host *host, u32 
> *cid);  int mmc_spi_read_ocr(struct mmc_host *host, int 
> highcap, u32 *ocrp);  int mmc_spi_set_crc(struct mmc_host 
> *host, int use_crc);  int mmc_card_sleepawake(struct mmc_host 
> *host, int sleep);
> +int mmc_bus_test(struct mmc_card *card, u8 bus_width);
>  
>  #endif
>  
> diff --git a/drivers/mmc/host/sdhci.c 
> b/drivers/mmc/host/sdhci.c index 5569886..d5febe5 100644
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
> @@ -23,6 +23,7 @@
>  
>  #include <linux/leds.h>
>  
> +#include <linux/mmc/mmc.h>
>  #include <linux/mmc/host.h>
>  
>  #include "sdhci.h"
> @@ -1521,7 +1522,11 @@ static void sdhci_data_irq(struct 
> sdhci_host *host, u32 intmask)
>  
>  	if (intmask & SDHCI_INT_DATA_TIMEOUT)
>  		host->data->error = -ETIMEDOUT;
> -	else if (intmask & (SDHCI_INT_DATA_CRC | 
> SDHCI_INT_DATA_END_BIT))
> +	else if (intmask & SDHCI_INT_DATA_END_BIT)
> +		host->data->error = -EILSEQ;
> +	else if ((intmask & SDHCI_INT_DATA_CRC) &&
> +		SDHCI_GET_CMD(sdhci_readw(host, SDHCI_COMMAND))
> +			!= MMC_BUS_TEST_R)
>  		host->data->error = -EILSEQ;
>  	else if (intmask & SDHCI_INT_ADMA_ERROR) {
>  		printk(KERN_ERR "%s: ADMA error\n", 
> mmc_hostname(host->mmc)); diff --git 
> a/drivers/mmc/host/sdhci.h b/drivers/mmc/host/sdhci.h index 
> 1efe7dc..6e0969e 100644
> --- a/drivers/mmc/host/sdhci.h
> +++ b/drivers/mmc/host/sdhci.h
> @@ -52,6 +52,7 @@
>  #define  SDHCI_CMD_RESP_SHORT_BUSY 0x03
>  
>  #define SDHCI_MAKE_CMD(c, f) (((c & 0xff) << 8) | (f & 0xff))
> +#define SDHCI_GET_CMD(c) ((c>>8) & 0x3f)
>  
>  #define SDHCI_RESPONSE		0x10
>  
> diff --git a/include/linux/mmc/host.h 
> b/include/linux/mmc/host.h index 3a85e73..bcb793e 100644
> --- a/include/linux/mmc/host.h
> +++ b/include/linux/mmc/host.h
> @@ -172,6 +172,7 @@ struct mmc_host {
>  #define MMC_CAP_1_2V_DDR	(1 << 12)	/* can support */
>  						/* DDR mode at 1.2V */
>  #define MMC_CAP_POWER_OFF_CARD	(1 << 13)	/* Can 
> power off after boot */
> +#define MMC_CAP_BUS_WIDTH_TEST	(1 << 14)	/* 
> CMD14/CMD19 bus width ok */
>  
>  	mmc_pm_flag_t		pm_caps;	/* supported pm 
> features */
>  
> diff --git a/include/linux/mmc/mmc.h 
> b/include/linux/mmc/mmc.h index 956fbd87..612301f 100644
> --- a/include/linux/mmc/mmc.h
> +++ b/include/linux/mmc/mmc.h
> @@ -40,7 +40,9 @@
>  #define MMC_READ_DAT_UNTIL_STOP  11   /* adtc [31:0] dadr    
>     R1  */
>  #define MMC_STOP_TRANSMISSION    12   /* ac                  
>     R1b */
>  #define MMC_SEND_STATUS          13   /* ac   [31:16] RCA    
>     R1  */
> +#define MMC_BUS_TEST_R           14   /* adtc                
>     R1  */
>  #define MMC_GO_INACTIVE_STATE    15   /* ac   [31:16] RCA    
>         */
> +#define MMC_BUS_TEST_W           19   /* adtc                
>     R1  */
>  #define MMC_SPI_READ_OCR         58   /* spi                 
>  spi_R3 */
>  #define MMC_SPI_CRC_ON_OFF       59   /* spi  [0:0] flag     
>  spi_R1 */
>  
> --
> 1.7.3.5
> 
> 
> 
> From 08c82dfad2458f8f9b83126224a85e7ea9e2b046 Mon Sep 17 00:00:00 2001
> From: Takashi Iwai <tiwai@suse.de>
> Date: Wed, 22 Dec 2010 09:59:44 +0100
> Subject: [PATCH] mmc: fix mmc_set_bus_width_ddr() call 
> without bus-width-test cap
> 
> With the bus-width test patch, mmc_set_bus_width*() isn't 
> called properly
> when the driver doesn't set MMC_CAP_BUS_WIDTH and no DDR mode.
> This patch fixes the regression by moving the call up before 
> the cap test.
> 
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> Reviewed-by: Chris Ball <cjb@laptop.org>
> Signed-off-by: Chris Ball <cjb@laptop.org>
> ---
>  drivers/mmc/core/mmc.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/mmc/core/mmc.c b/drivers/mmc/core/mmc.c
> index 1d8409f..c86dd73 100644
> --- a/drivers/mmc/core/mmc.c
> +++ b/drivers/mmc/core/mmc.c
> @@ -558,6 +558,8 @@ static int mmc_init_card(struct mmc_host 
> *host, u32 ocr,
>  					 EXT_CSD_BUS_WIDTH,
>  					 ext_csd_bits[idx][0]);
>  			if (!err) {
> +				mmc_set_bus_width_ddr(card->host,
> +						      
> bus_width, MMC_SDR_MODE);
>  				/*
>  				 * If controller can't handle 
> bus width test,
>  				 * use the highest bus width to maintain
> @@ -565,8 +567,6 @@ static int mmc_init_card(struct mmc_host 
> *host, u32 ocr,
>  				 */
>  				if (!(host->caps & 
> MMC_CAP_BUS_WIDTH_TEST))
>  					break;
> -				mmc_set_bus_width_ddr(card->host,
> -						      
> bus_width, MMC_SDR_MODE);
>  				err = mmc_bus_test(card, bus_width);
>  				if (!err)
>  					break;
> -- 
> 1.7.3.5
> 
> 
> 
> On Jan 18, 2011, at 4:36 PM, Tomoya MORINAGA wrote:
> 
> > Hi Philip,
> >  
> > On Wednesday, December 01, 2010 10:31 AM, Philip Rakity wrote:
> > > Thanks very much, I'll plan on sending this to Linus 
> tomorrow, along
> > > with the rest of my .37 queue, unless there are any more review
> > > comments from anyone.
> >  
> > We tried to use the MMC card like the following on kernel-2.6.37.
> >  
> > On Tuesday, November 09, 2010 2:40 PM, Tomoya MORINAGA wrote:
> > > I am facing the issue about some MMC cards on Intel EG20T PCH 
> > > (Platform Controller Hub).
> > > The linux version is 2.6.36.
> > > I can not transfer data the MMC cards (e.g. Transcned MMC card).
> > > The card is 1 bit bus width. And the card is according to MMC 
> > > specification V3.x.
> > > And the EG20T has a 4 bit bus width capability Linux MMC 
> > > standard driver decides the card bus width as 4 bit, if the 
> > > MMC specification version is larger than or equal to V4.0 
> like below.
> >  
> > However it seems the issue remains to be seen.
> > Have you fixed the MMC unrecognized issue in kernel-2.6.37?
> >  
> > Thanks,
> > -----------------------------------------
> > Tomoya MORINAGA
> > OKI SEMICONDUCTOR CO., LTD.
> 

[-- Attachment #2: mmc_log --]
[-- Type: application/octet-stream, Size: 125810 bytes --]

 error -84 transferring data, sector 3940338, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940338
mmcblk0: error -84 transferring data, sector 3940339, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940339
mmcblk0: error -84 transferring data, sector 3940340, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940340
mmcblk0: error -84 transferring data, sector 3940341, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940341
mmcblk0: error -84 transferring data, sector 3940342, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940342
mmcblk0: error -84 transferring data, sector 3940343, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940343
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 8, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 8
mmcblk0: error -84 transferring data, sector 9, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 9
mmcblk0: error -84 transferring data, sector 10, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 10
mmcblk0: error -84 transferring data, sector 11, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 11
mmcblk0: error -84 transferring data, sector 12, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 12
mmcblk0: error -84 transferring data, sector 13, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 13
mmcblk0: error -84 transferring data, sector 14, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 14
mmcblk0: error -84 transferring data, sector 15, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 15
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 3940344, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940344
mmcblk0: error -84 transferring data, sector 3940345, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940345
mmcblk0: error -84 transferring data, sector 3940346, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940346
mmcblk0: error -84 transferring data, sector 3940347, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940347
mmcblk0: error -84 transferring data, sector 3940348, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940348
mmcblk0: error -84 transferring data, sector 3940349, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940349
mmcblk0: error -84 transferring data, sector 3940350, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940350
mmcblk0: error -84 transferring data, sector 3940351, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940351
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 3940344, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940344
mmcblk0: error -84 transferring data, sector 3940345, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940345
mmcblk0: error -84 transferring data, sector 3940346, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940346
mmcblk0: error -84 transferring data, sector 3940347, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940347
mmcblk0: error -84 transferring data, sector 3940348, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940348
mmcblk0: error -84 transferring data, sector 3940349, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940349
mmcblk0: error -84 transferring data, sector 3940350, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940350
mmcblk0: error -84 transferring data, sector 3940351, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940351
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 3940344, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940344
mmcblk0: error -84 transferring data, sector 3940345, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940345
mmcblk0: error -84 transferring data, sector 3940346, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940346
mmcblk0: error -84 transferring data, sector 3940347, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940347
mmcblk0: error -84 transferring data, sector 3940348, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940348
mmcblk0: error -84 transferring data, sector 3940349, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940349
mmcblk0: error -84 transferring data, sector 3940350, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940350
mmcblk0: error -84 transferring data, sector 3940351, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940351
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 3940344, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940344
mmcblk0: error -84 transferring data, sector 3940345, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940345
mmcblk0: error -84 transferring data, sector 3940346, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940346
mmcblk0: error -84 transferring data, sector 3940347, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940347
mmcblk0: error -84 transferring data, sector 3940348, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940348
mmcblk0: error -84 transferring data, sector 3940349, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940349
mmcblk0: error -84 transferring data, sector 3940350, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940350
mmcblk0: error -84 transferring data, sector 3940351, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940351
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 3940344, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940344
mmcblk0: error -84 transferring data, sector 3940345, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940345
mmcblk0: error -84 transferring data, sector 3940346, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940346
mmcblk0: error -84 transferring data, sector 3940347, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940347
mmcblk0: error -84 transferring data, sector 3940348, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940348
mmcblk0: error -84 transferring data, sector 3940349, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940349
mmcblk0: error -84 transferring data, sector 3940350, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940350
mmcblk0: error -84 transferring data, sector 3940351, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940351
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 3940344, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940344
mmcblk0: error -84 transferring data, sector 3940345, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940345
mmcblk0: error -84 transferring data, sector 3940346, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940346
mmcblk0: error -84 transferring data, sector 3940347, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940347
mmcblk0: error -84 transferring data, sector 3940348, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940348
mmcblk0: error -84 transferring data, sector 3940349, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940349
mmcblk0: error -84 transferring data, sector 3940350, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940350
mmcblk0: error -84 transferring data, sector 3940351, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940351
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 3940288, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940288
mmcblk0: error -84 transferring data, sector 3940289, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940289
mmcblk0: error -84 transferring data, sector 3940290, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940290
mmcblk0: error -84 transferring data, sector 3940291, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940291
mmcblk0: error -84 transferring data, sector 3940292, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940292
mmcblk0: error -84 transferring data, sector 3940293, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940293
mmcblk0: error -84 transferring data, sector 3940294, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940294
mmcblk0: error -84 transferring data, sector 3940295, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940295
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 3940336, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940336
mmcblk0: error -84 transferring data, sector 3940337, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940337
mmcblk0: error -84 transferring data, sector 3940338, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940338
mmcblk0: error -84 transferring data, sector 3940339, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940339
mmcblk0: error -84 transferring data, sector 3940340, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940340
mmcblk0: error -84 transferring data, sector 3940341, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940341
mmcblk0: error -84 transferring data, sector 3940342, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940342
mmcblk0: error -84 transferring data, sector 3940343, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940343
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 8, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 8
mmcblk0: error -84 transferring data, sector 9, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 9
mmcblk0: error -84 transferring data, sector 10, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 10
mmcblk0: error -84 transferring data, sector 11, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 11
mmcblk0: error -84 transferring data, sector 12, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 12
mmcblk0: error -84 transferring data, sector 13, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 13
mmcblk0: error -84 transferring data, sector 14, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 14
mmcblk0: error -84 transferring data, sector 15, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 15
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 8, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 8
mmcblk0: error -84 transferring data, sector 9, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 9
mmcblk0: error -84 transferring data, sector 10, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 10
mmcblk0: error -84 transferring data, sector 11, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 11
mmcblk0: error -84 transferring data, sector 12, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 12
mmcblk0: error -84 transferring data, sector 13, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 13
mmcblk0: error -84 transferring data, sector 14, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 14
mmcblk0: error -84 transferring data, sector 15, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 15
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 3940344, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940344
mmcblk0: error -84 transferring data, sector 3940345, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940345
mmcblk0: error -84 transferring data, sector 3940346, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940346
mmcblk0: error -84 transferring data, sector 3940347, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940347
mmcblk0: error -84 transferring data, sector 3940348, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940348
mmcblk0: error -84 transferring data, sector 3940349, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940349
mmcblk0: error -84 transferring data, sector 3940350, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940350
mmcblk0: error -84 transferring data, sector 3940351, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940351
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 3940344, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940344
mmcblk0: error -84 transferring data, sector 3940345, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940345
mmcblk0: error -84 transferring data, sector 3940346, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940346
mmcblk0: error -84 transferring data, sector 3940347, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940347
mmcblk0: error -84 transferring data, sector 3940348, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940348
mmcblk0: error -84 transferring data, sector 3940349, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940349
mmcblk0: error -84 transferring data, sector 3940350, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940350
mmcblk0: error -84 transferring data, sector 3940351, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940351
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 3940344, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940344
mmcblk0: error -84 transferring data, sector 3940345, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940345
mmcblk0: error -84 transferring data, sector 3940346, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940346
mmcblk0: error -84 transferring data, sector 3940347, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940347
mmcblk0: error -84 transferring data, sector 3940348, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940348
mmcblk0: error -84 transferring data, sector 3940349, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940349
mmcblk0: error -84 transferring data, sector 3940350, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940350
mmcblk0: error -84 transferring data, sector 3940351, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3940351
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 2048, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2048
mmcblk0: error -84 transferring data, sector 2049, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2049
mmcblk0: error -84 transferring data, sector 2050, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2050
mmcblk0: error -84 transferring data, sector 2051, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2051
mmcblk0: error -84 transferring data, sector 2052, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2052
mmcblk0: error -84 transferring data, sector 2053, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2053
mmcblk0: error -84 transferring data, sector 2054, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2054
mmcblk0: error -84 transferring data, sector 2055, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2055
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 8, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 8
mmcblk0: error -84 transferring data, sector 9, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 9
mmcblk0: error -84 transferring data, sector 10, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 10
mmcblk0: error -84 transferring data, sector 11, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 11
mmcblk0: error -84 transferring data, sector 12, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 12
mmcblk0: error -84 transferring data, sector 13, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 13
mmcblk0: error -84 transferring data, sector 14, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 14
mmcblk0: error -84 transferring data, sector 15, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 15
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 8, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 8
mmcblk0: error -84 transferring data, sector 9, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 9
mmcblk0: error -84 transferring data, sector 10, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 10
mmcblk0: error -84 transferring data, sector 11, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 11
mmcblk0: error -84 transferring data, sector 12, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 12
mmcblk0: error -84 transferring data, sector 13, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 13
mmcblk0: error -84 transferring data, sector 14, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 14
mmcblk0: error -84 transferring data, sector 15, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 15
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 8, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 8
mmcblk0: error -84 transferring data, sector 9, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 9
mmcblk0: error -84 transferring data, sector 10, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 10
mmcblk0: error -84 transferring data, sector 11, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 11
mmcblk0: error -84 transferring data, sector 12, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 12
mmcblk0: error -84 transferring data, sector 13, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 13
mmcblk0: error -84 transferring data, sector 14, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 14
mmcblk0: error -84 transferring data, sector 15, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 15
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 24, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 24
mmcblk0: error -84 transferring data, sector 25, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 25
mmcblk0: error -84 transferring data, sector 26, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 26
mmcblk0: error -84 transferring data, sector 27, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 27
mmcblk0: error -84 transferring data, sector 28, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 28
mmcblk0: error -84 transferring data, sector 29, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 29
mmcblk0: error -84 transferring data, sector 30, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 30
mmcblk0: error -84 transferring data, sector 31, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 31
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 24, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 24
mmcblk0: error -84 transferring data, sector 25, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 25
mmcblk0: error -84 transferring data, sector 26, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 26
mmcblk0: error -84 transferring data, sector 27, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 27
mmcblk0: error -84 transferring data, sector 28, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 28
mmcblk0: error -84 transferring data, sector 29, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 29
mmcblk0: error -84 transferring data, sector 30, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 30
mmcblk0: error -84 transferring data, sector 31, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 31
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 24, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 24
mmcblk0: error -84 transferring data, sector 25, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 25
mmcblk0: error -84 transferring data, sector 26, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 26
mmcblk0: error -84 transferring data, sector 27, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 27
mmcblk0: error -84 transferring data, sector 28, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 28
mmcblk0: error -84 transferring data, sector 29, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 29
mmcblk0: error -84 transferring data, sector 30, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 30
mmcblk0: error -84 transferring data, sector 31, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 31
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 56, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 56
mmcblk0: error -84 transferring data, sector 57, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 57
mmcblk0: error -84 transferring data, sector 58, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 58
mmcblk0: error -84 transferring data, sector 59, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 59
mmcblk0: error -84 transferring data, sector 60, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 60
mmcblk0: error -84 transferring data, sector 61, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 61
mmcblk0: error -84 transferring data, sector 62, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 62
mmcblk0: error -84 transferring data, sector 63, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 63
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 56, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 56
mmcblk0: error -84 transferring data, sector 57, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 57
mmcblk0: error -84 transferring data, sector 58, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 58
mmcblk0: error -84 transferring data, sector 59, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 59
mmcblk0: error -84 transferring data, sector 60, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 60
mmcblk0: error -84 transferring data, sector 61, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 61
mmcblk0: error -84 transferring data, sector 62, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 62
mmcblk0: error -84 transferring data, sector 63, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 63
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 56, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 56
mmcblk0: error -84 transferring data, sector 57, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 57
mmcblk0: error -84 transferring data, sector 58, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 58
mmcblk0: error -84 transferring data, sector 59, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 59
mmcblk0: error -84 transferring data, sector 60, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 60
mmcblk0: error -84 transferring data, sector 61, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 61
mmcblk0: error -84 transferring data, sector 62, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 62
mmcblk0: error -84 transferring data, sector 63, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 63
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 120, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 120
mmcblk0: error -84 transferring data, sector 121, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 121
mmcblk0: error -84 transferring data, sector 122, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 122
mmcblk0: error -84 transferring data, sector 123, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 123
mmcblk0: error -84 transferring data, sector 124, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 124
mmcblk0: error -84 transferring data, sector 125, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 125
mmcblk0: error -84 transferring data, sector 126, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 126
mmcblk0: error -84 transferring data, sector 127, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 127
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 120, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 120
mmcblk0: error -84 transferring data, sector 121, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 121
mmcblk0: error -84 transferring data, sector 122, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 122
mmcblk0: error -84 transferring data, sector 123, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 123
mmcblk0: error -84 transferring data, sector 124, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 124
mmcblk0: error -84 transferring data, sector 125, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 125
mmcblk0: error -84 transferring data, sector 126, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 126
mmcblk0: error -84 transferring data, sector 127, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 127
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 120, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 120
mmcblk0: error -84 transferring data, sector 121, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 121
mmcblk0: error -84 transferring data, sector 122, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 122
mmcblk0: error -84 transferring data, sector 123, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 123
mmcblk0: error -84 transferring data, sector 124, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 124
mmcblk0: error -84 transferring data, sector 125, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 125
mmcblk0: error -84 transferring data, sector 126, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 126
mmcblk0: error -84 transferring data, sector 127, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 127
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 8, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 8
mmcblk0: error -84 transferring data, sector 9, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 9
mmcblk0: error -84 transferring data, sector 10, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 10
mmcblk0: error -84 transferring data, sector 11, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 11
mmcblk0: error -84 transferring data, sector 12, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 12
mmcblk0: error -84 transferring data, sector 13, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 13
mmcblk0: error -84 transferring data, sector 14, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 14
mmcblk0: error -84 transferring data, sector 15, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 15
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 8, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 8
mmcblk0: error -84 transferring data, sector 9, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 9
mmcblk0: error -84 transferring data, sector 10, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 10
mmcblk0: error -84 transferring data, sector 11, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 11
mmcblk0: error -84 transferring data, sector 12, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 12
mmcblk0: error -84 transferring data, sector 13, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 13
mmcblk0: error -84 transferring data, sector 14, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 14
mmcblk0: error -84 transferring data, sector 15, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 15
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 24, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 24
mmcblk0: error -84 transferring data, sector 25, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 25
mmcblk0: error -84 transferring data, sector 26, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 26
mmcblk0: error -84 transferring data, sector 27, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 27
mmcblk0: error -84 transferring data, sector 28, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 28
mmcblk0: error -84 transferring data, sector 29, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 29
mmcblk0: error -84 transferring data, sector 30, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 30
mmcblk0: error -84 transferring data, sector 31, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 31
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 24, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 24
mmcblk0: error -84 transferring data, sector 25, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 25
mmcblk0: error -84 transferring data, sector 26, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 26
mmcblk0: error -84 transferring data, sector 27, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 27
mmcblk0: error -84 transferring data, sector 28, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 28
mmcblk0: error -84 transferring data, sector 29, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 29
mmcblk0: error -84 transferring data, sector 30, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 30
mmcblk0: error -84 transferring data, sector 31, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 31
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 56, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 56
mmcblk0: error -84 transferring data, sector 57, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 57
mmcblk0: error -84 transferring data, sector 58, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 58
mmcblk0: error -84 transferring data, sector 59, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 59
mmcblk0: error -84 transferring data, sector 60, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 60
mmcblk0: error -84 transferring data, sector 61, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 61
mmcblk0: error -84 transferring data, sector 62, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 62
mmcblk0: error -84 transferring data, sector 63, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 63
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 56, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 56
mmcblk0: error -84 transferring data, sector 57, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 57
mmcblk0: error -84 transferring data, sector 58, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 58
mmcblk0: error -84 transferring data, sector 59, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 59
mmcblk0: error -84 transferring data, sector 60, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 60
mmcblk0: error -84 transferring data, sector 61, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 61
mmcblk0: error -84 transferring data, sector 62, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 62
mmcblk0: error -84 transferring data, sector 63, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 63
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 120, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 120
mmcblk0: error -84 transferring data, sector 121, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 121
mmcblk0: error -84 transferring data, sector 122, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 122
mmcblk0: error -84 transferring data, sector 123, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 123
mmcblk0: error -84 transferring data, sector 124, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 124
mmcblk0: error -84 transferring data, sector 125, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 125
mmcblk0: error -84 transferring data, sector 126, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 126
mmcblk0: error -84 transferring data, sector 127, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 127
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 120, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 120
mmcblk0: error -84 transferring data, sector 121, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 121
mmcblk0: error -84 transferring data, sector 122, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 122
mmcblk0: error -84 transferring data, sector 123, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 123
mmcblk0: error -84 transferring data, sector 124, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 124
mmcblk0: error -84 transferring data, sector 125, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 125
mmcblk0: error -84 transferring data, sector 126, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 126
mmcblk0: error -84 transferring data, sector 127, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 127
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
quiet_error: 204 callbacks suppressed
Buffer I/O error on device mmcblk0, logical block 0
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
Buffer I/O error on device mmcblk0, logical block 0
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
Buffer I/O error on device mmcblk0, logical block 0
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
Buffer I/O error on device mmcblk0, logical block 0
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
Buffer I/O error on device mmcblk0, logical block 0
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
Buffer I/O error on device mmcblk0, logical block 0
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 16, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 16
mmcblk0: error -84 transferring data, sector 17, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 17
mmcblk0: error -84 transferring data, sector 18, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 18
mmcblk0: error -84 transferring data, sector 19, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 19
mmcblk0: error -84 transferring data, sector 20, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 20
mmcblk0: error -84 transferring data, sector 21, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 21
mmcblk0: error -84 transferring data, sector 22, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 22
mmcblk0: error -84 transferring data, sector 23, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 23
Buffer I/O error on device mmcblk0, logical block 2
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 128, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 128
mmcblk0: error -84 transferring data, sector 129, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 129
mmcblk0: error -84 transferring data, sector 130, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 130
mmcblk0: error -84 transferring data, sector 131, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 131
mmcblk0: error -84 transferring data, sector 132, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 132
mmcblk0: error -84 transferring data, sector 133, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 133
mmcblk0: error -84 transferring data, sector 134, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 134
mmcblk0: error -84 transferring data, sector 135, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 135
Buffer I/O error on device mmcblk0, logical block 16
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 128, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 128
mmcblk0: error -84 transferring data, sector 129, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 129
mmcblk0: error -84 transferring data, sector 130, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 130
mmcblk0: error -84 transferring data, sector 131, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 131
mmcblk0: error -84 transferring data, sector 132, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 132
mmcblk0: error -84 transferring data, sector 133, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 133
mmcblk0: error -84 transferring data, sector 134, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 134
mmcblk0: error -84 transferring data, sector 135, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 135
Buffer I/O error on device mmcblk0, logical block 16
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 128, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 128
mmcblk0: error -84 transferring data, sector 129, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 129
mmcblk0: error -84 transferring data, sector 130, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 130
mmcblk0: error -84 transferring data, sector 131, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 131
mmcblk0: error -84 transferring data, sector 132, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 132
mmcblk0: error -84 transferring data, sector 133, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 133
mmcblk0: error -84 transferring data, sector 134, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 134
mmcblk0: error -84 transferring data, sector 135, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 135
Buffer I/O error on device mmcblk0, logical block 16
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 16, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 16
mmcblk0: error -84 transferring data, sector 17, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 17
mmcblk0: error -84 transferring data, sector 18, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 18
mmcblk0: error -84 transferring data, sector 19, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 19
mmcblk0: error -84 transferring data, sector 20, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 20
mmcblk0: error -84 transferring data, sector 21, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 21
mmcblk0: error -84 transferring data, sector 22, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 22
mmcblk0: error -84 transferring data, sector 23, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 23
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 128, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 128
mmcblk0: error -84 transferring data, sector 129, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 129
mmcblk0: error -84 transferring data, sector 130, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 130
mmcblk0: error -84 transferring data, sector 131, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 131
mmcblk0: error -84 transferring data, sector 132, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 132
mmcblk0: error -84 transferring data, sector 133, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 133
mmcblk0: error -84 transferring data, sector 134, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 134
mmcblk0: error -84 transferring data, sector 135, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 135
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 64, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 64
mmcblk0: error -84 transferring data, sector 65, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 65
mmcblk0: error -84 transferring data, sector 66, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 66
mmcblk0: error -84 transferring data, sector 67, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 67
mmcblk0: error -84 transferring data, sector 68, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 68
mmcblk0: error -84 transferring data, sector 69, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 69
mmcblk0: error -84 transferring data, sector 70, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 70
mmcblk0: error -84 transferring data, sector 71, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 71
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 64, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 64
mmcblk0: error -84 transferring data, sector 65, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 65
mmcblk0: error -84 transferring data, sector 66, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 66
mmcblk0: error -84 transferring data, sector 67, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 67
mmcblk0: error -84 transferring data, sector 68, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 68
mmcblk0: error -84 transferring data, sector 69, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 69
mmcblk0: error -84 transferring data, sector 70, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 70
mmcblk0: error -84 transferring data, sector 71, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 71
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 64, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 64
mmcblk0: error -84 transferring data, sector 65, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 65
mmcblk0: error -84 transferring data, sector 66, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 66
mmcblk0: error -84 transferring data, sector 67, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 67
mmcblk0: error -84 transferring data, sector 68, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 68
mmcblk0: error -84 transferring data, sector 69, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 69
mmcblk0: error -84 transferring data, sector 70, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 70
mmcblk0: error -84 transferring data, sector 71, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 71
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 64, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 64
mmcblk0: error -84 transferring data, sector 65, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 65
mmcblk0: error -84 transferring data, sector 66, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 66
mmcblk0: error -84 transferring data, sector 67, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 67
mmcblk0: error -84 transferring data, sector 68, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 68
mmcblk0: error -84 transferring data, sector 69, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 69
mmcblk0: error -84 transferring data, sector 70, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 70
mmcblk0: error -84 transferring data, sector 71, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 71
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 64, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 64
mmcblk0: error -84 transferring data, sector 65, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 65
mmcblk0: error -84 transferring data, sector 66, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 66
mmcblk0: error -84 transferring data, sector 67, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 67
mmcblk0: error -84 transferring data, sector 68, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 68
mmcblk0: error -84 transferring data, sector 69, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 69
mmcblk0: error -84 transferring data, sector 70, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 70
mmcblk0: error -84 transferring data, sector 71, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 71
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 64, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 64
mmcblk0: error -84 transferring data, sector 65, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 65
mmcblk0: error -84 transferring data, sector 66, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 66
mmcblk0: error -84 transferring data, sector 67, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 67
mmcblk0: error -84 transferring data, sector 68, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 68
mmcblk0: error -84 transferring data, sector 69, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 69
mmcblk0: error -84 transferring data, sector 70, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 70
mmcblk0: error -84 transferring data, sector 71, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 71
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 64, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 64
mmcblk0: error -84 transferring data, sector 65, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 65
mmcblk0: error -84 transferring data, sector 66, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 66
mmcblk0: error -84 transferring data, sector 67, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 67
mmcblk0: error -84 transferring data, sector 68, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 68
mmcblk0: error -84 transferring data, sector 69, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 69
mmcblk0: error -84 transferring data, sector 70, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 70
mmcblk0: error -84 transferring data, sector 71, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 71
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 64, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 64
mmcblk0: error -84 transferring data, sector 65, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 65
mmcblk0: error -84 transferring data, sector 66, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 66
mmcblk0: error -84 transferring data, sector 67, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 67
mmcblk0: error -84 transferring data, sector 68, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 68
mmcblk0: error -84 transferring data, sector 69, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 69
mmcblk0: error -84 transferring data, sector 70, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 70
mmcblk0: error -84 transferring data, sector 71, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 71
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 64, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 64
mmcblk0: error -84 transferring data, sector 65, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 65
mmcblk0: error -84 transferring data, sector 66, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 66
mmcblk0: error -84 transferring data, sector 67, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 67
mmcblk0: error -84 transferring data, sector 68, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 68
mmcblk0: error -84 transferring data, sector 69, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 69
mmcblk0: error -84 transferring data, sector 70, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 70
mmcblk0: error -84 transferring data, sector 71, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 71
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 64, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 64
mmcblk0: error -84 transferring data, sector 65, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 65
mmcblk0: error -84 transferring data, sector 66, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 66
mmcblk0: error -84 transferring data, sector 67, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 67
mmcblk0: error -84 transferring data, sector 68, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 68
mmcblk0: error -84 transferring data, sector 69, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 69
mmcblk0: error -84 transferring data, sector 70, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 70
mmcblk0: error -84 transferring data, sector 71, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 71
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 256, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 256
mmcblk0: error -84 transferring data, sector 257, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 257
mmcblk0: error -84 transferring data, sector 258, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 258
mmcblk0: error -84 transferring data, sector 259, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 259
mmcblk0: error -84 transferring data, sector 260, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 260
mmcblk0: error -84 transferring data, sector 261, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 261
mmcblk0: error -84 transferring data, sector 262, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 262
mmcblk0: error -84 transferring data, sector 263, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 263
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 16, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 16
mmcblk0: error -84 transferring data, sector 17, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 17
mmcblk0: error -84 transferring data, sector 18, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 18
mmcblk0: error -84 transferring data, sector 19, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 19
mmcblk0: error -84 transferring data, sector 20, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 20
mmcblk0: error -84 transferring data, sector 21, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 21
mmcblk0: error -84 transferring data, sector 22, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 22
mmcblk0: error -84 transferring data, sector 23, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 23
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 128, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 128
mmcblk0: error -84 transferring data, sector 129, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 129
mmcblk0: error -84 transferring data, sector 130, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 130
mmcblk0: error -84 transferring data, sector 131, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 131
mmcblk0: error -84 transferring data, sector 132, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 132
mmcblk0: error -84 transferring data, sector 133, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 133
mmcblk0: error -84 transferring data, sector 134, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 134
mmcblk0: error -84 transferring data, sector 135, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 135
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 128, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 128
mmcblk0: error -84 transferring data, sector 129, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 129
mmcblk0: error -84 transferring data, sector 130, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 130
mmcblk0: error -84 transferring data, sector 131, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 131
mmcblk0: error -84 transferring data, sector 132, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 132
mmcblk0: error -84 transferring data, sector 133, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 133
mmcblk0: error -84 transferring data, sector 134, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 134
mmcblk0: error -84 transferring data, sector 135, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 135
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 16, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 16
mmcblk0: error -84 transferring data, sector 17, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 17
mmcblk0: error -84 transferring data, sector 18, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 18
mmcblk0: error -84 transferring data, sector 19, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 19
mmcblk0: error -84 transferring data, sector 20, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 20
mmcblk0: error -84 transferring data, sector 21, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 21
mmcblk0: error -84 transferring data, sector 22, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 22
mmcblk0: error -84 transferring data, sector 23, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 23
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 8, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 8
mmcblk0: error -84 transferring data, sector 9, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 9
mmcblk0: error -84 transferring data, sector 10, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 10
mmcblk0: error -84 transferring data, sector 11, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 11
mmcblk0: error -84 transferring data, sector 12, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 12
mmcblk0: error -84 transferring data, sector 13, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 13
mmcblk0: error -84 transferring data, sector 14, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 14
mmcblk0: error -84 transferring data, sector 15, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 15
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 16, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 16
mmcblk0: error -84 transferring data, sector 17, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 17
mmcblk0: error -84 transferring data, sector 18, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 18
mmcblk0: error -84 transferring data, sector 19, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 19
mmcblk0: error -84 transferring data, sector 20, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 20
mmcblk0: error -84 transferring data, sector 21, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 21
mmcblk0: error -84 transferring data, sector 22, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 22
mmcblk0: error -84 transferring data, sector 23, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 23
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 8, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 8
mmcblk0: error -84 transferring data, sector 9, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 9
mmcblk0: error -84 transferring data, sector 10, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 10
mmcblk0: error -84 transferring data, sector 11, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 11
mmcblk0: error -84 transferring data, sector 12, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 12
mmcblk0: error -84 transferring data, sector 13, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 13
mmcblk0: error -84 transferring data, sector 14, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 14
mmcblk0: error -84 transferring data, sector 15, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 15
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 128, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 128
mmcblk0: error -84 transferring data, sector 129, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 129
mmcblk0: error -84 transferring data, sector 130, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 130
mmcblk0: error -84 transferring data, sector 131, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 131
mmcblk0: error -84 transferring data, sector 132, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 132
mmcblk0: error -84 transferring data, sector 133, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 133
mmcblk0: error -84 transferring data, sector 134, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 134
mmcblk0: error -84 transferring data, sector 135, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 135
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 4096, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4096
mmcblk0: error -84 transferring data, sector 4097, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4097
mmcblk0: error -84 transferring data, sector 4098, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4098
mmcblk0: error -84 transferring data, sector 4099, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4099
mmcblk0: error -84 transferring data, sector 4100, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4100
mmcblk0: error -84 transferring data, sector 4101, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4101
mmcblk0: error -84 transferring data, sector 4102, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4102
mmcblk0: error -84 transferring data, sector 4103, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4103
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: A MMC card transfer issue
  2011-01-19  6:05           ` Philip Rakity
  2011-01-19  6:30             ` Tomoya MORINAGA
@ 2011-01-19 17:42             ` Chris Ball
  2011-01-19 23:49               ` Tomoya MORINAGA
  2011-01-26  8:28               ` Tomoya MORINAGA
  1 sibling, 2 replies; 26+ messages in thread
From: Chris Ball @ 2011-01-19 17:42 UTC (permalink / raw)
  To: Philip Rakity
  Cc: Tomoya MORINAGA, Kyungmin Park, linux-mmc@vger.kernel.org,
	linux-kernel@vger.kernel.org, andrew.chih.howe.khor@intel.com,
	kok.howg.ewe@intel.com

Hi,

On Tue, Jan 18, 2011 at 10:05:04PM -0800, Philip Rakity wrote:
> 
> For 1 bit transcend cards you need these 2 patches.
> 
> >From 22113efd00491310da802f3b1a9a66cfcf415fac Mon Sep 17 00:00:00 2001
> From: Aries Lee <arieslee@jmicron.com>
> Date: Wed, 15 Dec 2010 08:14:24 +0100
> Subject: [PATCH] mmc: Test bus-width for old MMC devices

Present in 2.6.38-rc1.

> >From 08c82dfad2458f8f9b83126224a85e7ea9e2b046 Mon Sep 17 00:00:00 2001
> From: Takashi Iwai <tiwai@suse.de>
> Date: Wed, 22 Dec 2010 09:59:44 +0100
> Subject: [PATCH] mmc: fix mmc_set_bus_width_ddr() call without bus-width-test cap

Also present in 2.6.38-rc1.

So, please re-test against 2.6.38-rc1 and let us know whether you still
have problems.  Thanks,

-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

^ permalink raw reply	[flat|nested] 26+ messages in thread

* RE: A MMC card transfer issue
  2011-01-19 17:42             ` Chris Ball
@ 2011-01-19 23:49               ` Tomoya MORINAGA
  2011-01-26  8:28               ` Tomoya MORINAGA
  1 sibling, 0 replies; 26+ messages in thread
From: Tomoya MORINAGA @ 2011-01-19 23:49 UTC (permalink / raw)
  To: 'Chris Ball', 'Philip Rakity'
  Cc: 'Kyungmin Park', linux-mmc, linux-kernel,
	andrew.chih.howe.khor, kok.howg.ewe, Toshiharu Okada

Hi Chris,

Thank you for your information.
We will test using 2.6.38-rc1 and report to you.
 
Thanks,
-----------------------------------------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.


> -----Original Message-----
> From: Chris Ball [mailto:cjb@laptop.org] 
> Sent: Thursday, January 20, 2011 2:43 AM
> To: Philip Rakity
> Cc: Tomoya MORINAGA; Kyungmin Park; 
> linux-mmc@vger.kernel.org; linux-kernel@vger.kernel.org; 
> andrew.chih.howe.khor@intel.com; kok.howg.ewe@intel.com
> Subject: Re: A MMC card transfer issue
> 
> Hi,
> 
> On Tue, Jan 18, 2011 at 10:05:04PM -0800, Philip Rakity wrote:
> > 
> > For 1 bit transcend cards you need these 2 patches.
> > 
> > >From 22113efd00491310da802f3b1a9a66cfcf415fac Mon Sep 17 00:00:00 
> > >2001
> > From: Aries Lee <arieslee@jmicron.com>
> > Date: Wed, 15 Dec 2010 08:14:24 +0100
> > Subject: [PATCH] mmc: Test bus-width for old MMC devices
> 
> Present in 2.6.38-rc1.
> 
> > >From 08c82dfad2458f8f9b83126224a85e7ea9e2b046 Mon Sep 17 00:00:00 
> > >2001
> > From: Takashi Iwai <tiwai@suse.de>
> > Date: Wed, 22 Dec 2010 09:59:44 +0100
> > Subject: [PATCH] mmc: fix mmc_set_bus_width_ddr() call without 
> > bus-width-test cap
> 
> Also present in 2.6.38-rc1.
> 
> So, please re-test against 2.6.38-rc1 and let us know whether 
> you still have problems.  Thanks,
> 
> -- 
> Chris Ball   <cjb@laptop.org>   <http://printf.net/>
> One Laptop Per Child
> 

^ permalink raw reply	[flat|nested] 26+ messages in thread

* RE: A MMC card transfer issue
  2011-01-19 17:42             ` Chris Ball
  2011-01-19 23:49               ` Tomoya MORINAGA
@ 2011-01-26  8:28               ` Tomoya MORINAGA
  2011-01-26 15:42                 ` Philip Rakity
  1 sibling, 1 reply; 26+ messages in thread
From: Tomoya MORINAGA @ 2011-01-26  8:28 UTC (permalink / raw)
  To: 'Chris Ball', 'Philip Rakity'
  Cc: 'Kyungmin Park', linux-mmc, linux-kernel,
	andrew.chih.howe.khor, kok.howg.ewe

On Thursday, January 20, 2011 2:43 AM, Chris Ball wrote
> So, please re-test against 2.6.38-rc1 and let us know whether 
> you still have problems.  Thanks,
I have tested the latest "2.6.38-rc2".
However, the issue remains to be seen.

Thanks in advance,
-----------------------------------------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.

> -----Original Message-----
> From: Chris Ball [mailto:cjb@laptop.org] 
> Sent: Thursday, January 20, 2011 2:43 AM
> To: Philip Rakity
> Cc: Tomoya MORINAGA; Kyungmin Park; 
> linux-mmc@vger.kernel.org; linux-kernel@vger.kernel.org; 
> andrew.chih.howe.khor@intel.com; kok.howg.ewe@intel.com
> Subject: Re: A MMC card transfer issue
> 
> Hi,
> 
> On Tue, Jan 18, 2011 at 10:05:04PM -0800, Philip Rakity wrote:
> > 
> > For 1 bit transcend cards you need these 2 patches.
> > 
> > >From 22113efd00491310da802f3b1a9a66cfcf415fac Mon Sep 17 00:00:00 
> > >2001
> > From: Aries Lee <arieslee@jmicron.com>
> > Date: Wed, 15 Dec 2010 08:14:24 +0100
> > Subject: [PATCH] mmc: Test bus-width for old MMC devices
> 
> Present in 2.6.38-rc1.
> 
> > >From 08c82dfad2458f8f9b83126224a85e7ea9e2b046 Mon Sep 17 00:00:00 
> > >2001
> > From: Takashi Iwai <tiwai@suse.de>
> > Date: Wed, 22 Dec 2010 09:59:44 +0100
> > Subject: [PATCH] mmc: fix mmc_set_bus_width_ddr() call without 
> > bus-width-test cap
> 
> Also present in 2.6.38-rc1.
> 
> So, please re-test against 2.6.38-rc1 and let us know whether 
> you still have problems.  Thanks,
> 
> -- 
> Chris Ball   <cjb@laptop.org>   <http://printf.net/>
> One Laptop Per Child
> 


^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: A MMC card transfer issue
  2011-01-26  8:28               ` Tomoya MORINAGA
@ 2011-01-26 15:42                 ` Philip Rakity
  2011-01-27  1:00                   ` Tomoya MORINAGA
  0 siblings, 1 reply; 26+ messages in thread
From: Philip Rakity @ 2011-01-26 15:42 UTC (permalink / raw)
  To: Tomoya MORINAGA
  Cc: Chris Ball, Kyungmin Park, linux-mmc@vger.kernel.org,
	linux-kernel@vger.kernel.org, andrew.chih.howe.khor@intel.com,
	kok.howg.ewe@intel.com


Did you define the CAP for BUS WIDTH ? 

MMC_CAP_BUS_WIDTH_TEST 

in the driver or the platform driver ?

Philip


On Jan 26, 2011, at 12:28 AM, Tomoya MORINAGA wrote:

> On Thursday, January 20, 2011 2:43 AM, Chris Ball wrote
>> So, please re-test against 2.6.38-rc1 and let us know whether 
>> you still have problems.  Thanks,
> I have tested the latest "2.6.38-rc2".
> However, the issue remains to be seen.
> 
> Thanks in advance,
> -----------------------------------------
> Tomoya MORINAGA
> OKI SEMICONDUCTOR CO., LTD.
> 
>> -----Original Message-----
>> From: Chris Ball [mailto:cjb@laptop.org] 
>> Sent: Thursday, January 20, 2011 2:43 AM
>> To: Philip Rakity
>> Cc: Tomoya MORINAGA; Kyungmin Park; 
>> linux-mmc@vger.kernel.org; linux-kernel@vger.kernel.org; 
>> andrew.chih.howe.khor@intel.com; kok.howg.ewe@intel.com
>> Subject: Re: A MMC card transfer issue
>> 
>> Hi,
>> 
>> On Tue, Jan 18, 2011 at 10:05:04PM -0800, Philip Rakity wrote:
>>> 
>>> For 1 bit transcend cards you need these 2 patches.
>>> 
>>>> From 22113efd00491310da802f3b1a9a66cfcf415fac Mon Sep 17 00:00:00 
>>>> 2001
>>> From: Aries Lee <arieslee@jmicron.com>
>>> Date: Wed, 15 Dec 2010 08:14:24 +0100
>>> Subject: [PATCH] mmc: Test bus-width for old MMC devices
>> 
>> Present in 2.6.38-rc1.
>> 
>>>> From 08c82dfad2458f8f9b83126224a85e7ea9e2b046 Mon Sep 17 00:00:00 
>>>> 2001
>>> From: Takashi Iwai <tiwai@suse.de>
>>> Date: Wed, 22 Dec 2010 09:59:44 +0100
>>> Subject: [PATCH] mmc: fix mmc_set_bus_width_ddr() call without 
>>> bus-width-test cap
>> 
>> Also present in 2.6.38-rc1.
>> 
>> So, please re-test against 2.6.38-rc1 and let us know whether 
>> you still have problems.  Thanks,
>> 
>> -- 
>> Chris Ball   <cjb@laptop.org>   <http://printf.net/>
>> One Laptop Per Child
>> 
> 


^ permalink raw reply	[flat|nested] 26+ messages in thread

* RE: A MMC card transfer issue
  2011-01-26 15:42                 ` Philip Rakity
@ 2011-01-27  1:00                   ` Tomoya MORINAGA
  2011-01-27  1:03                     ` Philip Rakity
  0 siblings, 1 reply; 26+ messages in thread
From: Tomoya MORINAGA @ 2011-01-27  1:00 UTC (permalink / raw)
  To: 'Philip Rakity'
  Cc: 'Chris Ball', 'Kyungmin Park', linux-mmc,
	linux-kernel, andrew.chih.howe.khor, kok.howg.ewe

Hi Philip,

On Thursday, January 27, 2011 12:42 AM, Philip Rakity wrote:
> Did you define the CAP for BUS WIDTH ? 
> 
> MMC_CAP_BUS_WIDTH_TEST 
> 
> in the driver or the platform driver ?

Let me make the above meaning clear.

I don't modify kernel source code "drivers/mmc" at all
Is the above mean I must modify something kernel source code ?

Thanks,
-----------------------------------------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.

^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: A MMC card transfer issue
  2011-01-27  1:00                   ` Tomoya MORINAGA
@ 2011-01-27  1:03                     ` Philip Rakity
  2011-01-27  1:31                       ` Tomoya MORINAGA
  0 siblings, 1 reply; 26+ messages in thread
From: Philip Rakity @ 2011-01-27  1:03 UTC (permalink / raw)
  To: Tomoya MORINAGA
  Cc: Chris Ball, Kyungmin Park, linux-mmc@vger.kernel.org,
	linux-kernel@vger.kernel.org, andrew.chih.howe.khor@intel.com,
	kok.howg.ewe@intel.com


yes

you need to have the driver or the low level code enable this QUIRK.

which mmc driver are you using.

On Jan 26, 2011, at 5:00 PM, Tomoya MORINAGA wrote:

> Hi Philip,
> 
> On Thursday, January 27, 2011 12:42 AM, Philip Rakity wrote:
>> Did you define the CAP for BUS WIDTH ? 
>> 
>> MMC_CAP_BUS_WIDTH_TEST 
>> 
>> in the driver or the platform driver ?
> 
> Let me make the above meaning clear.
> 
> I don't modify kernel source code "drivers/mmc" at all
> Is the above mean I must modify something kernel source code ?
> 
> Thanks,
> -----------------------------------------
> Tomoya MORINAGA
> OKI SEMICONDUCTOR CO., LTD.
> 


^ permalink raw reply	[flat|nested] 26+ messages in thread

* RE: A MMC card transfer issue
  2011-01-27  1:03                     ` Philip Rakity
@ 2011-01-27  1:31                       ` Tomoya MORINAGA
  2011-01-27  1:43                         ` Philip Rakity
  0 siblings, 1 reply; 26+ messages in thread
From: Tomoya MORINAGA @ 2011-01-27  1:31 UTC (permalink / raw)
  To: 'Philip Rakity'
  Cc: 'Chris Ball', 'Kyungmin Park', linux-mmc,
	linux-kernel, andrew.chih.howe.khor, kok.howg.ewe,
	'Toshiharu Okada'

Hi Philip,

> which MMC driver are you using.
Could you teach me how to get the information ?

> you need to have the driver or the low level code enable this QUIRK.
BTW, Is the above permanent treatment?
I think modifying kernel source code isn't preferred.

Thanks,
-----------------------------------------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.

> -----Original Message-----
> From: Philip Rakity [mailto:prakity@marvell.com] 
> Sent: Thursday, January 27, 2011 10:04 AM
> To: Tomoya MORINAGA
> Cc: Chris Ball; Kyungmin Park; linux-mmc@vger.kernel.org; 
> linux-kernel@vger.kernel.org; 
> andrew.chih.howe.khor@intel.com; kok.howg.ewe@intel.com
> Subject: Re: A MMC card transfer issue
> 
> 
> yes
> 
> you need to have the driver or the low level code enable this QUIRK.
> 
> which mmc driver are you using.
> 
> On Jan 26, 2011, at 5:00 PM, Tomoya MORINAGA wrote:
> 
> > Hi Philip,
> > 
> > On Thursday, January 27, 2011 12:42 AM, Philip Rakity wrote:
> >> Did you define the CAP for BUS WIDTH ? 
> >> 
> >> MMC_CAP_BUS_WIDTH_TEST
> >> 
> >> in the driver or the platform driver ?
> > 
> > Let me make the above meaning clear.
> > 
> > I don't modify kernel source code "drivers/mmc" at all Is the above 
> > mean I must modify something kernel source code ?
> > 
> > Thanks,
> > -----------------------------------------
> > Tomoya MORINAGA
> > OKI SEMICONDUCTOR CO., LTD.
> > 
> 


^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: A MMC card transfer issue
  2011-01-27  1:31                       ` Tomoya MORINAGA
@ 2011-01-27  1:43                         ` Philip Rakity
  2011-01-27  3:20                           ` Tomoya MORINAGA
  0 siblings, 1 reply; 26+ messages in thread
From: Philip Rakity @ 2011-01-27  1:43 UTC (permalink / raw)
  To: Tomoya MORINAGA
  Cc: Chris Ball, Kyungmin Park, linux-mmc@vger.kernel.org,
	linux-kernel@vger.kernel.org, andrew.chih.howe.khor@intel.com,
	kok.howg.ewe@intel.com, Toshiharu Okada


There is no good answer.  

Doing this patch for 2.6.20 or so a long time ago had problems because some controllers did not work.  The failures were equally unpleasant.

The failure you see today is at least not a regression since 1 bit did not work before.  

We hope that developers who know their h/w works add the CAP. 


On Jan 26, 2011, at 5:31 PM, Tomoya MORINAGA wrote:

> Hi Philip,
> 
>> which MMC driver are you using.
> Could you teach me how to get the information ?
> 
>> you need to have the driver or the low level code enable this QUIRK.
> BTW, Is the above permanent treatment?
> I think modifying kernel source code isn't preferred.
> 
> Thanks,
> -----------------------------------------
> Tomoya MORINAGA
> OKI SEMICONDUCTOR CO., LTD.
> 
>> -----Original Message-----
>> From: Philip Rakity [mailto:prakity@marvell.com] 
>> Sent: Thursday, January 27, 2011 10:04 AM
>> To: Tomoya MORINAGA
>> Cc: Chris Ball; Kyungmin Park; linux-mmc@vger.kernel.org; 
>> linux-kernel@vger.kernel.org; 
>> andrew.chih.howe.khor@intel.com; kok.howg.ewe@intel.com
>> Subject: Re: A MMC card transfer issue
>> 
>> 
>> yes
>> 
>> you need to have the driver or the low level code enable this QUIRK.
>> 
>> which mmc driver are you using.
>> 
>> On Jan 26, 2011, at 5:00 PM, Tomoya MORINAGA wrote:
>> 
>>> Hi Philip,
>>> 
>>> On Thursday, January 27, 2011 12:42 AM, Philip Rakity wrote:
>>>> Did you define the CAP for BUS WIDTH ? 
>>>> 
>>>> MMC_CAP_BUS_WIDTH_TEST
>>>> 
>>>> in the driver or the platform driver ?
>>> 
>>> Let me make the above meaning clear.
>>> 
>>> I don't modify kernel source code "drivers/mmc" at all Is the above 
>>> mean I must modify something kernel source code ?
>>> 
>>> Thanks,
>>> -----------------------------------------
>>> Tomoya MORINAGA
>>> OKI SEMICONDUCTOR CO., LTD.
>>> 
>> 
> 


^ permalink raw reply	[flat|nested] 26+ messages in thread

* RE: A MMC card transfer issue
  2011-01-27  1:43                         ` Philip Rakity
@ 2011-01-27  3:20                           ` Tomoya MORINAGA
       [not found]                             ` <0DBFCBB8-B4A3-46A6-A68D-14FAED451619@marvell.com>
  0 siblings, 1 reply; 26+ messages in thread
From: Tomoya MORINAGA @ 2011-01-27  3:20 UTC (permalink / raw)
  To: 'Philip Rakity'
  Cc: 'Chris Ball', 'Kyungmin Park', linux-mmc,
	linux-kernel, andrew.chih.howe.khor, kok.howg.ewe,
	'Toshiharu Okada'

Hi Philip,

> which MMC driver are you using.
According to boot message, it seems sdhci.c is loaded.

Do I add only  "mmc->caps |=  MMC_CAP_BUS_WIDTH_TEST" in sdhc.c ?

Thanks,
-----------------------------------------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.

> -----Original Message-----
> From: Philip Rakity [mailto:prakity@marvell.com] 
> Sent: Thursday, January 27, 2011 10:44 AM
> To: Tomoya MORINAGA
> Cc: Chris Ball; Kyungmin Park; linux-mmc@vger.kernel.org; 
> linux-kernel@vger.kernel.org; 
> andrew.chih.howe.khor@intel.com; kok.howg.ewe@intel.com; 
> Toshiharu Okada
> Subject: Re: A MMC card transfer issue
> 
> 
> There is no good answer.  
> 
> Doing this patch for 2.6.20 or so a long time ago had 
> problems because some controllers did not work.  The failures 
> were equally unpleasant.
> 
> The failure you see today is at least not a regression since 
> 1 bit did not work before.  
> 
> We hope that developers who know their h/w works add the CAP. 
> 
> 
> On Jan 26, 2011, at 5:31 PM, Tomoya MORINAGA wrote:
> 
> > Hi Philip,
> > 
> >> which MMC driver are you using.
> > Could you teach me how to get the information ?
> > 
> >> you need to have the driver or the low level code enable 
> this QUIRK.
> > BTW, Is the above permanent treatment?
> > I think modifying kernel source code isn't preferred.
> > 
> > Thanks,
> > -----------------------------------------
> > Tomoya MORINAGA
> > OKI SEMICONDUCTOR CO., LTD.
> > 
> >> -----Original Message-----
> >> From: Philip Rakity [mailto:prakity@marvell.com]
> >> Sent: Thursday, January 27, 2011 10:04 AM
> >> To: Tomoya MORINAGA
> >> Cc: Chris Ball; Kyungmin Park; linux-mmc@vger.kernel.org; 
> >> linux-kernel@vger.kernel.org; andrew.chih.howe.khor@intel.com; 
> >> kok.howg.ewe@intel.com
> >> Subject: Re: A MMC card transfer issue
> >> 
> >> 
> >> yes
> >> 
> >> you need to have the driver or the low level code enable 
> this QUIRK.
> >> 
> >> which mmc driver are you using.
> >> 
> >> On Jan 26, 2011, at 5:00 PM, Tomoya MORINAGA wrote:
> >> 
> >>> Hi Philip,
> >>> 
> >>> On Thursday, January 27, 2011 12:42 AM, Philip Rakity wrote:
> >>>> Did you define the CAP for BUS WIDTH ? 
> >>>> 
> >>>> MMC_CAP_BUS_WIDTH_TEST
> >>>> 
> >>>> in the driver or the platform driver ?
> >>> 
> >>> Let me make the above meaning clear.
> >>> 
> >>> I don't modify kernel source code "drivers/mmc" at all Is 
> the above 
> >>> mean I must modify something kernel source code ?
> >>> 
> >>> Thanks,
> >>> -----------------------------------------
> >>> Tomoya MORINAGA
> >>> OKI SEMICONDUCTOR CO., LTD.
> >>> 
> >> 
> > 
> 


^ permalink raw reply	[flat|nested] 26+ messages in thread

[parent not found: <0DBFCBB8-B4A3-46A6-A68D-14FAED451619@marvell.com>]

[parent not found: <9992F28C7C0C445E956D351E3774C821@hacdom.okisemi.com>]

[parent not found: <82CB4E44-6543-4578-ACE4-37850FC4A49A@marvell.com>]

[parent not found: <EE9384C765994E26857C78E3D3A19304@hacdom.okisemi.com    >]

[parent not found: <EE9384C765994E26857C78E3D3A19304@hacdom.okisemi.com>]

[parent not found: <EE9384C765994E26857C78E3D3A19304@hacdom.okisemi.com >]

[parent not found: <EE9384C765994E26857C78E3D3A19304@hacdom.okisemi.com   >]

[parent not found: <AF584C10-A796-43 5 B-8AB2-DA6D6C0E3FD7@marvell.com>]

[parent not found: <DE7D3AAF538943459079D18D0CE6ED44@hacdom.okisemi.com>]

[parent not found: <DDF13C55-A8A1-45C1-AE9A-A76754ED7008@marvell.com>]

[parent not found: <4425BB0054B748C68A25DD1DFBBB52A7@hacdom.okisemi.com>]

[parent not found: <5E1B7BBD-C96E-4CC0-B03B-ADCEB0120085@marvell.com>]

[parent not found: <0C438F11-132E-4639-820D-0E42EEDCD6E7@marvell.com>]

[parent not found: <671E3EC021E946A383C65F07A0101B27@hacdom.okisemi.com>]

[parent not found: <16706427-F00E-46F3-B0B4-9B7F06AD0E71@marvell.com>]

* Re: A MMC card transfer issue
       [not found]                                                   ` <16706427-F00E-46F3-B0B4-9B7F06AD0E71@marvell.com>
@ 2011-01-31 16:40                                                     ` Philip Rakity
  2011-01-31 17:18                                                       ` Nicolas Pitre
  2011-03-23  0:31                                                       ` Tomoya MORINAGA
  0 siblings, 2 replies; 26+ messages in thread
From: Philip Rakity @ 2011-01-31 16:40 UTC (permalink / raw)
  To: Nicolas Pitre
  Cc: Tomoya MORINAGA, Toshiharu Okada, Manabu Miyata, Takahiro Shimizu,
	linux-mmc@vger.kernel.org


Nico,

Need some advice on how to solve a problem with mmc.  Some background

>>>
>>> mmc cards have NO card specific data field to say the bus
>>> width that is supported.  SD cards have this field.
>>>
>>> The only way to know what width a mmc card supports is to
>>> probe the card sending CMD14/CMD19. (JEDEC standard 84- A441).
>>>
>>> In my system with the mods we made we can detect all mmc
>>> cards correctly.  The CMD14/CMD19 does not work correctly on Tomoya's system.
The CMD14/CMD19 times out. (see below)  The CMD14/CMD19 works on multiple Marvell SoC chips, Tomoya's
uses a PCI controller.

The transcend mmc card does not have the PHYSICAL pins for 4 bit mode; only 1 bit can be supported.

Testing the bus width is the recommend way to find out the bus width.  The current behavior when the
QUIRK is not defined is to default to 4 bit mode (same as has been done historically).

The only way to guarantee that cards really do work would be to default to 1 bit mode but this has a
4x performance degradation.

One possible solution would be to try to do a test read operation on the mmc card if the bus test failed
and see if there is an error.  In this case change the bus width to 1 bit.

a) Do you think this is a good idea?  --
b) How to plumb it in ?  -- can you sketch something out and I will try to implement it.

regards,

Philip

On Jan 30, 2011, at 9:57 PM, Philip Rakity wrote:

>
> On Jan 30, 2011, at 8:16 PM, Tomoya MORINAGA wrote:
>
>> Hi Philip,
>>
>>> The only way to know what width a mmc card supports is to
>>> probe the card sending CMD14/CMD19. (JEDEC standard 84- A441).
>>>
>>> In my system with the mods we made we can detect all mmc
>>> cards correctly..
>>
>> What's your system ? Linux ?
>
> linux -- 4 different Marvell SoC chips.  Running linux-next.   SD Host cotnroler
> supports  SD2.0 and now SD 3.0 specs.
>>
>>> The current code without BUS_WIDTH QUIRK defined -- breaks
>>> the transcend card in 1 bit mode but allows 4 bit cards to work.
>>> do you agree ?
>>
>> Yes,
>> Currently, since MMC driver works as 4-bit mode,
>> MMC-v4-1bit doesn't work.
>>
>>>
>>> I do not know how to fix the problem in any other way...
>>>
>>
>> possible choices are like below, I think.
>> 1.  always going into 1 bit mode (Like Windows)
>> 2.  As mentioned previous my mail, support 1-bit mode option by kernel configuration.
>
> Propose patch for this or we could extend existing QUIRK or CAP for 1 bit mode
> will look in the morning.
>
>> 3. Not support like the 1bit-MMC card (current spec)
>
> In some systems.
>
> The good news is that the transcend card IS REALLY STRANGE ! and quite an EXCEPTION.
> The bad news is things don't work all the time. Let me think how we could go into 1 bit mode.
> Let me post something to the mmc/ list on this -- Nico  has good good ideas on how to do things like
> this in the mmc/core layer.
>
> Philip
>
>
>
>>
>> Thanks,
>> -----------------------------------------
>> Tomoya MORINAGA
>> OKI SEMICONDUCTOR CO., LTD.
>>
>>> -----Original Message-----
>>> From: Philip Rakity [mailto:prakity@marvell.com]
>>> Sent: Monday, January 31, 2011 6:49 AM
>>> To: Tomoya MORINAGA
>>> Cc: Toshiharu Okada; Manabu Miyata; Takahiro Shimizu
>>> Subject: Re: A MMC card transfer issue
>>>
>>>
>>> Back to the beginning ..
>>>
>>> We also discovered that having a SD  controller that supports
>>> 8 bit data and a board design that does not -- does not all
>>> the 8 bit card to work at full speed.
>>> Using the controller values is not sufficient.
>>>
>>> We discovered that the transcend 1 bit card does not work in linux.
>>> The transcend mmc card does NOT have the electrical pins to
>>> support 4 bit mode --- compare the card against some other SD
>>> cards you have and you will see the missing pins.
>>>
>>> mmc cards have NO card specific data field to say the bus
>>> width that is supported.  SD cards have this field.
>>>
>>> The only way to know what width a mmc card supports is to
>>> probe the card sending CMD14/CMD19. (JEDEC standard 84- A441).
>>>
>>> In my system with the mods we made we can detect all mmc
>>> cards correctly..
>>>
>>> I understand it does not work on your system.
>>>
>>> The current code without BUS_WIDTH QUIRK defined -- breaks
>>> the transcend card in 1 bit mode but allows 4 bit cards to work.
>>> do you agree ?
>>>
>>> I do not believe the code worked before the bus width test
>>> otherwise I would not have seen to problem and we would not
>>> have generated any patches.
>>>
>>> You could guarantee all mmc cards work with bus_test by
>>> always going into 1 bit mode -- but his has a severe
>>> performance impact.
>>>
>>> I do not know how to fix the problem in any other way...
>>>
>>> Any suggestions
>>>
>>> Philip
>>>
>>>
>>>
>>>
>>> On Jan 28, 2011, at 8:13 AM, Philip Rakity wrote:
>>>
>>>>
>>>> On Jan 28, 2011, at 12:44 AM, Tomoya MORINAGA wrote:
>>>>
>>>>> Hi  Philip,
>>>>>
>>>>> It doesn't detect the 1bit-MMC correctly.
>>>>>> cmd.flags &= ~MSP_RSP_CRC;
>>>>> BTW, the above is not MSP_RSP_CRC but MMC_RSP_CRC.
>>>>>
>>>> My topo
>>>>>
>>>>> Root cause is MMC driver can't judge whether the interted
>>> MMC-v4-card is 1-bit or not.
>>>>> Thus, I think a user can only set "Use MMC-v4-1bit" or not.
>>>>
>>>> this is why the QUIRK is there.
>>>>>
>>>>> Though sent the following last November, How about the
>>> following line
>>>>> valid or invalid with compile option (Kconfig) ?
>>>>>
>>>>> In fact, invalidating the following line, the MMC-v4-1bit
>>> card can be detected correctly.
>>>>
>>>> which line ?
>>>>
>>>> The bus width test is needed for 8 bit cards.
>>>>
>>>> Philip
>>>>
>>>>>
>>>>>> linux/drivers/mmc/core/mmc.c
>>>>>>
>>>>>> 505        /*
>>>>>> 506         * Activate wide bus (if supported).
>>>>>> 507         */
>>>>>> 508        if ((card->csd.mmca_vsn >= CSD_SPEC_VER_4) &&
>>>>>> 509            (host->caps & (MMC_CAP_4_BIT_DATA |
>>>>>> MMC_CAP_8_BIT_DATA))) {
>>>>>> 510                unsigned ext_csd_bit, bus_width;
>>>>>> 511
>>>>>> 512                if (host->caps & MMC_CAP_8_BIT_DATA) {
>>>>>> 513                        ext_csd_bit = EXT_CSD_BUS_WIDTH_8;
>>>>>> 514                        bus_width = MMC_BUS_WIDTH_8;
>>>>>> 515                } else {
>>>>>> 516                        ext_csd_bit = EXT_CSD_BUS_WIDTH_4;
>>>>>> 517                        bus_width = MMC_BUS_WIDTH_4;
>>>>>> 518                }
>>>>>> 519
>>>>>> 520                err = mmc_switch(card, EXT_CSD_CMD_SET_NORMAL,
>>>>>> 521                                 EXT_CSD_BUS_WIDTH,
>>> ext_csd_bit);
>>>>>> 522
>>>>>> 523                if (err && err != -EBADMSG)
>>>>>> 524                        goto free_card;
>>>>>> 525
>>>>>> 526                if (err) {
>>>>>> 527                        printk(KERN_WARNING "%s: switch
>>>>>> to bus width %d "
>>>>>> 528                               "failed\n",
>>>>>> mmc_hostname(card->host),
>>>>>> 529                               1 << bus_width);
>>>>>> 530                        err = 0;
>>>>>> 531                } else {
>>>>>> 532                        mmc_set_bus_width(card->host,
>>> bus_width);
>>>>>> 533                }
>>>>>> 534        }
>>>>>> 535
>>>>>
>>>>> With Best Regards,
>>>>> -----------------------------------------
>>>>> Tomoya MORINAGA
>>>>> OKI SEMICONDUCTOR CO., LTD.
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Philip Rakity [mailto:prakity@marvell.com]
>>>>>> Sent: Friday, January 28, 2011 2:28 PM
>>>>>> To: Tomoya MORINAGA
>>>>>> Cc: Toshiharu Okada; Manabu Miyata
>>>>>> Subject: Re: A MMC card transfer issue
>>>>>>
>>>>>>
>>>>>> The SD controller you are using is broken.  It does not
>>> handle bus
>>>>>> width testing (CMD19/CMD14) gives CRC errors.  Not sure
>>> now to fix
>>>>>> this... or work around it.
>>>>>>
>>>>>> It is possible we should define a new RSP type that does
>>> not specify
>>>>>> CRC  (this is contained in the RESP_R1 see mmc_ops.c when
>>> doing the
>>>>>> send_bus_test().
>>>>>>
>>>>>> as a fast hack. add a line after
>>>>>>
>>>>>> cmd.flags = MMC_RSP_SPI_R1 |  MMC_RSP_R1 | MMC_CMD_ADTC;
>>>>>>
>>>>>> cmd.flags &= ~MSP_RSP_CRC;
>>>>>>
>>>>>>
>>>>>> and see what happens.
>>>>>>
>>>>>>
>>>>>> This is the problem I saw before in 2.6.20 and we could
>>> not figure
>>>>>> out a work around.
>>>>>>
>>>>>> Philip
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Jan 27, 2011, at 5:31 PM, Tomoya MORINAGA wrote:
>>>>>>
>>>>>>> Hi Philip,
>>>>>>>
>>>>>>> I attached boot log with  CONFIG_MMC_DEBUG.
>>>>>>>
>>>>>>> With Best Regards,
>>>>>>> -----------------------------------------
>>>>>>> Tomoya MORINAGA
>>>>>>> OKI SEMICONDUCTOR CO., LTD.
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Philip Rakity [mailto:prakity@marvell.com]
>>>>>>>> Sent: Friday, January 28, 2011 9:59 AM
>>>>>>>> To: Tomoya MORINAGA
>>>>>>>> Cc: Toshiharu Okada; Manabu Miyata
>>>>>>>> Subject: Re: A MMC card transfer issue
>>>>>>>>
>>>>>>>>
>>>>>>>> ouch
>>>>>>>>
>>>>>>>> please send complete console log.  Want to see what
>>> startup looks
>>>>>>>> like.
>>>>>>>>
>>>>>>>> you will need to enable CONFIG_MMC_DEBUG
>>>>>>>>
>>>>>>>> it is the only way to get a trace from the linux point of view.
>>>>>>>>
>>>>>>>> PHilip
>>>>>>>>
>>>>>>>> On Jan 27, 2011, at 4:29 PM, Tomoya MORINAGA wrote:
>>>>>>>>
>>>>>>>>> Hi Philip,
>>>>>>>>>
>>>>>>>>> According to your saying,
>>>>>>>>> I deleted the following 2-lines in drivers/mmc/core/mmc.c
>>>>>>>>>
>>>>>>>>>> if (!(host->caps & MMC_CAP_BUS_WIDTH_TEST))
>>>>>>>>>>       break;
>>>>>>>>>
>>>>>>>>> However, the issue remains to be seen.
>>>>>>>>> I attached the dmesg log.
>>>>>>>>> The error log differs from previous log.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> -----------------------------------------
>>>>>>>>> Tomoya MORINAGA
>>>>>>>>> OKI SEMICONDUCTOR CO., LTD.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Philip Rakity [mailto:prakity@marvell.com]
>>>>>>>>>> Sent: Friday, January 28, 2011 6:33 AM
>>>>>>>>>> To: Tomoya MORINAGA
>>>>>>>>>> Cc: Toshiharu Okada; Manabu Miyata
>>>>>>>>>> Subject: Re: A MMC card transfer issue
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Are you comfortable just deleting the test for the CAP for
>>>>>>>> bus width
>>>>>>>>>> in mmc.c ?
>>>>>>>>>>
>>>>>>>>>> I see you are using PCI  and SD -- this is where we
>>> had problems
>>>>>>>>>> before.
>>>>>>>>>>
>>>>>>>>>> In drivers/mmc/core/mmc.c
>>>>>>>>>>
>>>>>>>>>> change
>>>>>>>>>>
>>>>>>>>>>                       if (!err) {
>>>>>>>>>>
>>>>>>>>>> mmc_set_bus_width_ddr(card->host,
>>>>>>>>>>
>>>>>>>>>> bus_width, MMC_SDR_MODE);
>>>>>>>>>>                               /*
>>>>>>>>>>                                * If controller can't handle
>>>>>>>>>> bus width test,
>>>>>>>>>>                                * use the highest
>>> bus width to maintain
>>>>>>>>>>                                * compatibility with
>>> previous
>>>>>>>>>> MMC behavior.
>>>>>>>>>>                                */
>>>>>>>>>>                               if (!(host->caps &
>>>>>>>>>> MMC_CAP_BUS_WIDTH_TEST))
>>>>>>>>>>                                       break;
>>>>>>>>>>                               err =
>>> mmc_bus_test(card, bus_width);
>>>>>>>>>>                               if (!err)
>>>>>>>>>>                                       break;
>>>>>>>>>>                       }
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> to
>>>>>>>>>>
>>>>>>>>>>                       if (!err) {
>>>>>>>>>>
>>>>>>>>>> mmc_set_bus_width_ddr(card->host,
>>>>>>>>>>
>>>>>>>>>> bus_width, MMC_SDR_MODE);
>>>>>>>>>> #if 0
>>>>>>>>>>                               /*
>>>>>>>>>>                                * If controller can't handle
>>>>>>>>>> bus width test,
>>>>>>>>>>                                * use the highest
>>> bus width to maintain
>>>>>>>>>>                                * compatibility with
>>> previous
>>>>>>>>>> MMC behavior.
>>>>>>>>>>                                */
>>>>>>>>>>                               if (!(host->caps &
>>>>>>>>>> MMC_CAP_BUS_WIDTH_TEST))
>>>>>>>>>>                                       break; #endif
>>>>>>>>>>                               err =
>>> mmc_bus_test(card, bus_width);
>>>>>>>>>>                               if (!err)
>>>>>>>>>>                                       break;
>>>>>>>>>>                       }
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> This will tell us more about what if going on.
>>>>>>>>>>
>>>>>>>>>> Philip
>>>>>>>>>>
>>>>>>>>>> On Jan 26, 2011, at 10:36 PM, Tomoya MORINAGA wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi Philip
>>>>>>>>>>>
>>>>>>>>>>> Thank you for you help.
>>>>>>>>>>> I attached my kernel configuration file for 2.6.38-rc2.
>>>>>>>>>>>
>>>>>>>>>>> With Best Regards,
>>>>>>>>>>> -----------------------------------------
>>>>>>>>>>> Tomoya MORINAGA
>>>>>>>>>>> OKI SEMICONDUCTOR CO., LTD.
>>>>>>>>>>>
>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>> From: Philip Rakity [mailto:prakity@marvell.com]
>>>>>>>>>>>> Sent: Thursday, January 27, 2011 12:42 PM
>>>>>>>>>>>> To: Tomoya MORINAGA
>>>>>>>>>>>> Subject: Re: A MMC card transfer issue
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Lets go off list.
>>>>>>>>>>>>
>>>>>>>>>>>> send me the linux dot_config.
>>>>>>>>>>>>
>>>>>>>>>>>> I can go from there.
>>>>>>>>>>>>
>>>>>>>>>>>> Philip
>>>>>>>>>>>>
>>>>>>>>>>>> On Jan 26, 2011, at 7:20 PM, Tomoya MORINAGA wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Philip,
>>>>>>>>>>>>>
>>>>>>>>>>>>>> which MMC driver are you using.
>>>>>>>>>>>>> According to boot message, it seems sdhci.c is loaded.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Do I add only  "mmc->caps |=  MMC_CAP_BUS_WIDTH_TEST"
>>>>>>>> in sdhc.c ?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> -----------------------------------------
>>>>>>>>>>>>> Tomoya MORINAGA
>>>>>>>>>>>>> OKI SEMICONDUCTOR CO., LTD.
>>>>>>>>>>>>>
>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>> From: Philip Rakity [mailto:prakity@marvell.com]
>>>>>>>>>>>>>> Sent: Thursday, January 27, 2011 10:44 AM
>>>>>>>>>>>>>> To: Tomoya MORINAGA
>>>>>>>>>>>>>> Cc: Chris Ball; Kyungmin Park; linux-mmc@vger.kernel.org;
>>>>>>>>>>>>>> linux-kernel@vger.kernel.org;
>>>>>> andrew.chih.howe.khor@intel.com;
>>>>>>>>>>>>>> kok.howg.ewe@intel.com; Toshiharu Okada
>>>>>>>>>>>>>> Subject: Re: A MMC card transfer issue
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> There is no good answer.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Doing this patch for 2.6.20 or so a long time ago
>>>>>> had problems
>>>>>>>>>>>>>> because some controllers did not work.  The failures
>>>>>>>>>> were equally
>>>>>>>>>>>>>> unpleasant.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The failure you see today is at least not a
>>> regression since
>>>>>>>>>>>>>> 1 bit did not work before.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We hope that developers who know their h/w works add
>>>>>> the CAP.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Jan 26, 2011, at 5:31 PM, Tomoya MORINAGA wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Hi Philip,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> which MMC driver are you using.
>>>>>>>>>>>>>>> Could you teach me how to get the information ?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> you need to have the driver or the low level code enable
>>>>>>>>>>>>>> this QUIRK.
>>>>>>>>>>>>>>> BTW, Is the above permanent treatment?
>>>>>>>>>>>>>>> I think modifying kernel source code isn't preferred.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> -----------------------------------------
>>>>>>>>>>>>>>> Tomoya MORINAGA
>>>>>>>>>>>>>>> OKI SEMICONDUCTOR CO., LTD.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> -----Original Message-----
>>>>>>>>>>>>>>>> From: Philip Rakity [mailto:prakity@marvell.com]
>>>>>>>>>>>>>>>> Sent: Thursday, January 27, 2011 10:04 AM
>>>>>>>>>>>>>>>> To: Tomoya MORINAGA
>>>>>>>>>>>>>>>> Cc: Chris Ball; Kyungmin Park;
>>> linux-mmc@vger.kernel.org;
>>>>>>>>>>>>>>>> linux-kernel@vger.kernel.org;
>>>>>>>> andrew.chih.howe.khor@intel.com;
>>>>>>>>>>>>>>>> kok.howg.ewe@intel.com
>>>>>>>>>>>>>>>> Subject: Re: A MMC card transfer issue
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> yes
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> you need to have the driver or the low level code enable
>>>>>>>>>>>>>> this QUIRK.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> which mmc driver are you using.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Jan 26, 2011, at 5:00 PM, Tomoya MORINAGA wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi Philip,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Thursday, January 27, 2011 12:42 AM, Philip
>>>>>> Rakity wrote:
>>>>>>>>>>>>>>>>>> Did you define the CAP for BUS WIDTH ?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> MMC_CAP_BUS_WIDTH_TEST
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> in the driver or the platform driver ?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Let me make the above meaning clear.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I don't modify kernel source code
>>> "drivers/mmc" at all Is
>>>>>>>>>>>>>> the above
>>>>>>>>>>>>>>>>> mean I must modify something kernel source code ?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>> -----------------------------------------
>>>>>>>>>>>>>>>>> Tomoya MORINAGA
>>>>>>>>>>>>>>>>> OKI SEMICONDUCTOR CO., LTD.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> <config.config>
>>>>>>>>>>
>>>>>>>>> <Transcend_log>
>>>>>>>>
>>>>>>> <Transcend_log_debug_on>
>>>>>>
>>>>>
>>>>
>>>
>>
>


^ permalink raw reply	[flat|nested] 26+ messages in thread

* Re: A MMC card transfer issue
  2011-01-31 16:40                                                     ` Philip Rakity
@ 2011-01-31 17:18                                                       ` Nicolas Pitre
  2011-03-23  0:31                                                       ` Tomoya MORINAGA
  1 sibling, 0 replies; 26+ messages in thread
From: Nicolas Pitre @ 2011-01-31 17:18 UTC (permalink / raw)
  To: Philip Rakity
  Cc: Tomoya MORINAGA, Toshiharu Okada, Manabu Miyata, Takahiro Shimizu,
	linux-mmc@vger.kernel.org

On Mon, 31 Jan 2011, Philip Rakity wrote:

> The transcend mmc card does not have the PHYSICAL pins for 4 bit mode; only 1 bit can be supported.
> 
> Testing the bus width is the recommend way to find out the bus width.  The current behavior when the
> QUIRK is not defined is to default to 4 bit mode (same as has been done historically).
> 
> The only way to guarantee that cards really do work would be to default to 1 bit mode but this has a
> 4x performance degradation.
> 
> One possible solution would be to try to do a test read operation on the mmc card if the bus test failed
> and see if there is an error.  In this case change the bus width to 1 bit.
> 
> a) Do you think this is a good idea?  --
> b) How to plumb it in ?  -- can you sketch something out and I will try to implement it.

Sure.  This is probably a good thing to attempt lowering the bus width 
on errors.  In mmc_request_done() you could attempt switching to a 
narrower bus width and reattempt the failed command if that command was 
about some data transfer and the error was -ETIMEDOUT.


Nicolas

^ permalink raw reply	[flat|nested] 26+ messages in thread

* RE: A MMC card transfer issue
  2011-01-31 16:40                                                     ` Philip Rakity
  2011-01-31 17:18                                                       ` Nicolas Pitre
@ 2011-03-23  0:31                                                       ` Tomoya MORINAGA
  2011-03-24 14:19                                                         ` Philip Rakity
  1 sibling, 1 reply; 26+ messages in thread
From: Tomoya MORINAGA @ 2011-03-23  0:31 UTC (permalink / raw)
  To: 'Philip Rakity', 'Nicolas Pitre'
  Cc: 'Toshiharu Okada', linux-mmc

Hi Philip

Still we can see the issue in 2.6.38(The latest kernel).
In 2.6.38, is this issue resolved ?

With Best Regards,
-----------------------------------------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.

> -----Original Message-----
> From: Philip Rakity [mailto:prakity@marvell.com] 
> Sent: Tuesday, February 01, 2011 1:41 AM
> To: Nicolas Pitre
> Cc: Tomoya MORINAGA; Toshiharu Okada; Manabu Miyata; Takahiro 
> Shimizu; linux-mmc@vger.kernel.org
> Subject: Re: A MMC card transfer issue
> 


^ permalink raw reply	[flat|nested] 26+ messages in thread

* RE: A MMC card transfer issue
  2011-03-23  0:31                                                       ` Tomoya MORINAGA
@ 2011-03-24 14:19                                                         ` Philip Rakity
  2011-03-25  1:22                                                           ` Tomoya MORINAGA
  0 siblings, 1 reply; 26+ messages in thread
From: Philip Rakity @ 2011-03-24 14:19 UTC (permalink / raw)
  To: Tomoya MORINAGA, 'Nicolas Pitre'
  Cc: 'Toshiharu Okada', linux-mmc@vger.kernel.org

I think the solution is to try to rad the CSD if bus test fails.  If CSD read fails then lower bus width until it passes.  Not had time to work on this yet.  On my list of things to do.
________________________________________
From: Tomoya MORINAGA [tomoya-linux@dsn.okisemi.com]
Sent: Tuesday, March 22, 2011 5:31 PM
To: Philip Rakity; 'Nicolas Pitre'
Cc: 'Toshiharu Okada'; linux-mmc@vger.kernel.org
Subject: RE: A MMC card transfer issue

Hi Philip

Still we can see the issue in 2.6.38(The latest kernel).
In 2.6.38, is this issue resolved ?

With Best Regards,
-----------------------------------------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.

> -----Original Message-----
> From: Philip Rakity [mailto:prakity@marvell.com]
> Sent: Tuesday, February 01, 2011 1:41 AM
> To: Nicolas Pitre
> Cc: Tomoya MORINAGA; Toshiharu Okada; Manabu Miyata; Takahiro
> Shimizu; linux-mmc@vger.kernel.org
> Subject: Re: A MMC card transfer issue
>

^ permalink raw reply	[flat|nested] 26+ messages in thread

* RE: A MMC card transfer issue
  2011-03-24 14:19                                                         ` Philip Rakity
@ 2011-03-25  1:22                                                           ` Tomoya MORINAGA
  0 siblings, 0 replies; 26+ messages in thread
From: Tomoya MORINAGA @ 2011-03-25  1:22 UTC (permalink / raw)
  To: 'Philip Rakity', 'Nicolas Pitre'
  Cc: 'Toshiharu Okada', linux-mmc, kok.howg.ewe,
	'Lai, Mee Sim'

Hi  Philip,

On Thursday, March 24, 2011 11:19 PM, Philip Rakity wrote:
> I think the solution is to try to rad the CSD if bus test 
> fails.  If CSD read fails then lower bus width until it 
> passes.  Not had time to work on this yet.  On my list of 
> things to do.
OK.
Do you have fixed schedule for this work ?
If yes, let me know the schedule.

Thanks,
-----------------------------------------
Tomoya MORINAGA
OKI SEMICONDUCTOR CO., LTD.


^ permalink raw reply	[flat|nested] 26+ messages in thread

end of thread, other threads:[~2011-03-25  1:22 UTC | newest]

Thread overview: 26+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-11-09  5:39 A MMC card transfer issue Tomoya MORINAGA
2010-11-09  5:53 ` Kyungmin Park
2010-11-09  7:29   ` Tomoya MORINAGA
2010-11-11  2:59   ` Tomoya MORINAGA
2010-12-01  1:08     ` Tomoya MORINAGA
     [not found]       ` <2D50F985-2383-4406-8514-DFE462A5F546@marvell.com>
2010-12-01  3:15         ` Philip Rakity
     [not found]         ` <4D2E0464ABB54FFF9C10583336E27879@hacdom.okisemi.com>
2011-01-19  0:59           ` Philip Rakity
2011-01-19  1:29             ` Tomoya MORINAGA
2011-01-19  1:41               ` Chris Ball
2011-01-19  3:12                 ` Philip Rakity
2011-01-19  6:05           ` Philip Rakity
2011-01-19  6:30             ` Tomoya MORINAGA
2011-01-19 17:42             ` Chris Ball
2011-01-19 23:49               ` Tomoya MORINAGA
2011-01-26  8:28               ` Tomoya MORINAGA
2011-01-26 15:42                 ` Philip Rakity
2011-01-27  1:00                   ` Tomoya MORINAGA
2011-01-27  1:03                     ` Philip Rakity
2011-01-27  1:31                       ` Tomoya MORINAGA
2011-01-27  1:43                         ` Philip Rakity
2011-01-27  3:20                           ` Tomoya MORINAGA
     [not found]                             ` <0DBFCBB8-B4A3-46A6-A68D-14FAED451619@marvell.com>
     [not found]                               ` <9992F28C7C0C445E956D351E3774C821@hacdom.okisemi.com>
     [not found]                                 ` <82CB4E44-6543-4578-ACE4-37850FC4A49A@marvell.com>
     [not found]                                   ` <EE9384C765994E26857C78E3D3A19304@hacdom.okisemi.com    >
     [not found]                                   ` <EE9384C765994E26857C78E3D3A19304@hacdom.okisemi.com>
     [not found]                                   ` <EE9384C765994E26857C78E3D3A19304@hacdom.okisemi.com >
     [not found]                                   ` <EE9384C765994E26857C78E3D3A19304@hacdom.okisemi.com   >
     [not found]                                     ` <AF584C10-A796-43 5 B-8AB2-DA6D6C0E3FD7@marvell.com>
     [not found]                                       ` <DE7D3AAF538943459079D18D0CE6ED44@hacdom.okisemi.com>
     [not found]                                         ` <DDF13C55-A8A1-45C1-AE9A-A76754ED7008@marvell.com>
     [not found]                                           ` <4425BB0054B748C68A25DD1DFBBB52A7@hacdom.okisemi.com>
     [not found]                                             ` <5E1B7BBD-C96E-4CC0-B03B-ADCEB0120085@marvell.com>
     [not found]                                               ` <0C438F11-132E-4639-820D-0E42EEDCD6E7@marvell.com>
     [not found]                                                 ` <671E3EC021E946A383C65F07A0101B27@hacdom.okisemi.com>
     [not found]                                                   ` <16706427-F00E-46F3-B0B4-9B7F06AD0E71@marvell.com>
2011-01-31 16:40                                                     ` Philip Rakity
2011-01-31 17:18                                                       ` Nicolas Pitre
2011-03-23  0:31                                                       ` Tomoya MORINAGA
2011-03-24 14:19                                                         ` Philip Rakity
2011-03-25  1:22                                                           ` Tomoya MORINAGA

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox