sdhci Module is causing errors: "mmc0: Timeout waiting for hardware cmd interrupt - how to stop loading the module or resolving the issue

MaMo

New Member
Oct 11, 2023
2
0
1
Dear community,

I did come across this issue with the sdhci modules during a new installation.
Seems an internal SD Card Reader (which is not in use and will not be used) is causing this errors. See log file entry below.

The issue as such is "documented" a temporary fix to close the modules by submitting "modprobe -r sdhci_acpi" and "modprobe -r sdhci" is working fine. Sofar also creating no unstable environment or other issues.
The suggested permanent fix (blacklist sdhci, ..)do blacklist the two modules in /etc/modprobe.d/blacklist doesn't so anything. I did als try to enter this into pve-blacklist.config or blacklist.conf with no effect.

Is there any solution for this out there?

Proxmox VE8.0
x86 Environment

Many thanks
M

Oct 11 10:50:37 pve kernel: mmc0: Timeout waiting for hardware cmd interrupt.
Oct 11 10:50:37 pve kernel: mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
Oct 11 10:50:37 pve kernel: mmc0: sdhci: Sys addr: 0x00000000 | Version: 0x0000a402
Oct 11 10:50:37 pve kernel: mmc0: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000
Oct 11 10:50:37 pve kernel: mmc0: sdhci: Argument: 0x00000000 | Trn mode: 0x00000000
Oct 11 10:50:37 pve kernel: mmc0: sdhci: Present: 0x01ff0001 | Host ctl: 0x00000000
Oct 11 10:50:37 pve kernel: mmc0: sdhci: Power: 0x0000000f | Blk gap: 0x00000000
Oct 11 10:50:37 pve kernel: mmc0: sdhci: Wake-up: 0x00000000 | Clock: 0x0000f447
Oct 11 10:50:37 pve kernel: mmc0: sdhci: Timeout: 0x00000000 | Int stat: 0x00018000
Oct 11 10:50:37 pve kernel: mmc0: sdhci: Int enab: 0x00ff0003 | Sig enab: 0x00ff0003
Oct 11 10:50:37 pve kernel: mmc0: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000001
Oct 11 10:50:37 pve kernel: mmc0: sdhci: Caps: 0x67ea64b2 | Caps_1: 0x00000000
Oct 11 10:50:37 pve kernel: mmc0: sdhci: Cmd: 0x00000502 | Max curr: 0x00000001
Oct 11 10:50:37 pve kernel: mmc0: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000
Oct 11 10:50:37 pve kernel: mmc0: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000
Oct 11 10:50:37 pve kernel: mmc0: sdhci: Host ctl2: 0x00000000
Oct 11 10:50:37 pve kernel: mmc0: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000
Oct 11 10:50:37 pve kernel: mmc0: sdhci: ============================================
 
found out myself, this step was missing:

sudo update-initramfs -u

maybe this is helping somebody else.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!