On Mon, Jun 20, 2011 at 3:40 PM, Chris Ball <c...@laptop.org> wrote: > Hi Andy, > > On Mon, Jun 20 2011, Chris Ball wrote: >> On Mon, Jun 20 2011, Andrew Lutomirski wrote: >>> I have an SDHC card that works fine in a camera and in several >>> different USB-based readers. On my sdhci reader (the integrated one >>> on a Lenovo X220), though, it spews stuff like: >>> >>> [ 306.103556] mmcblk0: error -110 sending read/write command, >>> response 0x0, card status 0x400b00 >>> [ 306.103559] end_request: I/O error, dev mmcblk0, sector 410272 >>> [ 306.103595] mmc0: Got data interrupt 0x00600000 even though no data >>> operation was in progress. >>> [ 306.103597] sdhci: =========== REGISTER DUMP (mmc0)=========== >>> [ 306.103602] sdhci: Sys addr: 0xf9253200 | Version: 0x00000502 >>> [ 306.103607] sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000001 >>> [ 306.103613] sdhci: Argument: 0x000642a1 | Trn mode: 0x00000013 >>> [ 306.103618] sdhci: Present: 0x01cf0000 | Host ctl: 0x00000003 >>> [ 306.103623] sdhci: Power: 0x0000000f | Blk gap: 0x00000000 >>> [ 306.103628] sdhci: Wake-up: 0x00000000 | Clock: 0x00000107 >>> [ 306.103634] sdhci: Timeout: 0x00000009 | Int stat: 0x00000000 >>> [ 306.103639] sdhci: Int enab: 0x02ff00cb | Sig enab: 0x02ff00cb >>> [ 306.103644] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000 >>> [ 306.103649] sdhci: Caps: 0x21e8c8b2 | Caps_1: 0x00008073 >>> [ 306.103654] sdhci: Cmd: 0x0000113a | Max curr: 0x00000040 >>> [ 306.103655] sdhci: =========================================== >>> >>> all over the logs and fails some (but not all) attempts to read it. >>> The startup messages are: >>> >>> [ 830.308403] sdhci-pci 0000:0d:00.0: SDHCI controller found >>> [1180:e823] (rev 4) >>> [ 830.308632] sdhci-pci 0000:0d:00.0: PCI INT A -> GSI 16 (level, >>> low) -> IRQ 16 >>> [ 830.308720] sdhci-pci 0000:0d:00.0: setting latency timer to 64 >>> [ 830.308730] mmc0: no vmmc regulator found >>> [ 830.308802] Registered led device: mmc0:: >>> [ 830.309059] mmc0: SDHCI controller on PCI [0000:0d:00.0] using DMA >>> >>> and lspci says: >>> >>> 0d:00.0 System peripheral: Ricoh Co Ltd Device e823 (rev 04) >>> >>> I see this on 2.6.39.1 and 3.0 git from today. >> >> Any idea whether this is present in previous kernels too? It'd be >> great if you can test a few earlier ones and find out whether we're >> looking at a regression or just new hardware to add quirks for.
2.6.37 doesn't recognize the reader, and if I add the PCI id via new_id, the driver fails with a different error. I'll post that in a bit. I tried a 2.6.38 Fedora 15 kernel but it didn't boot (dracut bug). I can fiddle with it and get a .38 kernel working if you like. > > Ah, could you try this patch, please? > > http://thread.gmane.org/gmane.linux.kernel.mmc/8254 > ("mmc: Enable MMC card reader for RICOH [1180:e823]") Doesn't help. Some tracing shows that the initial (BIOS-provided?) value of config byte 0xCB is 0x87. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
