Announcement

Collapse
No announcement yet.

Linux In 2020 Can Finally Provide Sane Monitoring Of SATA Drive Temperatures

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Linux In 2020 Can Finally Provide Sane Monitoring Of SATA Drive Temperatures

    Phoronix: Linux In 2020 Can Finally Provide Sane Monitoring Of SATA Drive Temperatures

    Here is another long overdue kernel change... For more than a decade there have been patches trying to get SATA/SCSI drive temperature monitoring working nicely within the Linux kernel but none of that work ever made it through for mainlining. That has left various user-space tools to provide the functionality, but in doing so that has required root access and not to mention the need to first install said utilities. Well, with Linux 5.6 in 2020, there is finally a proper drive temperature driver for disks and solid-state drives with temperature sensors...

    http://www.phoronix.com/scan.php?pag...nel-SATA-Temps

  • birdie
    replied
    Originally posted by groeck View Post

    I'll be happy to review and if appropriate accept respective patches. Note that the original patch included support for reporting energy values, which should be dropped. See Jean Delvare's feedback from the time for reasons.
    I'm quite sure this patch is so stale it won't apply to mainline and thus needs to be fixed/rewritten and I'm not a C programmer to do that. And I've no idea how to make the person who wrote it in the first place to get back to it. Looks like a lost case to me

    I'm pretty sure thousands of users will be happy to test it just like we're now testing your k10temp patched driver.

    Leave a comment:


  • groeck
    replied
    Originally posted by birdie View Post

    Great many thanks, Guenter! It's great to see you here - quite unexpected!

    Now what about reviving additional data points in the coretemp driver, a feature I asked you about many years ago, and you actually implemented it, only to abandon it swiftly under some weird pretense?
    I'll be happy to review and if appropriate accept respective patches. Note that the original patch included support for reporting energy values, which should be dropped. See Jean Delvare's feedback from the time for reasons.

    Leave a comment:


  • groeck
    replied
    Originally posted by groeck View Post
    ... Either case, a preliminary patch series adding more telemetry reporting to the k10temp driver is now available for testing at https://patchwork.kernel.org/project...?series=229271.
    Thanks everyone for the test feedback. An updated version of the series is now available at https://patchwork.kernel.org/project...?series=230307. Note that I may hold the series for the 5.7 kernel; while I got a lot of test feedback, no one actually reviewed the code. I won't drop it entirely without review (it doesn't seem that risky), but that warrants a lengthy soak time in linux-next.

    Leave a comment:


  • birdie
    replied
    Originally posted by groeck View Post
    Thanks a lot for all the feedback. Regarding test coverage for drivetemp, I can only recommend for everyone - especially everyone who raised concerns here - to test it and provide feedback. The driver is only loaded on request, so anyone with concerns about performance impact can simply not load it or, to be sure, blacklist it. This is not an opt-out driver, it is an opt-in driver.
    Regarding temperature and other telemetry reporting on Ryzen CPUs, please note that AMD did not publish the necessary information which would enable any such improvements. Quite obviously at least some of that information has leaked, and the zenpower driver referenced here makes use of it. At this point I would like to point out that patches to improve the upstream k10temp driver to report the additional telemetry have before now not been posted. As a kind reminder, anyone interested in such improvements to this and other drivers is invited to submit patches for inclusion into the upstream kernel. Either case, a preliminary patch series adding more telemetry reporting to the k10temp driver is now available for testing at https://patchwork.kernel.org/project...?series=229271.
    Great many thanks, Guenter! It's great to see you here - quite unexpected!

    Now what about reviving additional data points in the coretemp driver, a feature I asked you about many years ago, and you actually implemented it, only to abandon it swiftly under some weird pretense?
    Last edited by birdie; 01-17-2020, 09:54 AM.

    Leave a comment:


  • groeck
    replied
    Thanks a lot for all the feedback. Regarding test coverage for drivetemp, I can only recommend for everyone - especially everyone who raised concerns here - to test it and provide feedback. The driver is only loaded on request, so anyone with concerns about performance impact can simply not load it or, to be sure, blacklist it. This is not an opt-out driver, it is an opt-in driver.
    Regarding temperature and other telemetry reporting on Ryzen CPUs, please note that AMD did not publish the necessary information which would enable any such improvements. Quite obviously at least some of that information has leaked, and the zenpower driver referenced here makes use of it. At this point I would like to point out that patches to improve the upstream k10temp driver to report the additional telemetry have before now not been posted. As a kind reminder, anyone interested in such improvements to this and other drivers is invited to submit patches for inclusion into the upstream kernel. Either case, a preliminary patch series adding more telemetry reporting to the k10temp driver is now available for testing at https://patchwork.kernel.org/project...?series=229271.

    Leave a comment:


  • tuxd3v
    replied
    Originally posted by tildearrow View Post
    I. completely. agree.
    It's been a while and I still cannot read my AMD card's memory temperature or voltage.
    Manufacturers just don't care enough to work with Linux :l
    That type of Hardware is diferent..
    Disks are a very sensitive thing, among others..

    Seagate has the OpenSeaChest Tools, and they work great, for other vendors I don't know..

    Leave a comment:


  • tildearrow
    replied
    Originally posted by birdie View Post

    HWiNFO does not need any "special drivers for sensors". It works right out of the box after you install Windows without installing any drivers whatsoever.

    It needs AMD/NVIDIA drivers to monitor GPUs though but it's because NVIDIA and AMD closely guard their HW interfaces and only expose them via their own proprietary APIs.

    God, why are there so many stupid open source fanatics here?
    I. completely. agree.

    It's been a while and I still cannot read my AMD card's memory temperature or voltage.

    Manufacturers just don't care enough to work with Linux :l

    Leave a comment:


  • tildearrow
    replied
    Originally posted by 144Hz View Post
    Too bad when SATA drives just went to the same pile as floppy drives.
    What are you talking about?

    Leave a comment:


  • caligula
    replied
    Originally posted by 144Hz View Post
    Too bad when SATA drives just went to the same pile as floppy drives.
    Don't be silly. The price per storage unit is significantly lower. At least for smaller corporations, spending $10k or $100k on drives is a relevant question.

    Leave a comment:

Working...
X