Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #84299

Bug#1085425: linux-image-6.10.12-riscv64: dwmmc_starfive causes filesystem corruption on emmc

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On 2024-10-19 23:08, Aurelien Jarno wrote:
> Hi,
> 
> On 2024-10-19 20:48, Jing Luo wrote:
>> Package: src:linux
>> Version: 6.10.12-1
>> Severity: critical
>> Tags: upstream
>> Justification: causes serious data loss
>> 
>> Hi,
>> 
>> The dwmmc_starfive module causes serious filesystem corruption when 
>> debian
>> is installed to emmc with linux-image-6.10.12-riscv64.
> 
> The dwmmc_starfive module is providing support for both emmc and
> sd-card. Are you also able to reproduce the issue with the sd-card?

I couldn't reproduce it with sd card: I still see kernel log spam by 
dwmmc_starfive, but the filesystem itself looks ok. The filesystem 
passed e2fsck and a debsums run.

>> The board in question
>> is Starfive Visionfive 2.
> 
> How much memory do you have on this board?

8GB.

>> The system tested on uses upstream u-boot and the
>> rootfs uses ext4. Please see the attached kernel log. The emmc was 
>> written
>> garbage even under light I/O.
> 
> What do you mean by upstream u-boot? The version in Debian or a newer
> version? Do you pass the kernel version of the device-tree to the
> bootloader?

Ah, that's a newer u-boot, 2024.10 I built using defconfig. I use 
u-boot-menu to generate the extlinux.conf so the kernel loads the device 
tree from /usr/lib/linux-image...

I tried debian's 2024.01 version of u-boot, but I'm afraid that the 
result was the same.

>> Also: the vendor kernel doesn't have this issue. The latest 6.11.2-1 
>> is not
>> tested yet because I could not get it to boot (another bug?).
> 
> This version does work on a VisionFive 2 board, admittedly I haven't
> tested the emmc part. Could you please provide more version on the
> issue, as kernel 6.10.12-1 is basically unsupported?

I finally and unfortunately reproduced this with 6.11.2-1.

Another thing I noticed: the filesystem corruption has a pattern (sort 
of),
it looks like this with /var/lib/dpkg/status:

PPacaage  apaarmrr
Saatu:: isstall ok installed
Priority: optional
Section: admin
Inttaleed-iize  2333
Miintiine:: Dbbia  ApAArmrr Taam 
ppkgaapprrmo--temm@lsstsaalitth.eebinn.ogg>
rrchttecuure  riccv6

Sorrce  apaarmrr (..1.--1)VVeriion  3...7-++b1RRepaace:: fiitxddat  (<  
1:..2..

Deeend:: dbbcoff, eebcnnf >>= ..5)|| dbbcoff-200, iibc  (>  2.88)
uuggssts  apaarmrr-poofiees-xxtr,, apparoor-ttil

Braaks  apaarmrr-poofiees-xxtr  (<  1.11),ffcixx-dtta <<< 
::4...9.--1uuunt22),s

Cofffiees:  /ecc/apparoor.//abi/3.0 f97e410509c5def279aa227c7de12e06
  
/etc/apparmo..d/bbi/eernll-544-ottofrreennetoork557b88ac44e6118f55a0ddc8004733

  /ttc/pppammordd/aii/krrne--5.--vaiill  77447eff0b114f88bf77689998882044
  eetcaapprrmo..d/bbstaactoonsXX e88b3665c668c99b5222d11dbddf0992


And I couldn't chroot into the rootfs because it fails to run /bin/bash:

$ ldd /mnt/bin/bash
         linux-vdso.so.1 (0x0000003f8a5e4000)
         lbbtiffo.oo.6llib..so66 => not found
         lib..so66 => not found
         l--liuux-iisc664-pp64..so11 => not found

Oh well.

-- 
Jing Luo
About me: https://jing.rocks/about/
GPG Fingerprint: 4E09 8D19 00AA 3F72 1899 2614 09B3 316E 13A1 1EFC

Back to linux.debian.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Bug#1085425: linux-image-6.10.12-riscv64: dwmmc_starfive causes filesystem corruption on emmc Jing Luo <jing@jing.rocks> - 2024-10-19 19:10 +0200
  Bug#1085425: linux-image-6.10.12-riscv64: dwmmc_starfive causes filesystem corruption on emmc Jing Luo <jing@jing.rocks> - 2024-10-20 17:00 +0200

csiph-web