All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arman Hajishafieha <arman.hajishafieha@hotmail.com>
To: "hch@lst.de" <hch@lst.de>, "me@kingtous.cn" <me@kingtous.cn>
Cc: "kbusch@kernel.org" <kbusch@kernel.org>,
	"kingtous@qq.com" <kingtous@qq.com>,
	"sagi@grimberg.me" <sagi@grimberg.me>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"axboe@fb.com" <axboe@fb.com>
Subject: Re: [PATCH] fix: nvme_update_ns_info method should be called even if nvme_ms_ids_equal return false
Date: Mon, 23 May 2022 18:18:01 +0000	[thread overview]
Message-ID: <741c80abb8a443c4745f213e9ecd413f6a6a7467.camel@hotmail.com> (raw)
In-Reply-To: <20220412050441.GA5311@lst.de>

On Tue, 2022-04-12 at 07:04 +0200, Christoph Hellwig wrote:
> On Mon, Apr 11, 2022 at 10:20:13PM +0800, 金韬 wrote:
> > btw, I checked the patch code, I noticed "MAXIO MAP1202" is hard
> > coded in 
> > pci.c. I think not only MAP1202 has the problem mentioned in this
> > thread, 
> > but also "MAXIO MAP1002"(Gloway Basic 1T NVMe SSD, which has the
> > same 
> > suspend issue).
> 
> If you can verify it has the issue we can add a quirk for it as well.

Hello.

I can confirm that "MAXIO MAP1001" (1e4b:1001) controller found in
"Asgard N2 1TB SSD" suffers from the exact same issue as well.
After applying the patch to disable checking namespace identifiers it
can resume from suspend normally. It seems like this issue affects a
wider range of Maxio controllers.
Could you please add a quirk for this device as well?

  parent reply	other threads:[~2022-05-23 18:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08  2:57 [PATCH] fix: nvme_update_ns_info method should be called even if nvme_ms_ids_equal return false me
2022-04-08  5:19 ` Christoph Hellwig
     [not found]   ` <ABwAxgCYBwe5Iq2fM1-8qqrc.3.1649398333597.Hmail.me@kingtous.cn>
2022-04-08  6:22     ` Christoph Hellwig
2022-04-08  7:56       ` 金韬
2022-04-08  8:07         ` Christoph Hellwig
2022-04-08  8:35           ` 金韬
2022-04-08 15:18           ` Keith Busch
2022-04-08 16:04             ` Christoph Hellwig
2022-04-09  0:58               ` Tao Jin
2022-04-09  4:43                 ` Christoph Hellwig
2022-04-09  9:11                   ` Tao Jin
2022-04-11  5:49                     ` Christoph Hellwig
2022-04-11  5:56                       ` 金韬
2022-04-11  6:07                         ` Christoph Hellwig
2022-04-11 14:20                           ` 金韬
2022-04-12  5:04                             ` Christoph Hellwig
2022-04-12  6:34                               ` 金韬
2022-05-23 18:18                               ` Arman Hajishafieha [this message]
2022-05-24 13:50                                 ` hch
2022-05-24 16:51                                   ` Arman Hajishafieha
2022-05-24 20:54                                     ` Chaitanya Kulkarni

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=741c80abb8a443c4745f213e9ecd413f6a6a7467.camel@hotmail.com \
    --to=arman.hajishafieha@hotmail.com \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kingtous@qq.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=me@kingtous.cn \
    --cc=sagi@grimberg.me \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.