From owner-freebsd-hackers@freebsd.org Tue Nov 6 16:58: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 0A8811129F23 for ; Tue, 6 Nov 2018 16:58:32 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A0D58020A; Tue, 6 Nov 2018 16:58:31 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-io1-xd33.google.com with SMTP id o19-v6so9742350iod.3; Tue, 06 Nov 2018 08:58:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FdC60EvGZu6VkSRFNUb8c6Ghtf8BDzU3CxNtiHWzfDw=; b=OyBlrNmMV+9/oixmavm4FwzuiZNNvCiZxiuFeUoT1hlBOYNmcJLXiiEGYuX041oIx5 +czgAdn6iCrtyrGZr3SR92UtVUrLOcYbLZ+BbrAWu46kai+CAO+m15iT9VdK+3Fdb4Ly TbbI3w3+Y0Jkh5X3a+YD1GRGq2xoPDqhWBRaC+8Vh8BUQ/Fs3UDhf2GeWzBVkK2/1qNQ IedPYW+Yyf+DpdoeE1s8elA/yaZGquM5Hc4ZVz2A23xcdTfV8kYoSHwNG36bwSyOXjBs JuaI/jmsTcUX+HYk7pq7Cj6mLUQB/g4KE01hrwpUySzDN+zzIAYssGvN8/spbRsQaotn CUTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FdC60EvGZu6VkSRFNUb8c6Ghtf8BDzU3CxNtiHWzfDw=; b=uAGOfNiebUxEyxdJ02l7uv4rUfqmv8mcE1n2LQEmRl05E7zL5NOEBT51cdnS2rJfRr GSQk+M3xJrGv6Yx5XKN7cusAqDjXpRUHBa2juGAq2P5t0RpDGcyfSwii8YPbzxUmEyaX lel6g/mrJkgLVqdJh3mqvELPjsEseubafEDKyqhfIzn+wPwenDwz3SxzcV5MgradHlP2 Tw6ysnBy11+6zOyrj2P7ItI4ZwHGZLXM+3xtyhcGolqSXXQAByZIG02wRpDSvEb8w9KA ZEaKJtXSKLyFtv4GPGKEJ8Av3p5a8vT/VJjDAtz/MBIr9CplrD17DVmUmDylRFuOHFHc qE1A== X-Gm-Message-State: AGRZ1gJlDLTd6aebIjXWl/jHBWzCV6X4LgHkqrzVm2F+DwYdNTOASk+u SpL7Ee5gl2cBT3zIiP72Li4nm3zQ1tLgHcYjOcSF X-Google-Smtp-Source: AJdET5d85/kKKaFYaLhImJjYBYk9MRZL4sPDLi6HXhvQrZES3NolrmKbDI1dF1lecQACdcv8IZzx1+SOwdGAmHpCxOk= X-Received: by 2002:a6b:cf18:: with SMTP id o24-v6mr9957677ioa.245.1541523510292; Tue, 06 Nov 2018 08:58:30 -0800 (PST) MIME-Version: 1.0 References: <1952737.4WAli8B44Z@photon.int.bluestop.org> In-Reply-To: From: Zaphod Beeblebrox Date: Tue, 6 Nov 2018 11:58:18 -0500 Message-ID: Subject: Re: Threadripper Thermal strangeness. To: mjoras@freebsd.org Cc: rebecca@bluestop.org, FreeBSD Hackers X-Rspamd-Queue-Id: 4A0D58020A X-Spamd-Result: default: False [-4.45 / 200.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.993,0]; R_DKIM_ALLOW(-0.20)[gmail.com]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; IP_SCORE(-0.54)[ipnet: 2607:f8b0::/32(-1.24), asn: 15169(-1.39), country: US(-0.08)]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[3.3.d.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.91)[-0.906,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Server: mx1.freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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 16:58:32 -0000 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. On Mon, Nov 5, 2018 at 6:45 PM Matt Joras wrote: > You have to use the sensor_offset to get the actual value at the die. > I believe for all Threadripper chips the offset is -27C. > > Matt > On Mon, Nov 5, 2018 at 3:14 PM Rebecca Cran via freebsd-hackers > wrote: > > > > On Monday, 5 November 2018 14:23:22 MST Zaphod Beeblebrox wrote: > > > > > kldloading "amdtemp.ko" reports an idle temp of 55C or so and heavy > > > compiling (make world -j32) reports temperatures as high as 95C ... > upto > > > and including some instability and/or crash or rebooting. > > > > I have a new Threadripper 2990WX in an ASUS motherboard - and mine just > > reports ridiculous values: > > > > % sysctl dev.amdtemp | grep sensor > > dev.amdtemp.3.core0.sensor0: 112.6C > > dev.amdtemp.3.sensor_offset: 0 > > dev.amdtemp.2.core0.sensor0: 113.5C > > dev.amdtemp.2.sensor_offset: 0 > > dev.amdtemp.1.core0.sensor0: 111.7C > > dev.amdtemp.1.sensor_offset: 0 > > dev.amdtemp.0.core0.sensor0: 114.5C > > dev.amdtemp.0.sensor_offset: 0 > > > > -- > > Rebecca > > > > > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to " > freebsd-hackers-unsubscribe@freebsd.org" >