[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <379bba80-df0f-44c5-a15e-fd4393c52b8f@simg.de>
Date: Tue, 28 Jan 2025 13:00:31 +0100
From: Stefan <linux-kernel@...g.de>
To: Christoph Hellwig <hch@....de>, Thorsten Leemhuis <linux@...mhuis.info>,
bugzilla-daemon@...nel.org
Cc: Mario Limonciello <mario.limonciello@....com>,
Bruno Gravato <bgravato@...il.com>, 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>
Subject: Re: [Bug 219609] File corruptions on SSD in 1st M.2 socket of AsRock
X600M-STX + Ryzen 8700G
Hi,
Am 28.01.25 um 08:41 schrieb Christoph Hellwig:
> So basically you need a specific board and a specific CPU, and only
> one M.2 SSD in the two slots to reproduce it?
more generally, it dependents on which PCIe devices are used. On my PC
corruptions also disappear if I disable the ethernet controller in the BIOS.
Furthermore it depends on transaction sizes (that's why older kernels
work), IOMMU, sometimes on volatile write cache and partially on SSD
type (which may have something to do with the former things).
> Puh. I'm kinda lost on what we could do about this on the Linux
> side.
Because it also depends on the CPU series, a firmware or hardware issue
seems to be more likely than a Linux bug.
ATM ASRock is still trying to reproduce the issue. (I'm in contact with
them to. But they have Chinese new year holidays in Taiwan this week.)
If they can't reproduce it, they have to provide an explanation why the
issues are seen by so many users.
Regards Stefan
Powered by blists - more mailing lists