All of lore.kernel.org
 help / color / mirror / Atom feed
* [lm-sensors] inaccurate fan speed
@ 2013-06-17  4:22 earl middlebrook
  2013-06-17  6:57 ` Jean Delvare
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: earl middlebrook @ 2013-06-17  4:22 UTC (permalink / raw)
  To: lm-sensors


[-- Attachment #1.1: Type: text/plain, Size: 1195 bytes --]

Hello,

I am running Ubuntu 12.04 on a lenovo l512 laptop.  It has been running a
bit hot (to the touch) and since I run it full throttle quite often I
thought I should monitor the hardware more closely.  I installed lm-sensors
from the Software Centre, ran sensors detect (only detected coretemp),
installed psensors and restarted.

The first thing to note is that the temp rarely starts or idles below 60C.
The second, and most apparent, is that the fan speed indicated is obviously
erroneous.  It hovers around 790 when idling and when it is very hot (core
~95C) it drops to 550.  The fan is obviously spinning up a little, but
still not as fast as i would expect for a computer about to light itself on
fire.  If you look at the temp and fan speed graph generated by Psensors,
there seems to be a strong negative correlation.  This leads me to think
that at least the fan if not all the sensor outputs are off by some
factor.

If you have heard of this problem or know a fix let me know.  I would be
happy to provide any more details.  Although I dont know where the relevant
data is dumped.

Thanks in advance!
Earl

-- 
Earl Middlebrook
Potts Lab
University of Utah
Lab phone 801 585 9678

[-- Attachment #1.2: Type: text/html, Size: 1422 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [lm-sensors] inaccurate fan speed
  2013-06-17  4:22 [lm-sensors] inaccurate fan speed earl middlebrook
@ 2013-06-17  6:57 ` Jean Delvare
  2013-06-21 10:16 ` Jean Delvare
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: Jean Delvare @ 2013-06-17  6:57 UTC (permalink / raw)
  To: lm-sensors

Hi Earl,

On Sun, 16 Jun 2013 22:22:00 -0600, earl middlebrook wrote:
> I am running Ubuntu 12.04 on a lenovo l512 laptop.  It has been running a
> bit hot (to the touch) and since I run it full throttle quite often I
> thought I should monitor the hardware more closely.  I installed lm-sensors
> from the Software Centre, ran sensors detect (only detected coretemp),
> installed psensors and restarted.
> 
> The first thing to note is that the temp rarely starts or idles below 60C.
> The second, and most apparent, is that the fan speed indicated is obviously
> erroneous.

The coretemp driver only reports temperatures, not fan speed. So you
must have another driver already loaded which reports the fan speed. On
a Lenovo laptop it may be the thinkpad_acpi driver. Please show us the
complete output of sensors so we get a better idea of which drivers are
used and what they do report. Please also tell us what kernel version
you are running.

>  It hovers around 790 when idling and when it is very hot (core
> ~95C) it drops to 550.  The fan is obviously spinning up a little, but
> still not as fast as i would expect for a computer about to light itself on
> fire.  If you look at the temp and fan speed graph generated by Psensors,
> there seems to be a strong negative correlation.  This leads me to think
> that at least the fan if not all the sensor outputs are off by some
> factor.

Please check in the BIOS if you can change settings related to thermal
management or fan speed control.

> If you have heard of this problem or know a fix let me know.  I would be
> happy to provide any more details.  Although I dont know where the relevant
> data is dumped.

I had not heard of this before, but searching bugzilla.kernel.org for
similar cases I found this report:
https://bugzilla.kernel.org/show_bug.cgi?id'792

The good news is that you're not alone. The bad news is that this bug
report is getting old but the bug is still not fixed, apparently it's a
difficult one.

Henrique, as the maintainer of the thinkpad_acpi driver, is there
anything you can do to help, or is the problem outside your
jurisdiction?

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [lm-sensors] inaccurate fan speed
  2013-06-17  4:22 [lm-sensors] inaccurate fan speed earl middlebrook
  2013-06-17  6:57 ` Jean Delvare
