From: "Diederik de Haas" <didi.debian@cknow.org>
To: <linux-nvme@lists.infradead.org>
Cc: <linux-kernel@vger.kernel.org>,
"Diederik de Haas" <didi.debian@cknow.org>
Subject: [BUG report] kernel warnings with Samsung 970 EVO 2TB SSD
Date: Sat, 16 Aug 2025 13:40:44 +0200 [thread overview]
Message-ID: <DC3TO97G0RMI.3KKUONOCLJHFB@cknow.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4867 bytes --]
Hi,
I have a Samsung 970 EVO 2TB SSD and I see these kernel warnings:
root@nanopi-r5s:~# uname -a
Linux nanopi-r5s 6.16-arm64-cknow #1 SMP PREEMPT Debian 6.16-1 (2025-07-28) aarch64 GNU/Linux
root@nanopi-r5s:~# dmesg --level 0,1,2
root@nanopi-r5s:~# dmesg --level 3
root@nanopi-r5s:~# dmesg --level 4
[ 2.410231] dw-apb-uart fe660000.serial: forbid DMA for kernel console
[ 5.234812] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
[ 5.242112] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation.
[ 5.246222] gpio gpiochip2: Static allocation of GPIO base is deprecated, use dynamic allocation.
[ 5.252811] gpio gpiochip3: Static allocation of GPIO base is deprecated, use dynamic allocation.
[ 5.265791] gpio gpiochip4: Static allocation of GPIO base is deprecated, use dynamic allocation.
[ 5.741901] r8169 0000:01:00.0: can't read MAC address, setting random one
[ 5.806644] pci 0001:10:00.0: Primary bus is hard wired to 0
[ 5.849952] r8169 0001:11:00.0: can't read MAC address, setting random one
[ 6.017270] pci 0002:20:00.0: Primary bus is hard wired to 0
[ 6.393688] nvme nvme0: missing or invalid SUBNQN field.
[ 21.484306] nvme nvme0: using unchecked data buffer
root@nanopi-r5s:~# dmesg | grep nvme
[ 6.386187] nvme nvme0: pci function 0002:21:00.0
[ 6.386697] nvme 0002:21:00.0: enabling device (0000 -> 0002)
[ 6.393688] nvme nvme0: missing or invalid SUBNQN field.
[ 6.397901] nvme nvme0: D3 entry latency set to 8 seconds
[ 6.428168] nvme nvme0: 4/0/0 default/read/poll queues
[ 6.465173] nvme0n1: p1
[ 12.522314] systemd[1]: Starting modprobe@nvme_fabrics.service - Load Kernel Module nvme_fabrics...
[ 12.973871] systemd[1]: modprobe@nvme_fabrics.service: Deactivated successfully.
[ 12.977051] systemd[1]: Finished modprobe@nvme_fabrics.service - Load Kernel Module nvme_fabrics.
[ 21.484306] nvme nvme0: using unchecked data buffer
Before I put this SSD into my FriendlyELEC NanoPi R5S (rk3568; arm64)
I had it in my main PC (AMD Ryzen 1800X; amd64) where I had these
warnings as well, so it seems directly connected to the drive, not the
device it's plugged into.
I wonder if something can be done to fix those warnings.
I'm not aware of these warnings causing actual problems, but I haven't
'really' used it thus far (mostly to store some media files), but I want
to use my NanoPi R5S as my server (with f.e. my git repos), so I want to
be extra sure my data won't be at risk. And I don't like ignoring kernel
warnings; I assume they're warnings for a reason.
Some more data about the drive:
root@nanopi-r5s:~# nvme list
Node Generic SN Model Namespace Usage Format FW Rev
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
/dev/nvme0n1 /dev/ng0n1 xxxxxxxxxxxxxxx Samsung SSD 970 EVO Plus 2TB 0x1 534.51 GB / 2.00 TB 512 B + 0 B 2B2QEXM7
root@nanopi-r5s:~# nvme get-feature /dev/nvme0 -f 3
get-feature:0x03 (LBA Range Type): NVMe status: Invalid Namespace or Format: The namespace or the format of that namespace is invalid(0x200b)
I don't know if it would/can be risky to share the Serial Number, so I
blanked that out, but I can provide that if that would be helpful.
root@nanopi-r5s:~# lspci -v -s 0002:21:00.0
0002:21:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 (prog-if 02 [NVM Express])
Subsystem: Samsung Electronics Co Ltd SSD 970 EVO/PRO
Flags: bus master, fast devsel, latency 0, IRQ 75
Memory at f0200000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, IntMsgNum 0
Capabilities: [b0] MSI-X: Enable+ Count=33 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [158] Power Budgeting <?>
Capabilities: [168] Secondary PCI Express
Capabilities: [188] Latency Tolerance Reporting
Capabilities: [190] L1 PM Substates
Kernel driver in use: nvme
Kernel modules: nvme
But I did not change the Device Serial Number from lspci.
AFAIK I have the latest firmware (checked with fwupd).
Happy to provide additional data, but as I don't know what would be
useful, I figured I'll leave it up to the experts to ask for it.
Cheers,
Diederik
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2025-08-16 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 11:40 Diederik de Haas [this message]
2025-08-16 13:20 ` [BUG report] kernel warnings with Samsung 970 EVO 2TB SSD Keith Busch
2025-08-16 14:11 ` Diederik de Haas
2025-08-18 18:58 ` Keith Busch
2025-08-18 20:48 ` Diederik de Haas
2025-08-18 21:20 ` Diederik de Haas
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=DC3TO97G0RMI.3KKUONOCLJHFB@cknow.org \
--to=didi.debian@cknow.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 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.