eMMC problems with Rock4 C+

Hello,
I've installed an emmc module on my Rock4 C+ card, with a DietPi OS image, which is running OK.... well, nearly OK - Today, I tried to run firefox, and got a "firefox crashed" error (which is not unusual with firefox), and I couldn't run firefox. I rebooted the OS, but then I got an error etlling me to run efsck on the emmc. I did and it booted OK after corrections have been applied - But still, no firefox -
I ran an update, and upgrade, which returned an error in unzipping firefox update ! 
OK, I uninstalled firefox, reinstalled it, and it runs OK - Anyway, a dmesg command returns this and a series of me

ssages like these ones :

[  195.048869] ------------[ cut here ]------------
[  195.048882] mmc1: cqhci: spurious TCN for tag 7
[  195.049030] WARNING: CPU: 0 PID: 281 at drivers/mmc/host/cqhci-core.c:787 cqhci_irq+0x4b4/0x640
[  195.049078] Modules linked in: snd_soc_hdmi_codec snd_soc_simple_card snd_soc_simple_card_utils snd_soc_rk817 dw_hdmi_cec dw_hdmi_i2s_audio btsdio bluetooth hantro_vpu(C) rockchip_vdec(C) brcmfmac rockchip_rga rockchip_iep v4l2_h264 brcmutil snd_soc_core videobuf2_dma_contig videobuf2_dma_sg snd_pcm_dmaengine v4l2_mem2mem videobuf2_vmalloc videobuf2_memops snd_pcm videobuf2_v4l2 snd_timer cfg80211 snd soundcore videobuf2_common videodev mc rfkill cpufreq_dt ip_tables x_tables autofs4 realtek dwmac_rk stmmac_platform stmmac pcs_xpcs
[  195.049478] CPU: 0 PID: 281 Comm: kworker/0:1H Tainted: G         C        5.15.93-rockchip64 #23.02.2
[  195.049502] Hardware name: Radxa ROCK Pi 4C+ (DT)
[  195.049517] Workqueue: kblockd blk_mq_run_work_fn
[  195.049552] pstate: 800000c5 (Nzcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[  195.049576] pc : cqhci_irq+0x4b4/0x640
[  195.049601] lr : cqhci_irq+0x4b4/0x640
[  195.049623] sp : ffff800008003d10
[  195.049634] x29: ffff800008003d10 x28: ffff000000fa49c0 x27: ffff000000633580
[  195.049675] x26: ffff00000070b698 x25: ffff80000952c010 x24: ffff800009d07710
[  195.049714] x23: ffff8000095504a8 x22: 0000000000000002 x21: ffff000000633000
[  195.049752] x20: 0000000000000007 x19: ffff00000070b680 x18: 0000000000000001
[  195.049790] x17: ffff8000edfe8000 x16: ffff800008004000 x15: 0000000000000249
[  195.049829] x14: ffff800008003a20 x13: 00000000ffffffea x12: ffff800009b2fe58
[  195.049868] x11: 0000000000000003 x10: ffff800009b17e18 x9 : ffff800009b17e70
[  195.049907] x8 : 0000000000017fe8 x7 : c0000000ffffefff x6 : 0000000000000001
[  195.049944] x5 : ffff8000edfe8000 x4 : 0000000000000000 x3 : 0000000000010004
[  195.049982] x2 : 0000000000010003 x1 : 3f965b3718a37200 x0 : 0000000000000000
[  195.050021] Call trace:
[  195.050032]  cqhci_irq+0x4b4/0x640
[  195.050057]  sdhci_arasan_cqhci_irq+0x5c/0x88
[  195.050081]  sdhci_irq+0xcc/0x1030
[  195.050108]  __handle_irq_event_percpu+0x60/0x258
[  195.050137]  handle_irq_event_percpu+0x38/0x88
[  195.050162]  handle_irq_event+0x48/0x98
[  195.050186]  handle_fasteoi_irq+0xb8/0x148
[  195.050208]  handle_domain_irq+0x90/0xd8
[  195.050232]  gic_handle_irq+0xb8/0x134
[  195.050254]  call_on_irq_stack+0x28/0x50
[  195.050279]  do_interrupt_handler+0x58/0x68
[  195.050302]  el1_interrupt+0x30/0x78
[  195.050323]  el1h_64_irq_handler+0x18/0x28
[  195.050344]  el1h_64_irq+0x74/0x78
[  195.050363]  preempt_count_sub+0x18/0xc0
[  195.050388]  _raw_spin_unlock_irqrestore+0x20/0x40
[  195.050416]  sdhci_cqe_enable+0x130/0x228
[  195.050442]  sdhci_arasan_cqe_enable+0x94/0xb8
[  195.050466]  cqhci_request+0xd0/0x650
[  195.050489]  mmc_cqe_start_req+0xb4/0x198
[  195.050515]  mmc_blk_mq_issue_rq+0x49c/0x868
[  195.050538]  mmc_mq_queue_rq+0x114/0x2b0
[  195.050559]  blk_mq_dispatch_rq_list+0x124/0x8b0
[  195.050587]  __blk_mq_sched_dispatch_requests+0xc4/0x1d8
[  195.050608]  blk_mq_sched_dispatch_requests+0x3c/0x78
[  195.050629]  __blk_mq_run_hw_queue+0x64/0xa0
[  195.050651]  blk_mq_run_work_fn+0x20/0x30
[  195.050673]  process_one_work+0x20c/0x4e8
[  195.050699]  worker_thread+0x48/0x498
[  195.050722]  kthread+0x138/0x150
[  195.050744]  ret_from_fork+0x10/0x20
[  195.050768] ---[ end trace 

[  344.530483] mmc1: running CQE recovery
[  344.783580] mmc1: running CQE recovery
[  344.789425] mmc1: running CQE recovery
[  344.794499] mmc1: running CQE recovery
[  344.794953] blk_update_request: I/O error, dev mmcblk1, sector 7635968 op 0x1:(WRITE) flags 0x800 phys_seg 82 prio class 0
[  344.795010] EXT4-fs warning (device mmcblk1p1): ext4_end_bio:348: I/O error 10 writing to inode 3940 starting block 954615)
[  344.795141] Buffer I/O error on device mmcblk1p1, logical block 950400
[  344.795201] Buffer I/O error on device mmcblk1p1, logical block 950401
[  344.795227] Buffer I/O error on device mmcblk1p1, logical block 950402
[  344.795256] Buffer I/O error on device mmcblk1p1, logical block 950403
[  344.795284] Buffer I/O error on device mmcblk1p1, logical block 950404
[  344.795310] Buffer I/O error on device mmcblk1p1, logical block 950405
[  344.795336] Buffer I/O error on device mmcblk1p1, logical block 950406
[  344.795362] Buffer I/O error on device mmcblk1p1, logical block 950407
[  344.795388] Buffer I/O error on device mmcblk1p1, logical block 950408
[  344.795415] Buffer I/O error on device mmcblk1p1, logical block 950409
[  427.310114] mmc1: running CQE recovery
[  427.316018] mmc1: running CQE recovery
[  466.650771] mmc1: running CQE recovery
[  466.657321] mmc1: running CQE recovery
[  466.700042] mmc1: running CQE recovery

I didn't notice that while I ran the same DietPi image on the SD card - 
Does anybody know if these are common problems with eMMC modules ? 
Thanks a lot,

JF