From: Holger Huo <holgerhuo@outlook.com>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Holger Huo <i@holger.one>
Subject: Re: [PATCH] drivers/nvme: Add quirks for device 1cc4:6a14
Date: Wed, 10 Apr 2024 13:31:50 +0800 [thread overview]
Message-ID: <ME3P282MB2481225B8B95249FB92E4981B5062@ME3P282MB2481.AUSP282.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <ZhYCyuP6vTJq-TZq@kbusch-mbp.dhcp.thefacebook.com>
On Wednesday, April 10, 2024 11:08:58 AM +08 Keith Busch wrote:
> On Wed, Apr 10, 2024 at 10:05:46AM +0800, Holger Huo wrote:
> > On Wednesday, April 10, 2024 4:14:42 AM +08 Keith Busch wrote:
> > > On Wed, Apr 10, 2024 at 03:28:50AM +0800, Holger Huo wrote:
> > > > This commit adds NVME_QUIRK_BOGUS_NID for device [1cc4:6a14], the
> > > > Shenzhen Unionmemory Information System Ltd. RPEYJ1T24MKN2QWY PCIe
> > > > 4.0 NVMe SSD 1024GB (DRAM-less), which can be found on many Lenovo
> > > > notebooks. This SSD produces all-zero nguid.
> > > >
> > > > Other SSDs manufatured by Shenzhen Unionmemory Information System
> > > > Ltd are likely to face similar issues, but I currently have no
> > > > device to test.
> > >
> > > Are you using the most recent stable kernel and still need this patch?
> > > These quirks shouldn't be necessary anymore unless it's advertising
> > > multipath capabilities, and it doesn't sound like this one should be
> > > doing that.
> >
> > Yes. My current Linux kernel version is 6.8.4 by arch. After further
> > investigation I found these quirks truly had no effects.
> > But my nvme drive still freezes with Device not ready; aborting reset,
> > CSTS=0x1 failures and AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0001
> > ...] waking from s0 (s2idle) sleep. Are there any other quirks or what
> > that I should try
>
> I've seen the IO_PAGE_FAULT error reported before, but all I've heard is
> that it means the device attempts to access a memory address that it is
> not allowed to. I don't know why that would happen, though. I've never
> first hand experience with this condition, I'm just as confused.
Thanks for your help! I found this to be IOMMU related and I have to set
AMD_IOMMU=off to have it working. This is not nvme driver related. Sorry for
making this patch.
prev parent reply other threads:[~2024-04-10 5:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 19:28 [PATCH] drivers/nvme: Add quirks for device 1cc4:6a14 Holger Huo
2024-04-09 20:14 ` Keith Busch
2024-04-10 2:05 ` Holger Huo
2024-04-10 3:08 ` Keith Busch
2024-04-10 5:31 ` Holger Huo [this message]
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=ME3P282MB2481225B8B95249FB92E4981B5062@ME3P282MB2481.AUSP282.PROD.OUTLOOK.COM \
--to=holgerhuo@outlook.com \
--cc=i@holger.one \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).