On boot MMC error - no mmc?!?

suse_rasputin · June 10, 2019, 7:26pm

Hi again!

For some weeks now I have on a Dell Latitude notebook on boot the following message running through the screen:

    4.677492] ehci-pci 0000:00:1d.0: EHCI Host Controller
    4.677501] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
    4.677518] ehci-pci 0000:00:1d.0: debug port 2
    4.681452] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
    4.685085] mmc0: Internal clock never stabilised.
    4.685534] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
    4.686136] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x0000c001
    4.686737] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
    4.687339] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
    4.687947] mmc0: sdhci: Present:   0x01ff0000 | Host ctl: 0x00000000
    4.688490] ehci-pci 0000:00:1d.0: irq 17, io mem 0xe2d50000
    4.688538] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000000
    4.689130] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x00001003
    4.689720] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
    4.690310] mmc0: sdhci: Int enab:  0x00ff0083 | Sig enab: 0x00ff0083
    4.690903] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
    4.691486] mmc0: sdhci: Caps:      0x21e608b2 | Caps_1:   0x00002077
    4.692077] mmc0: sdhci: Cmd:       0x00000000 | Max curr: 0x00000064
    4.692658] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
    4.693238] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
    4.693812] mmc0: sdhci: Host ctl2: 0x00000000
    4.694207] mmc0: sdhci: ============================================
    4.703795] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
    4.704137] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.01
    4.704140] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    4.704142] usb usb2: Product: EHCI Host Controller
    4.704144] usb usb2: Manufacturer: Linux 5.1.7-1-default ehci_hcd
    4.704146] usb usb2: SerialNumber: 0000:00:1d.0
    4.704336] hub 2-0:1.0: USB hub found
    4.704350] hub 2-0:1.0: 2 ports detected
    4.712058] firewire_ohci 0000:09:00.0: added OHCI v1.10 device as card 0, 8 IR + 8 IT contexts, quirks 0x10
    4.754909] sr 1:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
    4.754912] cdrom: Uniform CD-ROM driver Revision: 3.20
    4.755343] sr 1:0:0:0: Attached scsi CD-ROM sr0
    4.758512] mmc0: Internal clock never stabilised.
    4.759011] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
    4.759603] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x0000c001
    4.760203] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
    4.760792] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
    4.761383] mmc0: sdhci: Present:   0x01ff0000 | Host ctl: 0x00000000
    4.761974] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000000
    4.762568] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x00001003
    4.763159] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
    4.763759] mmc0: sdhci: Int enab:  0x00ff0083 | Sig enab: 0x00ff0083
    4.764353] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
    4.764943] mmc0: sdhci: Caps:      0x21e608b2 | Caps_1:   0x00002077
    4.765524] mmc0: sdhci: Cmd:       0x00000000 | Max curr: 0x00000064
    4.766114] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
    4.766701] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
    4.767283] mmc0: sdhci: Host ctl2: 0x00000000
    4.767680] mmc0: sdhci: ============================================
    4.806118] checking generic (d0000000 410000) vs hw (d0000000 10000000)
    4.806120] fb0: switching to inteldrmfb from VESA VGA
    4.890884] mmc0: Internal clock never stabilised.
    4.890886] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
    4.890896] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x0000c001
    4.890902] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
    4.890908] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
    4.890914] mmc0: sdhci: Present:   0x01ff0000 | Host ctl: 0x00000000
    4.890921] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000000
    4.890927] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x00002003
    4.890933] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
    4.890940] mmc0: sdhci: Int enab:  0x00ff0083 | Sig enab: 0x00ff0083
    4.890946] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
    4.890952] mmc0: sdhci: Caps:      0x21e608b2 | Caps_1:   0x00002077
    4.890959] mmc0: sdhci: Cmd:       0x00000000 | Max curr: 0x00000064
    4.890965] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
    4.890971] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
    4.890975] mmc0: sdhci: Host ctl2: 0x00000000
    4.890976] mmc0: sdhci: ============================================
    4.943792] mmc0: Internal clock never stabilised.
    4.987885] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
    4.987901] mmc0: sdhci: Sys addr:  0x00000000 | Version:  0x0000c001
    4.987908] mmc0: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
    4.987914] mmc0: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
    4.987921] mmc0: sdhci: Present:   0x01ff0000 | Host ctl: 0x00000000
    4.987927] mmc0: sdhci: Power:     0x0000000f | Blk gap:  0x00000000
    4.987934] mmc0: sdhci: Wake-up:   0x00000000 | Clock:    0x00004003
    4.987940] mmc0: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
    4.987941] Console: switching to colour dummy device 80x25
    4.987947] mmc0: sdhci: Int enab:  0x00ff0083 | Sig enab: 0x00ff0083
    4.987953] mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
    4.987960] mmc0: sdhci: Caps:      0x21e608b2 | Caps_1:   0x00002077
    4.987968] mmc0: sdhci: Cmd:       0x00000000 | Max curr: 0x00000064
    4.987976] mmc0: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
    4.987982] mmc0: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
    4.987986] mmc0: sdhci: Host ctl2: 0x00000000
    4.987987] mmc0: sdhci: ============================================
    4.988517] i915 0000:00:02.0: vgaarb: deactivate vga console
    4.998596] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    4.998598] [drm] Driver supports precise vblank timestamp query.

