All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Brunberg <ingo_brunberg@web.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: Namepace identification descriptor list is optional
Date: Thu, 23 Jul 2020 03:23:28 +0200	[thread overview]
Message-ID: <m3sgdj10tr.fsf@web.de> (raw)
In-Reply-To: <c92f9d41-de84-ab54-c003-8649d20deb50@grimberg.me> (message from Sagi Grimberg on Wed, 22 Jul 2020 16:23:24 -0700)

Sagi Grimberg <sagi@grimberg.me> writes:

>> With commit ea43d97, appearing now in kernel 5.7.8, you made my cheap
>> SSD disfunctional again. For reference, see bug 205679. Maybe you
>> remember the discussion.
>>
>> I do not know if this was intentional or not. Maybe you should introduce
>> a quirk for that particular controller.
>
> Either we quirk this controller, or we are back to test specific errors...
>
> What is the pci id of the device to test a quirk?

The PCI ID is 126f:2263

Related old and new bugs on bugzilla.kernel.org with some actual drives
listed are: 205679, 205645, 208583, 208585

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2020-07-23  1:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 15:56 [PATCH] nvme: Namepace identification descriptor list is optional Keith Busch
2019-12-02 15:56 ` Keith Busch
2019-12-02 16:15 ` Christoph Hellwig
2019-12-02 16:15   ` Christoph Hellwig
2019-12-02 16:22   ` Keith Busch
2019-12-02 16:22     ` Keith Busch
2019-12-02 16:27     ` Nadolski, Edmund
2019-12-02 16:27       ` Nadolski, Edmund
2019-12-02 16:29       ` Christoph Hellwig
2019-12-02 16:29         ` Christoph Hellwig
2019-12-02 16:45         ` Nadolski, Edmund
2019-12-02 16:45           ` Nadolski, Edmund
2019-12-02 16:49         ` Keith Busch
2019-12-02 16:49           ` Keith Busch
2019-12-02 17:34           ` Christoph Hellwig
2019-12-02 17:34             ` Christoph Hellwig
2019-12-02 21:21             ` Keith Busch
2019-12-02 21:21               ` Keith Busch
2020-07-10  8:22 ` Ingo Brunberg
2020-07-22 23:23   ` Sagi Grimberg
2020-07-23  1:23     ` Ingo Brunberg [this message]
2020-07-28 11:08       ` Christoph Hellwig
2020-07-28 14:41         ` Ingo Brunberg
2020-07-28 16:01           ` Sagi Grimberg
     [not found] <d163890a-a469-e71c-45b7-f63e1efee04e@intel.com>
2020-07-12  9:31 ` Ingo Brunberg
2020-07-12 17:03   ` Rajashekar, Revanth
2020-07-14 15:21   ` 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=m3sgdj10tr.fsf@web.de \
    --to=ingo_brunberg@web.de \
    --cc=linux-nvme@lists.infradead.org \
    --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.