lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 9 Jun 2018 22:14:20 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Kai-Heng Feng <kai.heng.feng@...onical.com>
Cc:     Chris Ouellet <rabbit.of.war@...il.com>,
        linux-hwmon@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Ryzen 2700 Temperature offset?

On Sun, Jun 10, 2018 at 03:03:47AM +0800, Kai-Heng Feng wrote:
> at 23:49, Guenter Roeck <linux@...ck-us.net> wrote:
> 
> >On Thu, Jun 07, 2018 at 11:03:13AM +0800, Kai Heng Feng wrote:
> >>Hi Guenter,
> >>
> >>A user thinks the Ryzen 2700 temperature may not be correct [1].
> >>Can you take a look when you have time? Thanks.
> >>
> >>Also, where can I find all these temperature offsets? I googled but with
> >>no
> >>result.
> >Problem is that the offsets are not documented in public, making it
> >difficult to find out. For Ryzen 2700, there is currently no offset
> >configured; I was told that there is none. For Ryzen 2700X, the offset
> >is 10 degrees C.
> 
> I am still quite interesting where you get this information...
> 
Primarily lots of online research. Windows tools usually support the
offsets, so screendumps help in some cases. 

> >
> >>[1] https://bugs.launchpad.net/bugs/1774817
> >
> >The key here is the commit mentioned in the log (1b59788979acd). It does
> >not only adjust the per-CPU offset, but also takes a configurable offset
> >of 49 degrees C into account. You'll need to apply that patch in your
> >kernel, or the temperature may be off by 49 degrees C.
> 
> So unless AMD shares these offsets value, we can never know what correct
> offsets are?
> 
Unfortunately that is correct.

AFAIK the information is available from AMD under NDA. I can not sign such an
NDA, and even if I could and would, I could not use the information in an open
source driver. Kind of a loose-loose situation. If you (Canonical) have any
influence at AMD, it might be useful to let them know that their policy is
not very helpful.

Guenter


> Kai-Heng
> 
> >
> >Hope this helps. If not, please let me know. Note that I am travelling;
> >responses may be delayed.
> >
> >Guenter
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hwmon" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