mmc0: error -110 whilst initialising SD card

[Frédéric]

Hi,

When I plug my new 64Gb SDXC card, I get this in dmesg:

mmc0: error -110 whilst initialising SD card

I have fuse, fuse-exfat and exfat-utils installed. I am using F28 on x86_64.

Works well with 8Gb SDHC.

Thanks,

F

[Samuel Sieb]

On 10/15/18 5:02 AM, Frédéric wrote:
>  When I plug my new 64Gb SDXC card, I get this in dmesg:
>  
>  mmc0: error -110 whilst initialising SD card 
Are there any other messages around that?

>  I have fuse, fuse-exfat and exfat-utils installed. I am using F28 on
> x86_64. 
Those packages are irrelevant as it hasn't got to that point yet.  Make 
sure you have the latest kernel.

>  Works well with 8Gb SDHC. 
Do you have anything else you can try the card in?

[Frédéric]

>  > mmc0: error -110 whilst initialising SD card
>  Are there any other messages around that? 
nothing else

>  > Works well with 8Gb SDHC.
>  Do you have anything else you can try the card in? 
well, it is strange because it works on an older computer with the same F28.
On this other computer, this is what I get:
[  172.702897] mmc0: new SDXC card at address aaaa
[  172.727538] mmcblk0: mmc0:aaaa SN64G 59.5 GiB
[  172.729685]  mmcblk0: p1

>  Make sure you have the latest kernel. 
I am now using the latest kernel 4.18.13-200.

F

[Samuel Sieb]

On 10/16/18 12:19 AM, Frédéric wrote:
>  well, it is strange because it works on an older computer with the
> same F28.
>  On this other computer, this is what I get:
>  [  172.702897] mmc0: new SDXC card at address aaaa
>  [  172.727538] mmcblk0: mmc0:aaaa SN64G 59.5 GiB
>  [  172.729685]  mmcblk0: p1 
That suggests that it might be a reader or driver problem.  Check the 
output of lspci to see what your SD reader device is.  Also check 
"journalctl -b" to check for initialization messages.  Searching for mmc 
should find the right area.

[Frédéric]

>  > [  172.702897] mmc0: new SDXC card at address aaaa
>  > [  172.727538] mmcblk0: mmc0:aaaa SN64G 59.5 GiB
>  > [  172.729685]  mmcblk0: p1
>
>  That suggests that it might be a reader or driver problem. 
I check the doc and it should really read SDXC.

>   Check the output of lspci to see what your SD reader device is.
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
RTS525A PCI Express Card Reader (rev 01)

>   Also check "journalctl -b" to check for initialization
> messages.  Searching for mmc
>  should find the right area. 
Oct 16 17:58:45 alpha kernel: mmc0: cannot verify signal voltage switch
Oct 16 17:58:46 alpha kernel: mmc0: error -110 whilst initialising SD card
Oct 16 17:58:47 alpha kernel: mmc0: cannot verify signal voltage switch
Oct 16 17:58:47 alpha kernel: mmc0: error -110 whilst initialising SD card
Oct 16 17:58:48 alpha kernel: mmc0: cannot verify signal voltage switch
Oct 16 17:58:48 alpha kernel: mmc0: error -110 whilst initialising SD card


That's all about it...

Kind regards,

F

[Samuel Sieb]

On 10/16/18 9:04 AM, Frédéric wrote:
> >   Check the output of lspci to see what your SD reader device
> is.
>  
>  03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
>  RTS525A PCI Express Card Reader (rev 01) 
Looking around, this device seems to have issues under Linux with people 
reporting the same symptoms that you are getting.  I would suggest 
filing an upstream kernel bug report.

