Date: Tue, 06 Nov 2018 10:32:29 -0700 From: Rebecca Cran <rebecca@bluestop.org> To: Zaphod Beeblebrox <zbeeble@gmail.com> Cc: mjoras@freebsd.org, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Threadripper Thermal strangeness. Message-ID: <1851518.EnoYUHA41c@photon.int.bluestop.org> In-Reply-To: <CACpH0MfRA668zX16XQjOGcUL_6r=EWoYNgBjM_V87_wy7uDM4A@mail.gmail.com> References: <CACpH0MdACWACn2_uO_S47nzKY174aeFq516FJdqkcxM_NMiCAw@mail.gmail.com> <CADdTf%2Bh2uU=zgmSDbOG%2BJAX9OLc1nG_gRAHmKh-S4Uo-NWNvKQ@mail.gmail.com> <CACpH0MfRA668zX16XQjOGcUL_6r=EWoYNgBjM_V87_wy7uDM4A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 6 November 2018 09:58:18 MST Zaphod Beeblebrox wrote:
> 1. Wouldn't it make sense to integrate this information in amdtemp.ko?
> 2. isn't sensor offset an item in the sysctl output of amdtemp.ko ... and
> it's value is 0 for me.
I think it would make sense: it looks like amdtemp is fairly basic at the
moment, and the sensor offset is supposed to be set manually.
>From amdtemp(4):
SYSCTL VARIABLES
The following variable is available as both sysctl(8) variable and
loader(8) tunable:
dev.amdtemp.%d.sensor_offset
Add the given offset to the temperature of the sensor. Default is 0.
--
Rebecca
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1851518.EnoYUHA41c>