@ 2013-06-21 10:16 ` Jean Delvare
  2013-06-28 14:34 ` earl middlebrook
  2013-06-29 12:04 ` Jean Delvare
  3 siblings, 0 replies; 5+ messages in thread
From: Jean Delvare @ 2013-06-21 10:16 UTC (permalink / raw)
  To: lm-sensors

SGkgRWFybCwKClBsZWFzZSBrZWVwIHRoZSBsaXN0IGluY2x1ZGVkLCBzbyB0aGF0IHlvdXIgbWVz
c2FnZXMgZ2V0IGFyY2hpdmVkLgoKT24gTW9uLCAxNyBKdW4gMjAxMyAxMjoyMToxNCAtMDYwMCwg
ZWFybCBtaWRkbGVicm9vayB3cm90ZToKPiBVYnVudHUgZGlkIGhhdmUgdGhpbmtwYWQtYWNwaSBy
dW5uaW5nLiAgSSBibGFja2xpc3RlZCBpdCBhcyBzdWdnZXN0ZWQgYnkKPiBIZW5yaXF1ZS4gIE5v
dyB0aGUgb3V0cHV0IG9mIHNlbnNvcnMgaXM6Cj4gZWFybEBFbEZ1dHVyb1tlYXJsXQo+IHNlbnNv
cnMgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFsx
MTozMUFNXQo+IGFjcGl0ei12aXJ0dWFsLTAKPiBBZGFwdGVyOiBWaXJ0dWFsIGRldmljZQo+IHRl
bXAxOiAgICAgICAgKzcwLjDCsEMgIChjcml0ID0gKzEwNS4wwrBDKQo+IAo+IGNvcmV0ZW1wLWlz
YS0wMDAwCj4gQWRhcHRlcjogSVNBIGFkYXB0ZXIKPiBDb3JlIDA6ICAgICAgICs2MS4wwrBDICAo
aGlnaCA9ICs5NS4wwrBDLCBjcml0ID0gKzEwNS4wwrBDKQo+IENvcmUgMjogICAgICAgKzY0LjDC
sEMgIChoaWdoID0gKzk1LjDCsEMsIGNyaXQgPSArMTA1LjDCsEMpCj4gCj4gVGhpcyBzZWVtcyBt
dWNoIG1vcmUgcmVhc29uYWJsZS4gIE1hbnkgb2YgdGhlIHRlbXBzIGRldGVjdGVkIGJ5Cj4gdGhp
bmtwYWQtYWNwaSB3ZXJlIDBDIG9mIGZsdWN0dWF0aW5nIG9mZiB0aGUgY2hhcnRzLgo+IFRoZSBj
b3JlcyB0ZW1wcyBhcmUgYXBwcm94aW1hdGVseSB0aGUgc2FtZSBhcyBiZWZvcmUuICBUaGV5IGZs
dWN0dWF0ZQo+IGZhc3RlciB0aG91Z2guICBTb21ldGhpbmcgYWJvdXQgdGhlIHVwZGF0ZSByYXRl
IEkgc3VwcG9zZS4KClRoZSBjb3JldGVtcCBkcml2ZXIgdXBkYXRlcyBpdHMgdmFsdWVzIGV2ZXJ5
IHNlY29uZCwgYW5kIHRoZXNlCmludGVncmF0ZWQgZGlnaXRhbCBzZW5zb3JzIGFyZSB2ZXJ5IHBy
b21wdCB0byByZWZsZWN0IHRlbXBlcmF0dXJlCmNoYW5nZXMuCgpUaGUgdmFsdWVzIGFyZSByZWxh
dGl2ZWx5IGhpZ2ggYnV0IHN0aWxsIHJlYXNvbmFibGU6IHRoZXJtYWwgbWFyZ2luIGlzCjMxwrBD
IChub3QgYWN0dWFsIGRlZ3JlZXMgQ2Vsc2l1cyBCVFcsIGJ1dCBjbG9zZSBlbm91Z2guKQoKSSBh
c3N1bWUgdGhlIGFib3ZlIGFyZSBpZGxlIHRlbXBlcmF0dXJlcyB0aG91Z2gsIHlvdSBzaG91bGQg
d29ycnkgaWYKdGhlIHRlbXBlcmF0dXJlcyBnbyB0b28gaGlnaCB3aGVuIHRoZSBtYWNoaW5lIGlz
IHVuZGVyIGxvYWQuCgo+ID4gKC4uLikKPiA+IEkgaGFkIG5vdCBoZWFyZCBvZiB0aGlzIGJlZm9y
ZSwgYnV0IHNlYXJjaGluZyBidWd6aWxsYS5rZXJuZWwub3JnIGZvcgo+ID4gc2ltaWxhciBjYXNl
cyBJIGZvdW5kIHRoaXMgcmVwb3J0Ogo+ID4gaHR0cHM6Ly9idWd6aWxsYS5rZXJuZWwub3JnL3No
b3dfYnVnLmNnaT9pZD0yNzc5Mgo+ID4KPiA+IFRoZSBnb29kIG5ld3MgaXMgdGhhdCB5b3UncmUg
bm90IGFsb25lLiBUaGUgYmFkIG5ld3MgaXMgdGhhdCB0aGlzIGJ1Zwo+ID4gcmVwb3J0IGlzIGdl
dHRpbmcgb2xkIGJ1dCB0aGUgYnVnIGlzIHN0aWxsIG5vdCBmaXhlZCwgYXBwYXJlbnRseSBpdCdz
IGEKPiA+IGRpZmZpY3VsdCBvbmUuCj4gCj4gSXQgZG9lcyBsb29rIGxpa2UgaXQgaXMgbm90IGdl
dHRpbmcgbXVjaCBhdHRlbnRpb24gYW55IG1vcmUuLi4KClRoYXQncyByaWdodC4gSSd2ZSBhZGRl
ZCBhIGNvbW1lbnQgcG9pbnRpbmcgdG8geW91ciByZXBvcnQuCgo+IEkgZG9udCB1bmRlcnN0YW5k
IG11Y2ggb2Ygd2hhdCBpcyBnb2luZyBvbiBidXQgaXQgc291bmRzIGRpZmZlcmVudCB0aGFuIG15
Cj4gcHJvYmxlbSwgYXQgbGVhc3Qgb24gdGhlIHN1cmZhY2UuICBGb3IgaW5zdGFuY2UsIEkgaGF2
ZSBubyBwcm9ibGVtcyB3aXRoCj4gdGhlIGJ1dHRvbnMgYW5kIHRoZSB0ZW1wcyBzZWVtIHN0cmFu
Z2UgZXZlbiBhZnRlciBhIGNvbGQgYm9vdC4KClllcywgSSBoYXZlIG5vdGljZWQgdGhlc2UgZGlm
ZmVyZW5jZXMgdG9vLCBidXQgSSBzdGlsbCBzdXNwZWN0IGEgY29tbW9uCnJvb3QgY2F1c2UuCgo+
ID4gSSdkIHJlY29tbWVuZCBibGFja2xpc3RpbmcgdGhpbmtwYWQtYWNwaSBhbmQgZG9pbmcgYSBm
dWxsIGNvbGQgYm9vdCBvZiB0aGUKPiA+IGJveCAocmVtb3ZlIGFsbCBiYXR0ZXJpZXMgYW5kIEFD
LCBwdXNoIHBvd2VyIGJ1dHRvbiBhdCBsZWFzdCB0ZW4gdGltZXMgZm9yCj4gPiBhdCBsZWFzdCB0
aHJlZSBzZWNvbmRzIGVhY2gsIGFuZCB0aGUgbGFzdCBvbmUgZm9yIGF0IGxlYXN0IDE1IHNlY29u
ZHMpLCB0bwo+ID4gbWFrZSBzdXJlIHRoaW5rcGFkLWFjcGkgaXMgbm90IGFjdHVhbGx5IG1ha2lu
ZyBtYXR0ZXJzIHdvcnNlLgo+IAo+IERvbmUuICBJdCByZW1vdmVzIG5vbi1zZW5zZSBzZW5zb3Ig
cmVhZGluZ3MuICBDUFUgc3RpbGwgbG9va3MgdmVyeSBob3QuCj4gVGhlIGFib3ZlIHNlbnNvcnMg
b3V0cHV0IHdhcyB3aXRoIG9ubHkgZmlyZWZveCB1cC4KPiAKPiA+IFRoYXQgc2FpZCwgdXN1YWxs
eSB0aGVzZSBib3hlcyB3b3JrIHRocm91Z2ggdGhlIHN0YW5kYXJkIEFDUEkgaW50ZXJmYWNlLCBh
bmQKPiA+IHRoZXkgX3JlYWxseV8gZGVwZW5kIG9uIEdQVSBhbmQgQ1BVIHRocm90dGxpbmcvY2xv
Y2svdm9sdGFnZSBjb250cm9sIHRvIGtlZXAKPiA+IGNvb2wuICBFc3BlY2lhbGx5IGlmIHRoZSBi
b3ggaGFzIGEgY3JhY2tlZCB0aGVybWFsIGludGVyZmFjZSBvciBzb21lIG90aGVyCj4gPiBkZWZl
Y3QuCj4gCj4gSXMgdGhpcyBqdXN0IGEgbWF0dGVyIG9mIGdldHRpbmcgaW4gdGhlcmUgYW5kIGhh
dmluZyBhIGxvb2s/CgpGaXJzdCB5b3Ugc2hvdWxkIGVuc3VyZSB0aGF0IGFsbCBwb3dlciBzYXZp
bmcgb3B0aW9ucyBhcmUgZW5hYmxlZC4KCkZvciB0aGUgQ1BVLCB0aGVzZSBhcmUgQyBzdGF0ZXMg
YW5kIGNwdWZyZXEgKGFsdGhvdWdoIHRoZSB1c2VmdWxuZXNzIG9mCmNwdWZyZXEgd2l0aCBnb29k
IEMgc3RhdGVzIGNhbiBiZSBkaXNjdXNzZWQuKSBQbGVhc2UgaW5zdGFsbCBwb3dlcnRvcCwKdGhl
biBjaGVjayB0aGUgSWRsZSBzdGF0cyBhbmQgRnJlcXVlbmN5IHN0YXRzIHBhbmVscyAodXNlIHRo
ZSBUYWIga2V5CnRvIG5hdmlnYXRlIGJldHdlZW4gdGhlc2UgaW4gcmVjZW50IHZlcnNpb25zIG9m
IHBvd2VydG9wLikgWW91IHNob3VsZApzZWUgbXVsdGlwbGUgQyBzdGF0ZXMgaW4gdGhlIGZpcnN0
IGFuZCBtdWx0aXBsZSBmcmVxdWVuY2llcyBpbiB0aGUKc2Vjb25kLgoKV2hlbiB0aGUgbWFjaGlu
ZSBpcyBpZGxlLCB0aGUgQ1BVIHNob3VsZCBzcGVuZCBtb3N0IG9mIHRoZSB0aW1lIGF0IHRoZQps
b3dlc3QgQyBzdGF0ZXMgYW5kIHRoZSBsb3dlc3QgZnJlcXVlbmN5LiBJZiB0aGlzIGlzbid0IHRo
ZSBjYXNlIHRoZW4Kc29tZXRoaW5nIGlzIHdyb25nLCBlaXRoZXIgaW4gdGhlIEJJT1Mgb3IgaW4g
dGhlIGtlcm5lbC4KCllvdSBtYXkgYWxzbyBjaGVjayB0aGUgcG93ZXIgbWFuYWdlbWVudCBvZiB0
aGUgZ3JhcGhpY3MgY2hpcC4gQnV0IHRoYXQKZGVwZW5kcyBhIGxvdCBvbiB3aGljaCBncmFwaGlj
cyBjaGlwIHlvdSBoYXZlIGFuZCB3aGljaCBkcml2ZXIgeW91IHVzZQpmb3IgaXQuCgo+ID4gV2Ug
cmVhbGx5IG5lZWQgYSBkdW1wIG9mIHRoZSBrZXJuZWwgYm9vdCBtZXNzYWdlcyB0byBrbm93IG1v
cmUuCj4gCj4gQ291bGQgeW91IGRpcmVjdCBtZSB0byB3aGVyZSB0aGlzIGlzIGxvY2F0ZWQgc28g
SSBtYXkgcGFzcyBpdCBhbG9uZz8KClJpZ2h0IGFmdGVyIGJvb3QsIGp1c3QgZG86CiQgZG1lc2cg
PiAvdG1wL2RtZXNnLnR4dApBbmQgc2hhcmUgdGhlIGZpbGUgd2l0aCB1cyAoc2VuZCBpdCB2aWEg
cHJpdmF0ZSBlLW1haWwgb3IgcG9zdCBpdCB0bwpzb21lIHBhc3RlYmluIHNpdGUuKQoKLS0gCkpl
YW4gRGVsdmFyZQoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18KbG0tc2Vuc29ycyBtYWlsaW5nIGxpc3QKbG0tc2Vuc29yc0BsbS1zZW5zb3JzLm9yZwpodHRw
Oi8vbGlzdHMubG0tc2Vuc29ycy5vcmcvbWFpbG1hbi9saXN0aW5mby9sbS1zZW5zb3Jz

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [lm-sensors] inaccurate fan speed
  2013-06-17  4:22 [lm-sensors] inaccurate fan speed earl middlebrook
  2013-06-17  6:57 ` Jean Delvare
  2013-06-21 10:16 ` Jean Delvare
@ 2013-06-28 14:34 ` earl middlebrook
  2013-06-29 12:04 ` Jean Delvare
  3 siblings, 0 replies; 5+ messages in thread
From: earl middlebrook @ 2013-06-28 14:34 UTC (permalink / raw)
  To: lm-sensors


[-- Attachment #1.1: Type: text/plain, Size: 7622 bytes --]

Hi all,

Sorry for the delay in responce, work conference...


On Fri, Jun 21, 2013 at 4:16 AM, Jean Delvare <khali@linux-fr.org> wrote:

> Hi Earl,
>
> Please keep the list included, so that your messages get archived.
>
> On Mon, 17 Jun 2013 12:21:14 -0600, earl middlebrook wrote:
> > Ubuntu did have thinkpad-acpi running.  I blacklisted it as suggested by
> > Henrique.  Now the output of sensors is:
> > earl@ElFuturo[earl]
> > sensors                                                     [11:31AM]
> > acpitz-virtual-0
> > Adapter: Virtual device
> > temp1:        +70.0°C  (crit = +105.0°C)
> >
> > coretemp-isa-0000
> > Adapter: ISA adapter
> > Core 0:       +61.0°C  (high = +95.0°C, crit = +105.0°C)
> > Core 2:       +64.0°C  (high = +95.0°C, crit = +105.0°C)
> >
> > This seems much more reasonable.  Many of the temps detected by
> > thinkpad-acpi were 0C of fluctuating off the charts.
> > The cores temps are approximately the same as before.  They fluctuate
> > faster though.  Something about the update rate I suppose.
>
> The coretemp driver updates its values every second, and these
> integrated digital sensors are very prompt to reflect temperature
> changes.
>
> The values are relatively high but still reasonable: thermal margin is
> 31°C (not actual degrees Celsius BTW, but close enough.)
>
I assume the above are idle temperatures though, you should worry if
> the temperatures go too high when the machine is under load.
>
> > > (...)
> > > I had not heard of this before, but searching bugzilla.kernel.org for
> > > similar cases I found this report:
> > > https://bugzilla.kernel.org/show_bug.cgi?id=27792
> > >
> > > The good news is that you're not alone. The bad news is that this bug
> > > report is getting old but the bug is still not fixed, apparently it's a
> > > difficult one.
> >
> > It does look like it is not getting much attention any more...
>
> That's right. I've added a comment pointing to your report.
>
> > I dont understand much of what is going on but it sounds different than
> my
> > problem, at least on the surface.  For instance, I have no problems with
> > the buttons and the temps seem strange even after a cold boot.
>
> Yes, I have noticed these differences too, but I still suspect a common
> root cause.
>
> > > I'd recommend blacklisting thinkpad-acpi and doing a full cold boot of
> the
> > > box (remove all batteries and AC, push power button at least ten times
> for
> > > at least three seconds each, and the last one for at least 15
> seconds), to
> > > make sure thinkpad-acpi is not actually making matters worse.
> >
> > Done.  It removes non-sense sensor readings.  CPU still looks very hot.
> > The above sensors output was with only firefox up.
> >
> > > That said, usually these boxes work through the standard ACPI
> interface, and
> > > they _really_ depend on GPU and CPU throttling/clock/voltage control
> to keep
> > > cool.  Especially if the box has a cracked thermal interface or some
> other
> > > defect.
> >
> > Is this just a matter of getting in there and having a look?
>
> First you should ensure that all power saving options are enabled.
>
> For the CPU, these are C states and cpufreq (although the usefulness of
> cpufreq with good C states can be discussed.) Please install powertop,
> then check the Idle stats and Frequency stats panels (use the Tab key
> to navigate between these in recent versions of powertop.) You should
> see multiple C states in the first and multiple frequencies in the
> second.
>
> When the machine is idle, the CPU should spend most of the time at the
> lowest C states and the lowest frequency. If this isn't the case then
> something is wrong, either in the BIOS or in the kernel.
>

Here are Idle stats from PowerTOP:

**  Package              |             Core          |             CPU
0               CPU 2
                             |                             | C0 active
4.5%                0.5%
                             |                             | POLL
0.0%    0.0 ms      0.0%    0.0 ms
                             |                             | C1-NHM
0.0%    0.0 ms      0.0%    0.0 ms
C3 (pc3)   16.9%    | C3 (cc3)   15.0%    | C3-NHM      3.8%    0.9 ms
12.8%   32.3 ms
C6 (pc6)   59.9%    | C6 (cc6)   76.3%    | C6-NHM     89.3%    3.7 ms
86.3%    4.0 ms

                             |             Core          |             CPU
1               CPU 3
                             |                              | C0 active
1.6%                0.9%
                             |                              | POLL
0.0%    0.0 ms      0.0%    0.0 ms
                             |                              | C1-NHM
0.0%    0.0 ms      0.0%    0.0 ms
                             | C3 (cc3)    8.5%      | C3-NHM      4.3%
1.1 ms      5.3%    2.3 ms
                             | C6 (cc6)   86.0%     | C6-NHM     92.7%
3.3 ms     93.2%    3.3 ms


Here are Frequency Stats:

Package |             Core    |            CPU 0       CPU 2
                    |                     | Actual    2.0 Ghz     1.8 Ghz
Turbo Mode  14.8%   | Turbo Mode  12.8%   | Turbo Mode  12.5%        5.3%
2.40 Ghz     0.0%   | 2.40 Ghz     0.0%   | 2.40 Ghz     0.0%        0.0%
2.27 Ghz     0.1%   | 2.27 Ghz     0.1%   | 2.27 Ghz     0.1%        0.0%
2.14 Ghz     0.0%   | 2.14 Ghz     0.0%   | 2.14 Ghz     0.0%        0.0%
2.00 Ghz     0.0%   | 2.00 Ghz     0.0%   | 2.00 Ghz     0.0%        0.0%
1.87 Ghz     0.0%   | 1.87 Ghz     0.0%   | 1.87 Ghz     0.0%        0.0%
1.74 Ghz     0.9%   | 1.74 Ghz     0.6%   | 1.74 Ghz     0.5%        0.3%
1.60 Ghz     0.0%   | 1.60 Ghz     0.0%   | 1.60 Ghz     0.0%        0.0%
1466 Mhz     0.0%   | 1466 Mhz     0.0%   | 1466 Mhz     0.0%        0.0%
1333 Mhz     0.1%   | 1333 Mhz     0.0%   | 1333 Mhz     0.0%        0.0%

                    |             Core    |            CPU 1       CPU 3
                    |                     | Actual    1.8 Ghz     1.8 Ghz
                    | Turbo Mode  10.9%   | Turbo Mode  10.2%        8.7%
                    | 2.40 Ghz     0.0%   | 2.40 Ghz     0.0%        0.0%
                    | 2.27 Ghz     0.1%   | 2.27 Ghz     0.1%        0.0%
                    | 2.14 Ghz     0.0%   | 2.14 Ghz     0.0%        0.0%
                    | 2.00 Ghz     0.0%   | 2.00 Ghz     0.0%        0.0%
                    | 1.87 Ghz     0.0%   | 1.87 Ghz     0.0%        0.0%
                    | 1.74 Ghz     0.8%   | 1.74 Ghz     0.8%        0.8%
                    | 1.60 Ghz     0.0%   | 1.60 Ghz     0.0%        0.0%
                    | 1466 Mhz     0.0%   | 1466 Mhz     0.0%        0.0%
                    | 1333 Mhz     0.1%   | 1333 Mhz     0.0%        0.0%

Noticed this in Tunables:
>> Good          Using 'ondemand' cpufreq governor

Could I try to toggle it and see if there is a conflict?



> You may also check the power management of the graphics chip. But that
> depends a lot on which graphics chip you have and which driver you use
> for it.
>
> > > We really need a dump of the kernel boot messages to know more.
> >
> > Could you direct me to where this is located so I may pass it along?
>
> Right after boot, just do:
> $ dmesg > /tmp/dmesg.txt
> And share the file with us (send it via private e-mail or post it to
> some pastebin site.)
>
> Private E-mail on the way.

> --
> Jean Delvare
>



-- 
Earl Middlebrook
Potts Lab
University of Utah
Lab phone 801 585 9678

[-- Attachment #1.2: Type: text/html, Size: 9482 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [lm-sensors] inaccurate fan speed
  2013-06-17  4:22 [lm-sensors] inaccurate fan speed earl middlebrook
                   ` (2 preceding siblings ...)
  2013-06-28 14:34 ` earl middlebrook
@ 2013-06-29 12:04 ` Jean Delvare
  3 siblings, 0 replies; 5+ messages in thread
