From: Michael Orlitzky <michael@orlitzky.com>
To: sophgo@lists.linux.dev
Subject: Re: SG2042 SATA (DMA?) issues
Date: Sun, 31 May 2026 11:05:20 -0400 [thread overview]
Message-ID: <ahxOMJqJTqKfY9SI@mertle> (raw)
In-Reply-To: <ahu57vcS0oOFmCI9@mertle>
On 2026-05-31 00:32:46, Michael Orlitzky wrote:
> Has anyone tried the recent SG2042 firmware and DMA coherence
> patches with the onboard SATA? ... 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.
Just to confirm, downgrading the firmware (zsbl, edk2, fip.bin) to
snapshots from December 2025 and reverting the dma-coherent dts
changes (e728a57834d) does fix the issue. It looks like something may
be seriously wrong, be careful if you have anything important on a
SATA drive.
next prev parent reply other threads:[~2026-05-31 15:05 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 [this message]
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=ahxOMJqJTqKfY9SI@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