Hi all,

On 2025-12-08 21:23, Ilikara Zheng wrote:

Secondary temperature thresholds (temp2_{min,max}) were not reported properly on this NVMe SSD. This resulted in an error while attempting to read these values with sensors(1):

ERROR: Can't get value of subfeature temp2_min: I/O error ERROR: Can't get value of subfeature temp2_max: I/O error

Add the device to the nvme_id_table with the NVME_QUIRK_NO_SECONDARY_TEMP_THRESH flag to suppress access to all non- composite temperature thresholds.

Cc: stable@vger.kernel.org Signed-off-by: Ilikara Zheng ilikara@aosc.io

---

drivers/nvme/host/pci.c | 2 ++ 1 file changed, 2 insertions(+)

diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c index e5ca8301bb8b..31049f33f27d 100644 --- a/drivers/nvme/host/pci.c +++ b/drivers/nvme/host/pci.c @@ -3997,6 +3997,8 @@ static const struct pci_device_id nvme_id_table[] = { .driver_data = NVME_QUIRK_NO_DEEPEST_PS, }, { PCI_DEVICE(0x1e49, 0x0041), /* ZHITAI TiPro7000 NVMe SSD */ .driver_data = NVME_QUIRK_NO_DEEPEST_PS, },

• { PCI_DEVICE(0x1fa0, 0x2283), /* Wodposit WPBSNM8-256GTP */

• .driver_data = NVME_QUIRK_NO_SECONDARY_TEMP_THRESH, },
  

  { PCI_DEVICE(0x025e, 0xf1ac), /* SOLIDIGM P44 pro SSDPFKKW020X7 */ .driver_data = NVME_QUIRK_NO_DEEPEST_PS, }, { PCI_DEVICE(0xc0a9, 0x540a), /* Crucial P2 */

I have tested this patch on a CTCISZ 3B6000M-NUC with an exact same SSD and this has resolved the error with sensor(1).

Tested-by: Wu Haotian rigoligo03@gmail.com