From: Michael Orlitzky <michael@orlitzky.com>
To: Chen Wang <unicorn_wang@outlook.com>
Cc: sophgo@lists.linux.dev, Han Gao <rabenda.cn@gmail.com>,
Inochi Amaoto <inochiama@outlook.com>,
Han Gao <gaohan@iscas.ac.cn>
Subject: Re: SG2042 SATA (DMA?) issues
Date: Sun, 31 May 2026 22:22:40 -0400 [thread overview]
Message-ID: <ahzs8MSmNU7_vsIT@mertle> (raw)
In-Reply-To: <MA5PR01MB125002F8416D3FC82656A5262FE152@MA5PR01MB12500.INDPRD01.PROD.OUTLOOK.COM>
On 2026-06-01 08:31:21, Chen Wang wrote:
>
> Changes related to DMA can be referred to at
> https://lore.kernel.org/linux-riscv/20260331171248.973014-1-gaohan@iscas.ac.cn/
>
> Hi Michael,
>
> please confirm whether you have updated the firmware mentioned in the
> patch email. If there are still issues after updating the firmware, this
> patch may need to be reassessed.
Yes, I have git checkouts of
* edk2-non-osi.git
* edk2-platforms.git
* edk2.git
* opensbi.git
* zsbl.git
from github.com/sophgo and am using the sg2042-dev branch where
applicable. The problem occurs with fip.bin from,
commit b379b0674328be40c9811032193014195944c664
Author: Chao Wei <chao.wei@sophgo.com>
Date: Mon Mar 30 21:27:39 2026 +0800
SG2042/Boot: Update fip.bin
SG2042: Disable PCIe write reorder on single chip
which is one commit ahead of the one linked by Han Gao. All other
firmware components are at their most recent commits.
The SATA drives had been working for over a year without issue. The
first occurrence of the problem in my kernel logs is immediately after
a kernel/firmware update, so to confirm, I looked through the git logs
and reverted each firmware component to an earlier commit:
* SRA1-20.fd (20251209)
* fip.bin (20251209, from the bootloader-riscv repo)
* fw_dynamic.bin (20251106)
* zsbl.bin (20251215)
* mango-milkv-pioneer.dtb (20251215)
and of course, I reverted the kernel patch that adds dma-coherent to
the dts, and replaced sg2042-milkv-pioneer.dtb.
This seems to fix the problem: I mounted and unmounted, copied to and
from, both partions for a few minutes without error. (I get an
unrelated kernel panic in amdgpu_irq.c with this firmware/kernel, but
was able to test over SSH after removing the GPU).
next prev parent reply other threads:[~2026-06-01 2:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 4:32 SG2042 SATA (DMA?) issues Michael Orlitzky
2026-05-31 15:05 ` Michael Orlitzky
2026-06-01 0:31 ` Chen Wang
2026-06-01 2:22 ` Michael Orlitzky [this message]
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=ahzs8MSmNU7_vsIT@mertle \
--to=michael@orlitzky.com \
--cc=gaohan@iscas.ac.cn \
--cc=inochiama@outlook.com \
--cc=rabenda.cn@gmail.com \
--cc=sophgo@lists.linux.dev \
--cc=unicorn_wang@outlook.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.