> >   Also check "journalctl -b" to check for
> initialization messages.  Searching for mmc
> > should find the right area.
>  
>  Oct 16 17:58:45 alpha kernel: mmc0: cannot verify signal voltage switch
>  Oct 16 17:58:46 alpha kernel: mmc0: error -110 whilst initialising SD card
>  Oct 16 17:58:47 alpha kernel: mmc0: cannot verify signal voltage switch
>  Oct 16 17:58:47 alpha kernel: mmc0: error -110 whilst initialising SD card
>  Oct 16 17:58:48 alpha kernel: mmc0: cannot verify signal voltage switch
>  Oct 16 17:58:48 alpha kernel: mmc0: error -110 whilst initialising SD card 
I didn't mean to grep for it.  I meant that while you were running 
"journalctl -b", you can search for that text and somewhere around it 
should be the initialization messages.  Try searching for RTS525A as 
well or just scan through all the messages and see if you can find anything.

For example, this is what my log shows:
Oct 03 06:22:56 kernel: sdhci: Secure Digital Host Controller Interface 
driver
Oct 03 06:22:56 kernel: sdhci: Copyright(c) Pierre Ossman
Oct 03 06:22:56 kernel: sdhci-pci 0000:23:00.1: SDHCI controller found 
[197b:2392] (rev 30)
Oct 03 06:22:56 kernel: sdhci-pci 0000:23:00.1: enabling device (0000 -> 
0002)
Oct 03 06:22:56 kernel: mmc0 bounce up to 128 segments into one, max 
segment size 65536 bytes
Oct 03 06:22:56 kernel: mmc0: SDHCI controller on PCI [0000:23:00.1] 
using DMA
Oct 03 06:22:56 kernel: sdhci-pci 0000:23:00.2: SDHCI controller found 
[197b:2391] (rev 30)
Oct 03 06:22:56 kernel: sdhci-pci 0000:23:00.2: Refusing to bind to 
secondary interface.

[Frédéric]

>  > Oct 16 17:58:48 alpha kernel: mmc0: error -110 whilst
> initialising SD card
>
>  I didn't mean to grep for it.  I meant that while you were running
>  "journalctl -b", you can search for that text and somewhere around it
>  should be the initialization messages.  Try searching for RTS525A as
>  well or just scan through all the messages and see if you can find anything. 
but there is really nothing else in the log.

However, if I try with another SDXC card (older), it works and I get this:
oct. 16 20:13:06 alpha kernel: mmc0: cannot verify signal voltage switch
oct. 16 20:13:06 alpha kernel: mmc0: new ultra high speed SDR104 SDXC
card at address e624
oct. 16 20:13:06 alpha kernel: mmcblk0: mmc0:e624 SU64G 59.5 GiB
oct. 16 20:13:06 alpha kernel:  mmcblk0: p1

Does that help?

F

[Samuel Sieb]

On 10/16/18 11:42 AM, Frédéric wrote:
>  but there is really nothing else in the log. 
Strange that there is no initialization message for the reader.

>  However, if I try with another SDXC card (older), it works and I get
> this:
>  oct. 16 20:13:06 alpha kernel: mmc0: cannot verify signal voltage switch
>  oct. 16 20:13:06 alpha kernel: mmc0: new ultra high speed SDR104 SDXC
>  card at address e624
>  oct. 16 20:13:06 alpha kernel: mmcblk0: mmc0:e624 SU64G 59.5 GiB
>  oct. 16 20:13:06 alpha kernel:  mmcblk0: p1
>  
>  Does that help? 
Do you have windows on that laptop?  That would narrow the problem down 
to whether it is the hardware and the card or if it's a driver issue. 
Other than that, you could try filing a kernel bug.  That's all I can 
suggest.

[Frédéric]

>  Do you have windows on that laptop?  That would narrow the problem
> down
>  to whether it is the hardware and the card 
well, the card works well on an older PC with F28 and on my Android phone...

>  Other than that, you could try filing a kernel bug.  That's all I
> can
>  suggest. 
thanks,

F

[Samuel Sieb]

On 10/16/18 12:21 PM, Frédéric wrote:
> > Do you have windows on that laptop?  That would narrow the
> problem down
> > to whether it is the hardware and the card
>  
>  well, the card works well on an older PC with F28 and on my Android phone... 
Sure, but they have different reader hardware.

[Frédéric]

>  Other than that, you could try filing a kernel bug. 
done: https://bugzilla.kernel.org/show_bug.cgi?id=201447

Regards,

F