From: Jean Delvare @ 2013-06-29 12:04 UTC (permalink / raw)
  To: lm-sensors

Hi Earl,

On Fri, 28 Jun 2013 08:34:26 -0600, earl middlebrook wrote:
> On Fri, Jun 21, 2013 at 4:16 AM, Jean Delvare <khali@linux-fr.org> wrote:
> > First you should ensure that all power saving options are enabled.
> >
> > For the CPU, these are C states and cpufreq (although the usefulness of
> > cpufreq with good C states can be discussed.) Please install powertop,
> > then check the Idle stats and Frequency stats panels (use the Tab key
> > to navigate between these in recent versions of powertop.) You should
> > see multiple C states in the first and multiple frequencies in the
> > second.
> >
> > When the machine is idle, the CPU should spend most of the time at the
> > lowest C states and the lowest frequency. If this isn't the case then
> > something is wrong, either in the BIOS or in the kernel.
> 
> Here are Idle stats from PowerTOP:
> 
> **  Package              |             Core          |             CPU
> 0               CPU 2
>                              |                             | C0 active
> 4.5%                0.5%
>                              |                             | POLL
> 0.0%    0.0 ms      0.0%    0.0 ms
>                              |                             | C1-NHM
> 0.0%    0.0 ms      0.0%    0.0 ms
> C3 (pc3)   16.9%    | C3 (cc3)   15.0%    | C3-NHM      3.8%    0.9 ms
> 12.8%   32.3 ms
> C6 (pc6)   59.9%    | C6 (cc6)   76.3%    | C6-NHM     89.3%    3.7 ms
> 86.3%    4.0 ms
> 
>                              |             Core          |             CPU
> 1               CPU 3
>                              |                              | C0 active
> 1.6%                0.9%
>                              |                              | POLL
> 0.0%    0.0 ms      0.0%    0.0 ms
>                              |                              | C1-NHM
> 0.0%    0.0 ms      0.0%    0.0 ms
>                              | C3 (cc3)    8.5%      | C3-NHM      4.3%
> 1.1 ms      5.3%    2.3 ms
>                              | C6 (cc6)   86.0%     | C6-NHM     92.7%
> 3.3 ms     93.2%    3.3 ms

