From: Guenter Roeck <linux@roeck-us.net>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-hwmon@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, Jens Axboe <axboe@fb.com>,
Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] nvme: hwmon: provide temperature min and max values for each sensor
Date: Tue, 12 Nov 2019 07:04:38 -0800
Message-ID: <e2699eee-8ca2-fcf4-d6b2-624cbddd4c6d@roeck-us.net> (raw)
In-Reply-To: <CAC5umyjviR1J5HojE6WBhYQCzu=CFPPoNxXY=T9KRw2yTpO=VQ@mail.gmail.com>
On 11/12/19 6:40 AM, Akinobu Mita wrote:
[ ... ]
>> I'll see if I can test this tonight on my other NVMEs. I also dug up an old
>> NVMe drive from Toshiba; I'll see if I can connect and test it as well.
>
> That's nice.
>
It works on all devices I have, including the Toshiba, with the exception
of the Intel. Interestingly, the Toshiba NVMe reports:
nvme-pci-0600
Adapter: PCI adapter
Composite: +56.0°C (low = -20.0°C, high = +85.0°C)
(crit = +82.0°C)
Sensor 1: +56.0°C (low = -20.0°C, high = +85.0°C)
ie the critical temperature is lower than the high temperature. Go figure.
The Toshiba model is
THNSN5256GPU7 NVMe TOSHIBA 256GB
The Intel NVMe has the latest firmware version installed, so this isn't
a problem that was ever fixed.
Guenter
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply index
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 14:17 Akinobu Mita
2019-11-10 16:30 ` Guenter Roeck
2019-11-11 15:56 ` Akinobu Mita
2019-11-11 17:35 ` Guenter Roeck
2019-11-12 14:40 ` Akinobu Mita
2019-11-12 15:04 ` Guenter Roeck [this message]
2019-11-12 15:06 ` Christoph Hellwig
2019-11-12 16:35 ` Guenter Roeck
2019-11-11 16:53 ` Christoph Hellwig
2019-11-12 14:19 ` Akinobu Mita
2019-11-12 14:21 ` Christoph Hellwig
2019-11-12 15:00 ` Akinobu Mita
2019-11-12 15:08 ` Christoph Hellwig
2019-11-12 16:38 ` Guenter Roeck
2019-11-13 12:58 ` Akinobu Mita
2019-11-13 14:11 ` Guenter Roeck
Reply instructions:
You may reply publically 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=e2699eee-8ca2-fcf4-d6b2-624cbddd4c6d@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akinobu.mita@gmail.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=jdelvare@suse.com \
--cc=kbusch@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--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
Linux-NVME Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/linux-nvme/0 linux-nvme/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 linux-nvme linux-nvme/ https://lore.kernel.org/linux-nvme \
linux-nvme@lists.infradead.org
public-inbox-index linux-nvme
Example config snippet for mirrors
Newsgroup available over NNTP:
nntp://nntp.lore.kernel.org/org.infradead.lists.linux-nvme
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git