On 1/12/20 4:07 AM, Linus Walleij wrote:
On Sun, Jan 12, 2020 at 1:03 PM Gabriel C <nix.or.die@xxxxxxxxx> wrote:
Am So., 12. Jan. 2020 um 12:22 Uhr schrieb Linus Walleij
<linus.walleij@xxxxxxxxxx>:
On Sun, Jan 12, 2020 at 12:18 PM Gabriel C <nix.or.die@xxxxxxxxx> wrote:
What I've noticed however is the nvme temperature low/high values on
the Sensors X are strange here.
(...)
Sensor 1: +27.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +29.9°C (low = -273.1°C, high = +65261.8°C)
(...)
Sensor 1: +23.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +25.9°C (low = -273.1°C, high = +65261.8°C)
That doesn't look strange to me. It seems like reasonable defaults
from the firmware if either it doesn't really log the min/max temperatures
or hasn't been through a cycle of updating these yet. Just set both
to absolute min/max temperatures possible.
Ok I'll check that.
Do you mean by setting the temperatures to use a lmsensors config?
Or is there a way to set these with a nvme command?
Not that I know of.
The min/max are the minumum and maximum temperatures the
device has experienced during this power-on cycle.
No, that would be lowest/highest. The above are (or should be) per-sensor
setpoints. The default for those is typically the absolute minimum /
maximum of the supported range.
Some SATA drives report the lowest/highest temperatures experienced
since power cycle, like here.
drivetemp-scsi-5-0
Adapter: SCSI adapter
temp1: +23.0°C (low = +0.0°C, high = +60.0°C)
(crit low = -41.0°C, crit = +85.0°C)
(lowest = +20.0°C, highest = +31.0°C)
Guenter