This looks reasonable, most time is spent in deepest C state (C6.)

> Here are Frequency Stats:
> 
> Package |             Core    |            CPU 0       CPU 2
>                     |                     | Actual    2.0 Ghz     1.8 Ghz
> Turbo Mode  14.8%   | Turbo Mode  12.8%   | Turbo Mode  12.5%        5.3%
> 2.40 Ghz     0.0%   | 2.40 Ghz     0.0%   | 2.40 Ghz     0.0%        0.0%
> 2.27 Ghz     0.1%   | 2.27 Ghz     0.1%   | 2.27 Ghz     0.1%        0.0%
> 2.14 Ghz     0.0%   | 2.14 Ghz     0.0%   | 2.14 Ghz     0.0%        0.0%
> 2.00 Ghz     0.0%   | 2.00 Ghz     0.0%   | 2.00 Ghz     0.0%        0.0%
> 1.87 Ghz     0.0%   | 1.87 Ghz     0.0%   | 1.87 Ghz     0.0%        0.0%
> 1.74 Ghz     0.9%   | 1.74 Ghz     0.6%   | 1.74 Ghz     0.5%        0.3%
> 1.60 Ghz     0.0%   | 1.60 Ghz     0.0%   | 1.60 Ghz     0.0%        0.0%
> 1466 Mhz     0.0%   | 1466 Mhz     0.0%   | 1466 Mhz     0.0%        0.0%
> 1333 Mhz     0.1%   | 1333 Mhz     0.0%   | 1333 Mhz     0.0%        0.0%
> 
>                     |             Core    |            CPU 1       CPU 3
>                     |                     | Actual    1.8 Ghz     1.8 Ghz
>                     | Turbo Mode  10.9%   | Turbo Mode  10.2%        8.7%
>                     | 2.40 Ghz     0.0%   | 2.40 Ghz     0.0%        0.0%
>                     | 2.27 Ghz     0.1%   | 2.27 Ghz     0.1%        0.0%
>                     | 2.14 Ghz     0.0%   | 2.14 Ghz     0.0%        0.0%
>                     | 2.00 Ghz     0.0%   | 2.00 Ghz     0.0%        0.0%
>                     | 1.87 Ghz     0.0%   | 1.87 Ghz     0.0%        0.0%
>                     | 1.74 Ghz     0.8%   | 1.74 Ghz     0.8%        0.8%
>                     | 1.60 Ghz     0.0%   | 1.60 Ghz     0.0%        0.0%
>                     | 1466 Mhz     0.0%   | 1466 Mhz     0.0%        0.0%
>                     | 1333 Mhz     0.1%   | 1333 Mhz     0.0%        0.0%

On my own system there is a last line, "Idle", where most time is
spent. I am surprised you don't have it. The total is way less than
100% so I can only guess that the rest of the time is spent in Idle
state. If this is the case then it's all OK.

> Noticed this in Tunables:
> >> Good          Using 'ondemand' cpufreq governor
> 
> Could I try to toggle it and see if there is a conflict?

No, that's the other way around. "Good" means that powertop thinks this
is a good thing with regards to power consumption (and I would agree,
even though deep C states save more power than frequency scaling on
recent Intel CPU.) The lines you should investigate are the "bad" ones. I
have many of these on my own system, BTW :(

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2013-06-29 12:04 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-06-17  4:22 [lm-sensors] inaccurate fan speed earl middlebrook
2013-06-17  6:57 ` Jean Delvare
2013-06-21 10:16 ` Jean Delvare
2013-06-28 14:34 ` earl middlebrook
2013-06-29 12:04 ` Jean Delvare

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.