Hello,
I had two issues but I was using RPMFusion's Fedora image (they use Raspberry downstream kernel, not Fedora one).
https://rpmfusion.org/Howto/RaspberryPi
uname -a: Linux xyserver5.lan 6.6.58-1.rpi4.fc41.aarch64 #1 SMP PREEMPT Wed Oct 23 16:00:13 UTC 2024 aarch64 GNU/Linux
First,
SanDisk Extreme Pro 64G
This happened during SELinux autorelabel or right after, during system reboot.Card details:Second,
Samsung Pro Plus 128G
A new line of "mmc0: running CQE recovery" was appearing every few seconds in dmesg.
I checked and this https://github.com/raspberrypi/linux/co ... 6494e6f0bb commit is indeed present in that kernel. This quirk only applies to cards made in 2023. Mine was made in 2024.
However the strange thing is when I used Raspberry Pi OS (upgraded to latest versions in a Pi 3) this issue was not present...
Card details:
I had two issues but I was using RPMFusion's Fedora image (they use Raspberry downstream kernel, not Fedora one).
https://rpmfusion.org/Howto/RaspberryPi
uname -a: Linux xyserver5.lan 6.6.58-1.rpi4.fc41.aarch64 #1 SMP PREEMPT Wed Oct 23 16:00:13 UTC 2024 aarch64 GNU/Linux
First,
SanDisk Extreme Pro 64G
This happened during SELinux autorelabel or right after, during system reboot.
Code:
Nov 12 15:52:32 xyserver5.lan kernel: mmc0: cqhci: timeout for tag 4, qcnt 2Nov 12 15:52:32 xyserver5.lan kernel: mmc0: cqhci: ============ CQHCI REGISTER DUMP ===========Nov 12 15:52:32 xyserver5.lan kernel: mmc0: cqhci: Caps: 0x000030c8 | Version: 0x00000510Nov 12 15:52:32 xyserver5.lan kernel: mmc0: cqhci: Config: 0x00000101 | Control: 0x00000000Nov 12 15:52:32 xyserver5.lan kernel: mmc0: cqhci: Int stat: 0x00000000 | Int enab: 0x00000016Nov 12 15:52:32 xyserver5.lan kernel: mmc0: cqhci: Int sig: 0x00000016 | Int Coal: 0x00000000Nov 12 15:52:32 xyserver5.lan kernel: mmc0: cqhci: TDL base: 0x06784000 | TDL up32: 0x00000000Nov 12 15:52:32 xyserver5.lan kernel: mmc0: cqhci: Doorbell: 0x00000030 | TCN: 0x00000000Nov 12 15:52:32 xyserver5.lan kernel: mmc0: cqhci: Dev queue: 0x00000000 | Dev Pend: 0x00000030Nov 12 15:52:32 xyserver5.lan kernel: mmc0: cqhci: Task clr: 0x00000000 | SSC1: 0x00004000Nov 12 15:52:32 xyserver5.lan kernel: mmc0: cqhci: SSC2: 0x0000aaaa | DCMD rsp: 0x00000000Nov 12 15:52:32 xyserver5.lan kernel: mmc0: cqhci: RED mask: 0xfdf9a080 | TERRI: 0x00000000Nov 12 15:52:32 xyserver5.lan kernel: mmc0: cqhci: Resp idx: 0x0000000d | Resp arg: 0x00000000Nov 12 15:52:32 xyserver5.lan kernel: mmc0: running CQE recoveryCode:
/sys/block/mmcblk0/device/cid:035344535236344786d3cf1852017700/sys/block/mmcblk0/device/csd:400e0032db790001dbd37f800a404000/sys/block/mmcblk0/device/date:07/2023/sys/block/mmcblk0/device/dsr:0x404/sys/block/mmcblk0/device/erase_size:512/sys/block/mmcblk0/device/ext_perf:18/sys/block/mmcblk0/device/ext_power:07/sys/block/mmcblk0/device/fwrev:0x6/sys/block/mmcblk0/device/hwrev:0x8/sys/block/mmcblk0/device/manfid:0x000003/sys/block/mmcblk0/device/name:SR64G/sys/block/mmcblk0/device/ocr:0x00300000/sys/block/mmcblk0/device/oemid:0x5344/sys/block/mmcblk0/device/preferred_erase_size:4194304/sys/block/mmcblk0/device/rca:0xaaaa/sys/block/mmcblk0/device/removable:removable/sys/block/mmcblk0/device/scr:0245848700000000/sys/block/mmcblk0/device/serial:0xd3cf1852/sys/block/mmcblk0/device/ssr:0000000008000000040090000f05391e000800000002fc0003000000000000000000000000000000000000000000000000000000000000000000000000000000/sys/block/mmcblk0/device/type:SD/sys/block/mmcblk0/device/uevent:DRIVER=mmcblk/sys/block/mmcblk0/device/uevent:MMC_TYPE=SD/sys/block/mmcblk0/device/uevent:MMC_NAME=SR64G/sys/block/mmcblk0/device/uevent:MODALIAS=mmc:blockSamsung Pro Plus 128G
A new line of "mmc0: running CQE recovery" was appearing every few seconds in dmesg.
I checked and this https://github.com/raspberrypi/linux/co ... 6494e6f0bb commit is indeed present in that kernel. This quirk only applies to cards made in 2023. Mine was made in 2024.
However the strange thing is when I used Raspberry Pi OS (upgraded to latest versions in a Pi 3) this issue was not present...
Card details:
Code:
root@localhost:~# grep . /sys/block/mmcblk0/device/* 2>/dev/null /sys/block/mmcblk0/device/cid:1b534d4644345139309478628aa18527/sys/block/mmcblk0/device/csd:400e0032db790003baff7f800a40002d/sys/block/mmcblk0/device/date:05/2024/sys/block/mmcblk0/device/dsr:0x404/sys/block/mmcblk0/device/erase_size:512/sys/block/mmcblk0/device/fwrev:0x0/sys/block/mmcblk0/device/hwrev:0x3/sys/block/mmcblk0/device/manfid:0x00001b/sys/block/mmcblk0/device/name:FD4Q9/sys/block/mmcblk0/device/ocr:0x00300000/sys/block/mmcblk0/device/oemid:0x534d/sys/block/mmcblk0/device/preferred_erase_size:4194304/sys/block/mmcblk0/device/rca:0x0001/sys/block/mmcblk0/device/removable:removable/sys/block/mmcblk0/device/scr:0205848700000000/sys/block/mmcblk0/device/serial:0x9478628a/sys/block/mmcblk0/device/ssr:0000000008000000040090000811391e000800000002ff0003000000000000000000000000000000000000000000000000000000000000000000000000000000/sys/block/mmcblk0/device/type:SD/sys/block/mmcblk0/device/uevent:DRIVER=mmcblk/sys/block/mmcblk0/device/uevent:MMC_TYPE=SD/sys/block/mmcblk0/device/uevent:MMC_NAME=FD4Q9/sys/block/mmcblk0/device/uevent:MODALIAS=mmc:blockStatistics: Posted by xypista — Tue Nov 12, 2024 3:41 pm
