From: Christoph Hellwig <hch@lst.de>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
Bruno Gravato <bgravato@gmail.com>, Stefan <linux-kernel@simg.de>,
Keith Busch <kbusch@kernel.org>,
bugzilla-daemon@kernel.org, Adrian Huang <ahuang12@lenovo.com>,
Linux kernel regressions list <regressions@lists.linux.dev>,
linux-nvme@lists.infradead.org, Jens Axboe <axboe@fb.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Bug 219609] File corruptions on SSD in 1st M.2 socket of AsRock X600M-STX + Ryzen 8700G
Date: Tue, 28 Jan 2025 08:41:33 +0100 [thread overview]
Message-ID: <20250128074133.GA22435@lst.de> (raw)
In-Reply-To: <10e39c88-4667-4c61-b3eb-3dd7ee3074c3@leemhuis.info>
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.
next prev parent reply other threads:[~2025-01-28 7:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 14:38 [Regression] File corruptions on SSD in 1st M.2 socket of AsRock X600M-STX Thorsten Leemhuis
2025-01-08 15:07 ` Keith Busch
2025-01-09 8:28 ` Christoph Hellwig
2025-01-09 8:52 ` Thorsten Leemhuis
2025-01-09 15:44 ` [Bug 219609] File corruptions on SSD in 1st M.2 socket of AsRock X600M-STX + Ryzen 8700G Stefan
2025-01-10 11:17 ` Bruno Gravato
2025-01-15 6:37 ` Bruno Gravato
2025-01-15 8:40 ` Thorsten Leemhuis
2025-01-16 17:29 ` Thorsten Leemhuis
2025-01-17 8:05 ` Christoph Hellwig
2025-01-17 9:51 ` Thorsten Leemhuis
2025-01-17 9:55 ` Christoph Hellwig
2025-01-17 10:30 ` Thorsten Leemhuis
2025-02-04 6:26 ` Christoph Hellwig
2025-01-17 13:36 ` Bruno Gravato
2025-01-20 14:31 ` Thorsten Leemhuis
2025-01-28 7:41 ` Christoph Hellwig [this message]
2025-01-28 12:00 ` Stefan
2025-01-28 12:52 ` Dr. David Alan Gilbert
2025-01-28 14:24 ` Stefan
2025-02-02 8:32 ` Bruno Gravato
2025-02-04 6:12 ` Christoph Hellwig
2025-02-04 9:12 ` Bruno Gravato
2025-02-03 18:48 ` Stefan
2025-02-06 15:58 ` Stefan
2025-01-17 21:31 ` Stefan
2025-01-18 1:03 ` Keith Busch
2025-01-15 10:47 ` Stefan
2025-01-15 13:14 ` Bruno Gravato
2025-01-15 16:26 ` Stefan
2025-01-10 0:10 ` [Regression] File corruptions on SSD in 1st M.2 socket of AsRock X600M-STX Keith Busch
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=20250128074133.GA22435@lst.de \
--to=hch@lst.de \
--cc=ahuang12@lenovo.com \
--cc=axboe@fb.com \
--cc=bgravato@gmail.com \
--cc=bugzilla-daemon@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=kbusch@kernel.org \
--cc=linux-kernel@simg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux@leemhuis.info \
--cc=mario.limonciello@amd.com \
--cc=regressions@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