From: Michael Orlitzky <michael@orlitzky.com>
To: sophgo@lists.linux.dev
Subject: SG2042 SATA (DMA?) issues
Date: Sun, 31 May 2026 00:32:46 -0400 [thread overview]
Message-ID: <ahu57vcS0oOFmCI9@mertle> (raw)
Has anyone tried the recent SG2042 firmware and DMA coherence patches
with the onboard SATA? I am currently in the process of learning an
important lesson and wish I weren't. After a recent update, any ext4
filesystem that I put on a SATA drive quickly becomes corrupt. For
example,
EXT4-fs (sda1): mounted filesystem 54f42dce-97ef-4b4d-8a92-dab5d72a527b r/w with ordered data mode. Quota mode: disabled.
EXT4-fs error (device sda1): ext4_validate_block_bitmap:423: comm ext4lazyinit: bg 103: bad block bitmap checksum
EXT4-fs error (device sda1): ext4_validate_block_bitmap:423: comm ext4lazyinit: bg 255: bad block bitmap checksum
EXT4-fs error (device sda1): ext4_validate_block_bitmap:423: comm ext4lazyinit: bg 350: bad block bitmap checksum
EXT4-fs error (device sda1): ext4_validate_block_bitmap:423: comm ext4lazyinit: bg 886: bad block bitmap checksum
...
Here's a different error, from a different drive:
EXT4-fs (sdb1): ext4_check_descriptors: Block bitmap for group 109 overlaps superblock
EXT4-fs (sdb1): group descriptors corrupted!
These are two new drives, fresh out of the box. Running fsck doesn't
help -- the corruption returns almost immediately. Similarly after a
reformat.
I am testing with linux-next-20260529, and the following patches from
the mailing list. OpenSBI, zsbl, EDK2, and fip.bin are all up-to-date.
commit fe7d4d1c81361d02c8156c3989b8b07edebf96bf
Author: Vivian Wang <wangruikang@iscas.ac.cn>
Date: Mon Mar 9 19:09:38 2026 +0800
riscv: mm: Define DIRECT_MAP_PHYSMEM_END
commit 8e12c1f0ee16bd901df098d5133a2041a3f5383a
Author: Guo Ren (Alibaba DAMO Academy) <guoren@kernel.org>
Date: Tue Apr 21 10:31:40 2026 -0400
riscv: errata: Add ERRATA_THEAD_WRITE_ONCE fixup
commit d2c0c75176d2c220b7c13ae1dc2ca029d99f42fe
Author: Inochi Amaoto <inochiama@gmail.com>
Date: Tue Apr 7 07:26:55 2026 +0800
riscv: dts: sophgo: sg2042: use hex for CPU unit address
commit f582c404b9e034efa5891db6a5a0751a7488659c
Author: Han Gao <gaohan@iscas.ac.cn>
Date: Wed Apr 1 01:56:58 2026 +0800
PCI: Add quirk to disable PCIe port services on Sophgo SG2042
commit 6b2339e1faf20f8e819f729fd0b8b94a0169e6d2
Author: Han Gao <gaohan@iscas.ac.cn>
Date: Wed Apr 1 01:56:57 2026 +0800
PCI: Add per-device flag to disable native PCIe port services
commit 7e9fc0eb8ecdc96d31af68920b55f1885683ec88
Author: Icenowy Zheng <zhengxingda@iscas.ac.cn>
Date: Wed Apr 8 00:01:43 2026 +0800
riscv: dts: sophgo: reduce SG2042 MSI count to 16
next reply other threads:[~2026-05-31 4:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 4:32 Michael Orlitzky [this message]
2026-05-31 15:05 ` SG2042 SATA (DMA?) issues Michael Orlitzky
2026-06-01 0:31 ` Chen Wang
2026-06-01 2:22 ` Michael Orlitzky
2026-06-01 6:06 ` Chen Wang
2026-06-01 6:47 ` Michael Orlitzky
2026-06-01 8:00 ` Chen Wang
2026-06-01 8:12 ` Michael Orlitzky
2026-06-02 12:19 ` Han Gao
2026-06-02 19:20 ` Michael Orlitzky
2026-06-03 9:14 ` Niklas Cassel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ahu57vcS0oOFmCI9@mertle \
--to=michael@orlitzky.com \
--cc=sophgo@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox