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. (If I understood things right!) If the device firmware doesn't log that, or the firmware hasn't ran through a log point, it makes sense to report absolute min/max of the scales. Yours, Linus Walleij
