On 14/02/17 21:25, Daniel Drake wrote: > On the Acer ES1-432 (Apollo Lake), the eMMC storage is not detected. > Errors like these appear in dmesg: > > mmc0: starting CMD13 arg 00010000 flags 00000195 > sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x000a8001 > mmc0: req failed (CMD13): -84, retrying... > sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x000a8001 > mmc0: req failed (CMD13): -84, retrying... > sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x000a8001 > mmc0: req failed (CMD13): -84, retrying... > sdhci [sdhci_irq()]: *** mmc0 got interrupt: 0x000a8001 > mmc0: req done (CMD13): -84: 00000000 00000000 00000000 00000000 > mmc0: mmc_select_hs200 failed, error -84 > mmc0: error -84 whilst initialising MMC card > > Full dmesg attached (with MMC_DEBUG logs). > > We have reproduced this on Linux 4.8 and 4.9. > > If we add a PCI quirk for SDHCI_QUIRK2_BROKEN_HS200 then the eMMC is usable. > > Any ideas or debugging suggestions? We would like to get this fixed > and I don't think a PCI quirk is the right answer. Upstream we no longer check for CRC errors after the HS200 switch. Here is the relevant patch which will be in v4.10 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ef3d232245ab7a1bf361c52449e612e4c8b7c5ab -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
