[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANVEwpYneogzspz525v6beD3ay97rsUFwbJAvFbktb+Tq+UoKg@mail.gmail.com>
Date: Fri, 17 Jan 2020 18:58:19 +0000
From: Ken Moffat <zarniwhoop73@...glemail.com>
To: Guenter Roeck <linux@...ck-us.net>
Cc: linux-hwmon@...r.kernel.org, Clemens Ladisch <clemens@...isch.de>,
Jean Delvare <jdelvare@...e.com>, linux-kernel@...r.kernel.org
Subject: Re: [RFT PATCH 0/4] hwmon: k10temp driver improvements
On Fri, 17 Jan 2020 at 14:14, Guenter Roeck <linux@...ck-us.net> wrote:
>
> On 1/16/20 8:47 PM, Ken Moffat wrote:
> > unfortunately I don't have any report of in0. I'm guessing I need some
> > module(s) which did not seem to do anything useful in the past.
> >
> > All I have in the 'in' area is
> > nct6779-isa-0290
> > Adapter: ISA adapter
> > Vcore: +0.30 V (min = +0.00 V, max = +1.74 V)
> > in1: +0.00 V (min = +0.00 V, max = +0.00 V)
> > AVCC: +3.39 V (min = +0.00 V, max = +0.00 V) ALARM
> > +3.3V: +3.39 V (min = +0.00 V, max = +0.00 V) ALARM
>
> Looks like someone configured /etc/sensors3.conf on that system which tells it
> to report in0 as Vcore. So there is a very clear mismatch. Can you report
> the values seen when the system is under load ?
>
> Thanks,
> Guenter
I do have sensors3.conf from lm_sensors-3.4.0. Here are the figures
under load.
Vcore: +0.65 V (min = +0.00 V, max = +1.74 V)
k10temp-pci-00c3
Adapter: PCI adapter
Vcore: +1.27 V
Vsoc: +0.89 V
Tdie: +46.2°C (high = +70.0°C)
Tctl: +46.2°C
Icore: +48.84 A
Isoc: +10.10 A
ĸen
--
Before the universe began, there was a sound. It went: "One, two, ONE,
two, three, four" [...] The cataclysmic power chord that followed was
the creation of time and space and matter and it does Not Fade Away.
Powered by blists - more mailing lists