From: Claus Stovgaard <claus.stovgaard@gmail.com>
To: linux-nvme@lists.infradead.org
Subject: Missing or invalid SUBNQN on Corsair MP600 1TB device
Date: Mon, 25 Jan 2021 17:00:57 +0100 [thread overview]
Message-ID: <04fdb6a116bbc4d9eadc3f9434d8b6f2426e3c57.camel@gmail.com> (raw)
Hi
This is my first post to this mailing list, so please forgive me if it
is already discussed.
I have just build a new workstation, where I noticed the following
warning for the Corsair MP600 1 TB drive.
nvme nvme0: missing or invalid SUBNQN field.
it arrived with firmware 11.3 and I have later upgraded to firmware
13.0 to see if they have fixed the firmware.
Have also reported in their forum
https://forum.corsair.com/forums/showthread.php?p=1077109#post1077109
Looking in the host pci.c code it seems to be a known issue on some
drives where the "NVME_QUIRK_IGNORE_DEV_SUBNQN" is used.
So I guess that Corsair MP600 is a candidate for the same quirk.
Considered to add the Corsair to the list of drives with
NVME_QUIRK_IGNORE_DEV_SUBNQN, but would just ask here first, if it
would be the correct use and understanding.
Regards Claus
Below is info for my system for reference.
nova /home/frosteyes # uname -a
Linux nova 5.10.10-gentoo-FrostEyes #1 SMP PREEMPT Sun Jan 24 23:26:32
CET 2021 x86_64 AMD Ryzen 9 5950X 16-Core Processor AuthenticAMD
GNU/Linux
nova /home/frosteyes # journalctl -b | grep nvme0
jan 24 23:32:23 nova kernel: nvme nvme0: pci function 0000:01:00.0
jan 24 23:32:23 nova kernel: nvme nvme0: missing or invalid SUBNQN
field.
jan 24 23:32:23 nova kernel: nvme nvme0: Shutdown timeout set to 10
seconds
jan 24 23:32:23 nova kernel: nvme nvme0: 8/0/0 default/read/poll queues
jan 24 23:32:23 nova kernel: nvme0n1: p1 p2
nova /home/frosteyes # nvme list
Node SN Model
Namespace Usage Format FW Rev
---------------- -------------------- -------------------------------
--------- --------- -------------------------- ---------------- -----
---
/dev/nvme0n1 203982290001285542EC Force
MP600 1 1,00 TB
/ 1,00 TB 512 B + 0 B EGFM13.0
nova /home/frosteyes # lspci -v -nn -s 1:00
01:00.0 Non-Volatile memory controller [0108]: Phison Electronics
Corporation E16 PCIe4 NVMe Controller [1987:5016] (rev 01) (prog-if 02
[NVM Express])
Subsystem: Phison Electronics Corporation E16 PCIe4 NVMe
Controller [1987:5016]
Flags: bus master, fast devsel, latency 0, IRQ 42, NUMA node 0
Memory at fcf00000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [d0] MSI-X: Enable+ Count=9 Masked-
Capabilities: [e0] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [f8] Power Management version 3
Capabilities: [100] Latency Tolerance Reporting
Capabilities: [110] L1 PM Substates
Capabilities: [128] Alternative Routing-ID Interpretation (ARI)
Capabilities: [1e0] Data Link Feature <?>
Capabilities: [200] Advanced Error Reporting
Capabilities: [300] Secondary PCI Express
Capabilities: [340] Physical Layer 16.0 GT/s <?>
Capabilities: [378] Lane Margining at the Receiver <?>
Kernel driver in use: nvme
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-01-25 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 16:00 Claus Stovgaard [this message]
2021-01-25 17:58 ` Missing or invalid SUBNQN on Corsair MP600 1TB device Keith Busch
2021-02-01 21:22 ` Claus Stovgaard
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=04fdb6a116bbc4d9eadc3f9434d8b6f2426e3c57.camel@gmail.com \
--to=claus.stovgaard@gmail.com \
--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