From owner-freebsd-hackers@freebsd.org Tue Nov 6 17:32:32 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72095112AFF4 for ; Tue, 6 Nov 2018 17:32:32 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A50DC827EE; Tue, 6 Nov 2018 17:32:31 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 62C1A353BF; Tue, 6 Nov 2018 10:33:11 -0700 (MST) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aP9I8N77EXl5; Tue, 6 Nov 2018 10:33:11 -0700 (MST) Received: from photon.int.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Tue, 6 Nov 2018 10:33:11 -0700 (MST) From: Rebecca Cran To: Zaphod Beeblebrox Cc: mjoras@freebsd.org, FreeBSD Hackers Subject: Re: Threadripper Thermal strangeness. Date: Tue, 06 Nov 2018 10:32:29 -0700 Message-ID: <1851518.EnoYUHA41c@photon.int.bluestop.org> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: A50DC827EE X-Spamd-Result: default: False [-4.75 / 200.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bluestop.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; TO_DN_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.986,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bluestop.org:+]; DMARC_POLICY_ALLOW(-0.50)[bluestop.org,quarantine]; MX_GOOD(-0.01)[cached: mail.bluestop.org]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; CTE_CASE(0.50)[]; ASN(0.00)[asn:7922, ipnet:96.64.0.0/11, country:US]; IP_SCORE(-1.25)[ipnet: 96.64.0.0/11(-4.87), asn: 7922(-1.30), country: US(-0.08)] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Nov 2018 17:32:32 -0000 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