The notebook has an old fashioned HDD, have no idea what mmc0 might be…

Any help on this?

PS: …the built-in SD-card reader maybe? But what does the error message mean?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523178

suse_rasputin · June 10, 2019, 7:37pm

Output of lspci

lspci
[sudo] password for root: 
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port Mobile SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
09:00.0 FireWire (IEEE 1394): O2 Micro, Inc. 1394 OHCI Compliant Host Controller (rev 05)
09:00.1 SD Host controller: O2 Micro, Inc. OZ600RJ0/OZ900RJ0/OZ600RJS SD/MMC Card Reader Controller (rev 05)
09:00.2 Mass storage controller: O2 Micro, Inc. O2 Flash Memory Card (rev 05)
usser@dell3:~> sudo lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port Mobile SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
09:00.0 FireWire (IEEE 1394): O2 Micro, Inc. 1394 OHCI Compliant Host Controller (rev 05)
09:00.1 SD Host controller: O2 Micro, Inc. OZ600RJ0/OZ900RJ0/OZ600RJS SD/MMC Card Reader Controller (rev 05)
09:00.2 Mass storage controller: O2 Micro, Inc. O2 Flash Memory Card (rev 05)

tsu2 · June 10, 2019, 7:57pm

A big guess…
Assuming that this error is being thrown very early in the boot process,

It might be addressable with a BIOS upgrade.
There might be a driver support issue. Recommend collecting info about your sdcard hardware and then doing a search whether is supported without problems by the Linux kernel.

Although you say this is a Dell laptop, you don’t identify its model or architecture, is it using an ARM processor? How old is this machine (If the BIOS hasn’t been updated, then the BIOS date is a good indicator date of manufacture)

TSU

suse_rasputin · June 10, 2019, 8:06pm

It’s an E6520, latest BIOS v. A22 dated JAN 2019

https://www.dell.com/support/home/se/sv/sebsdt1/drivers/driversdetails?driverid=6434j&oscode=ww1&productcode=latitude-e6520

is already installed…

malcolmlewis · June 11, 2019, 2:44am

On Mon 10 Jun 2019 05:36:03 PM CDT, suse rasputin wrote:

Hi again!

For some weeks now I have on a Dell Latitude notebook on boot the
following message running through the screen:
<snip>

PS: …the built-in SD-card reader maybe? But what does the error
message mean?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523178

Hi
Yes it will be the card reader, no card installed? Do you have one to
insert? it may be dirty contacts.

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
Tumbleweed 20190607 | GNOME Shell 3.32.2 | 5.1.7-1-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

suse_rasputin · June 11, 2019, 8:15am

Hi Malcolm! I have inserted an empty SD-to-µSD adapter instead of the plastic dummy (for years now…). You think this might be the problem? Replaced the adapter and will have a look if this helps on next boot…

suse_rasputin · June 11, 2019, 11:03am

OK, replacing the adapter with a fresh one did not help, but completely removing it resolved the issue, no longer these error in dmesg on boot. Strange…

malcolmlewis · June 11, 2019, 3:23pm

Hi
I would surmise a driver change that senses that a card is inserted or a quirk is needed…

So if you plug the blank in after boot, what is the output like?

If you enable quirks manually at next boot;


sdhci.debug_quirks=1 sdhci.debug_quirks2=1

Plug the card in and out after boot, do you get more info?

suse_rasputin · June 11, 2019, 5:28pm

Hello again!

Inserting the empty adapter after booting is completed results in same error messages as see during boot, but only for the FIRST time the adapter is inserted, not after inserting for the second or third time.
I added the sdhci.debug… stuff to the linux line in the boot loader, correct? After booting I added the adapter and get:

https://paste.opensuse.org/79392746

malcolmlewis · June 11, 2019, 5:46pm

Hi
I wonder if the contacts are just dusty/dirty? Perhaps some air in there, or if can get a lint free cloth with isopropyl alcohol to clean the contacts…

If that doesn’t help, then would suggest a bug report against the kernel and attach the error you see.

suse_rasputin · June 11, 2019, 7:19pm

How to clean the card reader inside? Never get to the contacts… The adapters (both I tried) are brand new (the ones you buy with every µSD-card…)

I never bugged any kernels errrr… raised any kernel bugs. How to do that?

malcolmlewis · June 11, 2019, 7:50pm

Hi
Just have a look here;
openSUSE:Submitting bug reports - openSUSE

Log against the kernel, post back the bug reference here

suse_rasputin · June 11, 2019, 9:38pm

In my experience with opensource software projects it is absolutely essential for a bug to be fixed to make it reproducible for the programmers. In my case I don’t see how any developer should be able to reproduce the issue on his own hardware. Or?

malcolmlewis · June 11, 2019, 11:44pm

Hi
You would be surprised at what they can work out with a little bit of information

I would add the error and the usb-devices info for the device, they will ask if more information is needed (maybe dmidecode info).