[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250128074133.GA22435@lst.de>
Date: Tue, 28 Jan 2025 08:41:33 +0100
From: Christoph Hellwig <hch@....de>
To: Thorsten Leemhuis <linux@...mhuis.info>
Cc: Mario Limonciello <mario.limonciello@....com>,
Bruno Gravato <bgravato@...il.com>, Stefan <linux-kernel@...g.de>,
Keith Busch <kbusch@...nel.org>, bugzilla-daemon@...nel.org,
Adrian Huang <ahuang12@...ovo.com>,
Linux kernel regressions list <regressions@...ts.linux.dev>,
linux-nvme@...ts.infradead.org, Jens Axboe <axboe@...com>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
LKML <linux-kernel@...r.kernel.org>, Christoph Hellwig <hch@....de>
Subject: Re: [Bug 219609] File corruptions on SSD in 1st M.2 socket of
AsRock X600M-STX + Ryzen 8700G
On Mon, Jan 20, 2025 at 03:31:28PM +0100, Thorsten Leemhuis wrote:
> My former colleague Christian Hirsch (not CCed) can reproduce the
> problem reliably. He today switched the CPU to a Ryzen 7 7700 and later
> to some Ryzen 9600X – and with those things worked just fine, e.g. no
> corruptions. But they came back after putting the 8600G back in.
So basically you need a specific board and a specific CPU, and only
one M.2 SSD in the two slots to reproduce it? Puh. I'm kinda lost on
what we could do about this on the Linux side.
Powered by blists - more mailing lists