Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp5706173pxu; Wed, 23 Dec 2020 03:29:05 -0800 (PST) X-Google-Smtp-Source: ABdhPJzbfCTmjtdSB+DTaEzH5RI6emtWcYT/SaSdUCaaTEY9cZSAh0bJ5ng8btUOs3f4FSqXuDWQ X-Received: by 2002:a05:6402:307c:: with SMTP id bs28mr24514220edb.186.1608722945765; Wed, 23 Dec 2020 03:29:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1608722945; cv=none; d=google.com; s=arc-20160816; b=iQ6N8W5zMk2hyx960cRJPJlby1GYvKTetm4mBFiD6CIAM9gRopErRAETJIzf/EQqYw 4JoGKqhtcWNxn9aaDa58CKU/gcKQTVWIbWNwJY20GPlUrmtZPQBrFcDMdn68qbRoNNhb KCYdyDkCUUebrgL1frI5hX96vz5yLgXUMWXITjPMoAu4ryWBQ/za6bvbmT5ud1goTzSw Se7Zljsa6OtKPgST9INwMdBUZhFQxKgrKnnqI/4pOxroTdOZDKedRZxzmpwIlGZH6zAy yfaauSjsYBPQiNBIYUvVjwgek9I63UYBs+dtI9xfOtbdGM0dLVaAdNWJmnmwQIJPizQT zYmw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=Mq7oGyUGa59E1kgWxLfMA1Jci1ObdTHArjOhZkOa91w=; b=TY1xlnsKWXcCSVel43uS0uppshDPeLlGixc3VRFtzb+icZ+r9BRH/5DSArKYbpJJnE ORJKgYPKmPSZHj+tzH9oQCpYeER0yUmJpm1mNAM6jb/qHN1y8qOuLDNGaQP1/SMpwo/F 4IGHsUyUNFtoxgCd0ftueVIQS+MYU+DCBHgC43DL7YNCU5bNNyOiw7omeuIlFFI8ng4Y 3uHi8il58qIapfUCT0qYAWPYgXDAHYKp9xqSpoSZsw2hLt+K14YOyvC39KCwnFRUIg9Z BuXSl/INY6/iAUCJHw26UW6bK+zu8v9/GyRCkty023KZrGzfNHPl2DJ2DcNLrYhSi8Q8 lk6g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@googlemail.com header.s=20161025 header.b=cgwOvH1f; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=googlemail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id gw24si11426568ejb.715.2020.12.23.03.28.43; Wed, 23 Dec 2020 03:29:05 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@googlemail.com header.s=20161025 header.b=cgwOvH1f; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=googlemail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728474AbgLWL2j (ORCPT + 99 others); Wed, 23 Dec 2020 06:28:39 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35434 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728421AbgLWL2j (ORCPT ); Wed, 23 Dec 2020 06:28:39 -0500 Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9CBE9C0613D3; Wed, 23 Dec 2020 03:27:58 -0800 (PST) Received: by mail-lf1-x129.google.com with SMTP id y19so39175969lfa.13; Wed, 23 Dec 2020 03:27:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Mq7oGyUGa59E1kgWxLfMA1Jci1ObdTHArjOhZkOa91w=; b=cgwOvH1fNHe4eE0bHZQlCVZB/LJlra1wXoDb3tu2t5HFMc/IHOuLNI5MGy6veUtq6D l7GLpFZ8ANgItpF/g7Pfh2zlUsDuTgMuBoaR5EDo4zebl6j8MVxyQ5C1AE5dNdm1/DJv m5BA3qeOR+6+U1PjVMe5cX+OIwMXCJSddBCHLybeHGmuUVhzhkvvFZWslBudY+nKGHt7 ge3MZmEPQqJbqbBYUybFMN+ZDbCkIFv1R8bTFJ8bnK3xrezvPQhl/MwgK7RXo1l3tCsJ usuN3YH563xngmQnHpilwrHcOZQwr6NhjiXZ1eq4Kjk6uNUibpawwfbYmbE5C2nH/DpY OKBQ== 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:content-transfer-encoding; bh=Mq7oGyUGa59E1kgWxLfMA1Jci1ObdTHArjOhZkOa91w=; b=UipJi2/0+NJAhkkpd3tZARVUhgFePw0mXK86l9545lTSLaWunWdf81vPqvTLpy7upf Swd634TYwfxjIXcxiDgxcB9VntTiCCODe2Xok+7QAI629oaV2k0inY/bC+pzn8+QixDr sOslsVBU2GLQQurUxjwNSYBfReMTCgB/9EnM588tGoRLxLWg2GLn/OUeGGezxeiHD9L1 pFQFCAJX1WWyFcnS7KZ5AUdzWWbKF0JhOdog8Eldp1lAHeHLrw2tTb4jpVqIOfKUlsH0 qW+OstQ2tJ4EdPlEaTgBWcLW3mpIviXIcZKRBu5DbhQGOjSH5+vPfu6um6rh5w8KHKCE /iRQ== X-Gm-Message-State: AOAM532bxPwYcUsqoJLWraDJWdZgbUN0anZqtp3ftJHY6sMfos04Tne2 3nY+SIOvtGrDyjyt270HFUNGUPJXHTQ02vU8WQ== X-Received: by 2002:a05:6512:491:: with SMTP id v17mr10245162lfq.148.1608722877158; Wed, 23 Dec 2020 03:27:57 -0800 (PST) MIME-Version: 1.0 References: <9d621d34-e5ce-301a-1b89-92c0791fe348@roeck-us.net> <4483r6o2-245o-147-s71r-s64ss3nqr8ps@vanv.qr> In-Reply-To: <4483r6o2-245o-147-s71r-s64ss3nqr8ps@vanv.qr> From: Gabriel C Date: Wed, 23 Dec 2020 12:27:31 +0100 Message-ID: Subject: Re: k10temp: ZEN3 readings are broken To: Jan Engelhardt Cc: Guenter Roeck , linux-hwmon@vger.kernel.org, LKML , Wei Huang Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Mi., 23. Dez. 2020 um 11:41 Uhr schrieb Jan Engelhardt = : > > > On Tuesday 2020-12-22 04:58, Guenter Roeck wrote: > >On 12/21/20 5:45 PM, Gabriel C wrote: > >> Hello Guenter, > >> > >> while trying to add ZEN3 support for zenpower out of tree modules, I f= ind out > >> the in-kernel k10temp driver is broken with ZEN3 ( and partially ZEN2 = even ). > > > >[...] since I do not have time to actively maintain > >the driver, since each chip variant seems to use different addresses and= scales, > >and since the information about voltages and currents is unpublished by = AMD, > >I'll remove support for voltage/current readings from the upstream drive= r. > > I support that decision. > > /proc/cpuinfo::AMD Ryzen 7 3700X 8-Core Processor, fam 23 model 113 step = 0 > > A synthetic load (perl -e '1 while 1') x 16 shows: > Adapter: PCI adapter > Vcore: +1.28 V > Vsoc: +1.02 V > Tctl: +94.8=C2=B0C > Tdie: +94.8=C2=B0C > Tccd1: +94.8=C2=B0C > Icore: +76.00 A > Isoc: +6.75 A > > A BOINC workload on average: > k10temp-pci-00c3 > Adapter: PCI adapter > Vcore: +1.17 V > Vsoc: +1.02 V > Tctl: +94.9=C2=B0C > Tdie: +94.9=C2=B0C > Tccd1: +95.0=C2=B0C > Icore: +88.00 A > Isoc: +8.00 A > > The BOINC workload, when it momentarily spikes: > Adapter: PCI adapter > Vcore: +1.32 V > Vsoc: +1.02 V > Tctl: +94.1=C2=B0C > Tdie: +94.1=C2=B0C > Tccd1: +96.0=C2=B0C > Icore: +105.00 A > Isoc: +7.75 A > > For a processor sold as a 65 W part, observing reported sensors as > 88 A x 1.17 V + 8 A x 1.02 V =3D 111.12 W just can't be. We are off by a > factor of about 2. Just before I forget, even with 100% correct code you could still be off by a factor of 2 with a broken BIOS or a vendor who is trying to bypass AMD spec limits. See as an example this topic: https://cutt.ly/7h1bT48 Best Regards, Gabriel C