Created attachment 1663908 [details]
dmesg of any kernel outputs the same timeout

1. Please describe the problem:
Built-in SD reader does not work
dmesg is flooded with timeouts (no matter if a card is inserted)

2. What is the Version-Release number of the kernel:
Probably any 5.x kernel, maybe even below

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
Sorry, can't remember if it worked years ago (but it's working in Windows)

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Every time. dmesg contains repeatedly:

[  +0,000001] mmc1: sdhci: ============================================
[ +10,240071] mmc1: Timeout waiting for hardware cmd interrupt.
[  +0,000005] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[  +0,000007] mmc1: sdhci: Sys addr:  0x00000000 | Version:  0x0000a402
[  +0,000004] mmc1: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[  +0,000004] mmc1: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[  +0,000004] mmc1: sdhci: Present:   0x01ff0001 | Host ctl: 0x00000000
[  +0,000004] mmc1: sdhci: Power:     0x0000000f | Blk gap:  0x00000000
[  +0,000004] mmc1: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[  +0,000005] mmc1: sdhci: Timeout:   0x00000000 | Int stat: 0x00018000
[  +0,000004] mmc1: sdhci: Int enab:  0x00ff0003 | Sig enab: 0x00ff0003
[  +0,000004] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000001
[  +0,000005] mmc1: sdhci: Caps:      0x67ea64b2 | Caps_1:   0x00000000
[  +0,000004] mmc1: sdhci: Cmd:       0x0000371a | Max curr: 0x00000001
[  +0,000004] mmc1: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[  +0,000005] mmc1: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[  +0,000003] mmc1: sdhci: Host ctl2: 0x00000000
[  +0,000004] mmc1: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Yes

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.