[lm-sensors] [3.0 regression?] coretemp driver output has seemingly

[lm-sensors] [3.0 regression?] coretemp driver output has seemingly

[Artem S. Tashkinov]

Hello,

My 3.0-rc4 kernel `sensors` command reports this:

$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +37.0 C  (high = +80.0 C, crit = +99.0 C)
Core 0:         +32.0 C  (high = +80.0 C, crit = +99.0 C)
Core 3:         +32.0 C  (high = +80.0 C, crit = +99.0 C)

Whereas on kernel 2.6.39.x I had four separate cores reported without the
nonsensical "Physicial id 0" item.

I have an Intel Core i5 2500 CPU.

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 42
model name      : Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz
stepping        : 7
cpu MHz         : 1600.000
cache size      : 6144 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 4
apicid          : 0
initial apicid  : 0
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm
constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni
pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1
sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts
tpr_shadow vnmi flexpriority ept vpid
bogomips        : 6603.50
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

***

This problem is tracked at the kernel's bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id8202

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

Re: [lm-sensors] [3.0 regression?] coretemp driver output has

[Guenter Roeck]

On Fri, 2011-06-24 at 15:24 -0400, Artem S. Tashkinov wrote:
> Hello,
> 
> My 3.0-rc4 kernel `sensors` command reports this:
> 
> $ sensors
> coretemp-isa-0000
> Adapter: ISA adapter
> Physical id 0:  +37.0 C  (high = +80.0 C, crit = +99.0 C)
> Core 0:         +32.0 C  (high = +80.0 C, crit = +99.0 C)
> Core 3:         +32.0 C  (high = +80.0 C, crit = +99.0 C)
> 
> Whereas on kernel 2.6.39.x I had four separate cores reported without the
> nonsensical "Physicial id 0" item.
> 
Physical ID 0 is the CPU package temperature and displayed since pkgtemp
and coretemp have been merged into a single driver.

Only question is why Core 1 and Core 2 are not displayed, as the CPU is
not supposed to be hyperthreading and those should be physical cores.
Please provide complete output of /proc/cpuinfo.

Thanks,
Guenter

> I have an Intel Core i5 2500 CPU.
> 
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 42
> model name      : Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz
> stepping        : 7
> cpu MHz         : 1600.000
> cache size      : 6144 KB
> physical id     : 0
> siblings        : 4
> core id         : 0
> cpu cores       : 4
> apicid          : 0
> initial apicid  : 0
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 13
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm
> constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni
> pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1
> sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts
> tpr_shadow vnmi flexpriority ept vpid
> bogomips        : 6603.50
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
> 
> ***
> 
> This problem is tracked at the kernel's bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id8202
> 
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors



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

Re: [lm-sensors] [3.0 regression?] coretemp driver output has

[Guenter Roeck]

Hi Durga,

can you have a look at this ? I am a bit puzzled how it can happen.

Thanks,
Guenter

On Fri, 2011-06-24 at 15:24 -0400, Artem S. Tashkinov wrote:
> Hello,
> 
> My 3.0-rc4 kernel `sensors` command reports this:
> 
> $ sensors
> coretemp-isa-0000
> Adapter: ISA adapter
> Physical id 0:  +37.0 C  (high = +80.0 C, crit = +99.0 C)
> Core 0:         +32.0 C  (high = +80.0 C, crit = +99.0 C)
> Core 3:         +32.0 C  (high = +80.0 C, crit = +99.0 C)
> 
> Whereas on kernel 2.6.39.x I had four separate cores reported without the
> nonsensical "Physicial id 0" item.
> 
> I have an Intel Core i5 2500 CPU.
> 
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 42
> model name      : Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz
> stepping        : 7
> cpu MHz         : 1600.000
> cache size      : 6144 KB
> physical id     : 0
> siblings        : 4
> core id         : 0
> cpu cores       : 4
> apicid          : 0
> initial apicid  : 0
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 13
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm
> constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni
> pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1
> sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts
> tpr_shadow vnmi flexpriority ept vpid
> bogomips        : 6603.50
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management:
> 
> ***
> 
> This problem is tracked at the kernel's bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id8202
> 
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors



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

Re: [lm-sensors] [3.0 regression?] coretemp driver output has

[R, Durgadoss]

Hi Tashkinov,

I am looking into this issue.
Could you please provide us the output of (2)

1)cd /sys/devices/platform/coretemp.0/
2)grep . *

Also, Is you kernel booted with SMP option enabled ?

Thanks,
Durga
> -----Original Message-----
> From: Guenter Roeck [mailto:guenter.roeck@ericsson.com]
> Sent: Tuesday, June 28, 2011 2:15 AM
> To: R@imr4.ericy.com; R, Durgadoss
> Cc: Artem S. Tashkinov; lm-sensors@lm-sensors.org; Yu, Fenghua
> Subject: Re: [lm-sensors] [3.0 regression?] coretemp driver output has
> seemingly broken
> 
> Hi Durga,
> 
> can you have a look at this ? I am a bit puzzled how it can happen.
> 
> Thanks,
> Guenter
> 
> On Fri, 2011-06-24 at 15:24 -0400, Artem S. Tashkinov wrote:
> > Hello,
> >
> > My 3.0-rc4 kernel `sensors` command reports this:
> >
> > $ sensors
> > coretemp-isa-0000
> > Adapter: ISA adapter
> > Physical id 0:  +37.0 C  (high = +80.0 C, crit = +99.0 C)
> > Core 0:         +32.0 C  (high = +80.0 C, crit = +99.0 C)
> > Core 3:         +32.0 C  (high = +80.0 C, crit = +99.0 C)
> >
> > Whereas on kernel 2.6.39.x I had four separate cores reported without the
> > nonsensical "Physicial id 0" item.
> >
> > I have an Intel Core i5 2500 CPU.
> >
> > processor       : 0
> > vendor_id       : GenuineIntel
> > cpu family      : 6
> > model           : 42
> > model name      : Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz
> > stepping        : 7
> > cpu MHz         : 1600.000
> > cache size      : 6144 KB
> > physical id     : 0
> > siblings        : 4
> > core id         : 0
> > cpu cores       : 4
> > apicid          : 0
> > initial apicid  : 0
> > fdiv_bug        : no
> > hlt_bug         : no
> > f00f_bug        : no
> > coma_bug        : no
> > fpu             : yes
> > fpu_exception   : yes
> > cpuid level     : 13
> > wp              : yes
> > flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov
> > pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm
> > constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf pni
> > pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1
> > sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts
> > tpr_shadow vnmi flexpriority ept vpid
> > bogomips        : 6603.50
> > clflush size    : 64
> > cache_alignment : 64
> > address sizes   : 36 bits physical, 48 bits virtual
> > power management:
> >
> > ***
> >
> > This problem is tracked at the kernel's bugzilla:
> https://bugzilla.kernel.org/show_bug.cgi?id8202
> >
> > _______________________________________________
> > lm-sensors mailing list
> > lm-sensors@lm-sensors.org
> > http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> 

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

Re: [lm-sensors] [3.0 regression?] coretemp driver output has

[Artem S. Tashkinov]

> On Jun 28, 2011, R, Durgadoss <durgadoss.r@intel.com> wrote: 
> 
> Hi Tashkinov,
> 
> I am looking into this issue.
> Could you please provide us the output of (2)
> 
> 1)cd /sys/devices/platform/coretemp.0/
> 2)grep . *
> 
> Also, Is you kernel booted with SMP option enabled ?
> 
> Thanks,
> Durga

Please, call me Artem :)

$ cd /sys/devices/platform/coretemp.0/ && grep .*

modalias:platform:coretemp
name:coretemp
temp1_crit:99000
temp1_crit_alarm:0
temp1_input:35000
temp1_label:Physical id 0
temp1_max:80000
temp2_crit:99000
temp2_crit_alarm:0
temp2_input:35000
temp2_label:Core 0
temp2_max:80000
temp3_crit:99000
temp3_crit_alarm:0
temp3_input:35000
temp3_label:Core 1
temp3_max:80000
temp4_crit:99000
temp4_crit_alarm:0
temp4_input:34000
temp4_label:Core 2
temp4_max:80000
temp5_crit:99000
temp5_crit_alarm:0
temp5_input:32000
temp5_label:Core 3
temp5_max:80000
uevent:DRIVER=coretemp
uevent:MODALIAS=platform:coretemp

I don't have any special boot options for my kernel. Like I mentioned in my original e-mail 2.6.39.2 kernel works fine here.

Artem

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

Re: [lm-sensors] [3.0 regression?] coretemp driver output has

[R, Durgadoss]

Hi Artem,


> $ cd /sys/devices/platform/coretemp.0/ && grep .*
> 
> modalias:platform:coretemp
> name:coretemp
> temp1_crit:99000
> temp1_crit_alarm:0
> temp1_input:35000
> temp1_label:Physical id 0
> temp1_max:80000
> temp2_crit:99000
> temp2_crit_alarm:0
> temp2_input:35000
> temp2_label:Core 0
> temp2_max:80000
> temp3_crit:99000
> temp3_crit_alarm:0
> temp3_input:35000
> temp3_label:Core 1
> temp3_max:80000
> temp4_crit:99000
> temp4_crit_alarm:0
> temp4_input:34000
> temp4_label:Core 2
> temp4_max:80000
> temp5_crit:99000
> temp5_crit_alarm:0
> temp5_input:32000
> temp5_label:Core 3
> temp5_max:80000
> uevent:DRIVER=coretemp
> uevent:MODALIAS=platform:coretemp
> 
> I don't have any special boot options for my kernel. Like I mentioned in my
> original e-mail 2.6.39.2 kernel works fine here.
> 

Thanks for the quick help.

For me, it Seems like the driver works fine. The temperature data
is well aligned with the /proc/cpuinfo information you provided.
i.e the sysfs has data for 4 cores.

Do you still see any issues with this data from the sysfs ?
I hope none :-)

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

Re: [lm-sensors] [3.0 regression?] coretemp driver output has

[Guenter Roeck]

On Tue, Jun 28, 2011 at 03:20:58AM -0400, Artem S. Tashkinov wrote:
> > On Jun 28, 2011, R, Durgadoss <durgadoss.r@intel.com> wrote: 
> > 
> > Hi Tashkinov,
> > 
> > I am looking into this issue.
> > Could you please provide us the output of (2)
> > 
> > 1)cd /sys/devices/platform/coretemp.0/
> > 2)grep . *
> > 
> > Also, Is you kernel booted with SMP option enabled ?
> > 
He would not see any secondary CPUs at all if SMP was disabled ...

> > Thanks,
> > Durga
> 
> Please, call me Artem :)
> 
> $ cd /sys/devices/platform/coretemp.0/ && grep .*
> 
> modalias:platform:coretemp
> name:coretemp
> temp1_crit:99000
> temp1_crit_alarm:0
> temp1_input:35000
> temp1_label:Physical id 0
> temp1_max:80000
> temp2_crit:99000
> temp2_crit_alarm:0
> temp2_input:35000
> temp2_label:Core 0
> temp2_max:80000
> temp3_crit:99000
> temp3_crit_alarm:0
> temp3_input:35000
> temp3_label:Core 1
> temp3_max:80000
> temp4_crit:99000
> temp4_crit_alarm:0
> temp4_input:34000
> temp4_label:Core 2
> temp4_max:80000
> temp5_crit:99000
> temp5_crit_alarm:0
> temp5_input:32000
> temp5_label:Core 3
> temp5_max:80000
> uevent:DRIVER=coretemp
> uevent:MODALIAS=platform:coretemp
> 
> I don't have any special boot options for my kernel. Like I mentioned in my original e-mail 2.6.39.2 kernel works fine here.
> 
I start wondering ... do you have any ignore entries for coretemp in /etc/sensors3.conf ?

Or, in other words, what does the system report if you execute "sensors -u"
instead of "sensors" ?

Thanks,
Guenter

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

Re: [lm-sensors] [3.0 regression?] coretemp driver output has

[Artem S. Tashkinov]

On Jun 28, 2011, Guenter Roeck <guenter.roeck@ericsson.com> wrote: 

> I start wondering ... do you have any ignore entries for coretemp in /etc/sensors3.conf ?

> Or, in other words, what does the system report if you execute "sensors -u"
> instead of "sensors" ?

$ sensors -u
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:
  temp1_input: 37.000
  temp1_max: 80.000
  temp1_crit: 99.000
  temp1_crit_alarm: 0.000
Core 0:
  temp2_input: 37.000
  temp2_max: 80.000
  temp2_crit: 99.000
  temp2_crit_alarm: 0.000
Core 3:
  temp5_input: 35.000
  temp5_max: 80.000
  temp5_crit: 99.000
  temp5_crit_alarm: 0.000

nct6776-isa-0290
Adapter: ISA adapter
Vcore:
  in0_input: 0.856
  in0_min: 0.000
  in0_max: 1.744
  in0_alarm: 0.000
in1:
  in1_input: 1.024
  in1_min: 0.000
  in1_max: 0.000
  in1_alarm: 1.000
AVCC:
  in2_input: 3.328
  in2_min: 2.976
  in2_max: 3.632
  in2_alarm: 0.000
+3.3V:
  in3_input: 3.328
  in3_min: 2.976
  in3_max: 3.632
  in3_alarm: 0.000
in4:
  in4_input: 1.008
  in4_min: 0.000
  in4_max: 0.000
  in4_alarm: 1.000
in5:
  in5_input: 2.040
  in5_min: 0.000
  in5_max: 0.000
  in5_alarm: 1.000
3VSB:
  in7_input: 3.424
  in7_min: 2.976
  in7_max: 3.632
  in7_alarm: 0.000
Vbat:
  in8_input: 3.312
  in8_min: 2.704
  in8_max: 3.296
  in8_alarm: 1.000
fan1:
  fan1_input: 0.000
  fan1_min: 0.000
  fan1_alarm: 1.000
fan2:
  fan2_input: 738.000
  fan2_min: 0.000
  fan2_alarm: 1.000
fan3:
  fan3_input: 0.000
  fan3_min: 0.000
  fan3_alarm: 1.000
fan4:
  fan4_input: 0.000
  fan4_min: 0.000
  fan4_alarm: 1.000
fan5:
  fan5_input: 0.000
  fan5_min: 0.000
  fan5_alarm: 1.000
SYSTIN:
  temp1_input: 37.000
  temp1_max: 0.000
  temp1_max_hyst: 0.000
  temp1_alarm: 1.000
  temp1_type: 4.000
CPUTIN:
  temp2_input: -60.000
  temp2_max: 80.000
  temp2_max_hyst: 75.000
  temp2_alarm: 0.000
  temp2_type: 1.000
AUXTIN:
  temp3_input: 39.000
  temp3_max: 80.000
  temp3_max_hyst: 75.000
  temp3_alarm: 0.000
  temp3_type: 4.000
PECI Agent 0:
  temp4_input: 37.000
cpu0_vid:
  cpu0_vid: 2.050

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

Re: [lm-sensors] [3.0 regression?] coretemp driver output has

[Jean Delvare]

Hi Artem,

On Tue, 28 Jun 2011 08:42:40 +0000 (GMT), Artem S. Tashkinov wrote:
> On Jun 28, 2011, Guenter Roeck <guenter.roeck@ericsson.com> wrote: 
> 
> > I start wondering ... do you have any ignore entries for coretemp in /etc/sensors3.conf ?
> 
> > Or, in other words, what does the system report if you execute "sensors -u"
> > instead of "sensors" ?
> 
> $ sensors -u
> coretemp-isa-0000
> Adapter: ISA adapter
> Physical id 0:
>   temp1_input: 37.000
>   temp1_max: 80.000
>   temp1_crit: 99.000
>   temp1_crit_alarm: 0.000
> Core 0:
>   temp2_input: 37.000
>   temp2_max: 80.000
>   temp2_crit: 99.000
>   temp2_crit_alarm: 0.000
> Core 3:
>   temp5_input: 35.000
>   temp5_max: 80.000
>   temp5_crit: 99.000
>   temp5_crit_alarm: 0.000

I would be more interested by the output of:
$ sensors -u -c /dev/null

And if it still doesn't show Core 1 and Core 2, please try again under
strace:

$ strace sensors -u -c /dev/null 2> /tmp/sensors.trace

-- 
Jean Delvare

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

Re: [lm-sensors] [3.0 regression?] coretemp driver output has

[Artem S. Tashkinov]

On Jun 28, 2011, Jean Delvare <khali@linux-fr.org> wrote: 

> I would be more interested by the output of:
> $ sensors -u -c /dev/null
> 
> And if it still doesn't show Core 1 and Core 2, please try again under
> strace:
> 
> $ strace sensors -u -c /dev/null 2> /tmp/sensors.trace

Somehow I had a wrong configuration file which was seemingly ignored under previous kernels. As soon as I removed this file, sensors output has become correct.

I'm terribly sorry for calling a false alert.

Best wishes,

Artem

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

Re: [lm-sensors] [3.0 regression?] coretemp driver output has

[Jean Delvare]

On Tue, 28 Jun 2011 12:45:45 +0000 (GMT), Artem S. Tashkinov wrote:
> On Jun 28, 2011, Jean Delvare <khali@linux-fr.org> wrote: 
> 
> > I would be more interested by the output of:
> > $ sensors -u -c /dev/null
> > 
> > And if it still doesn't show Core 1 and Core 2, please try again under
> > strace:
> > 
> > $ strace sensors -u -c /dev/null 2> /tmp/sensors.trace
> 
> Somehow I had a wrong configuration file which was seemingly ignored under previous kernels. As soon as I removed this file, sensors output has become correct.
> 
> I'm terribly sorry for calling a false alert.

No problem, good thing that your problem is solved.

-- 
Jean Delvare

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

Re: [lm-sensors] [3.0 regression?] coretemp driver output has

[Guenter Roeck]

On Tue, Jun 28, 2011 at 08:13:31AM -0400, Jean Delvare wrote:
> Hi Artem,
> 
> On Tue, 28 Jun 2011 08:42:40 +0000 (GMT), Artem S. Tashkinov wrote:
> > On Jun 28, 2011, Guenter Roeck <guenter.roeck@ericsson.com> wrote: 
> > 
> > > I start wondering ... do you have any ignore entries for coretemp in /etc/sensors3.conf ?
> > 
> > > Or, in other words, what does the system report if you execute "sensors -u"
> > > instead of "sensors" ?
> > 
> > $ sensors -u
> > coretemp-isa-0000
> > Adapter: ISA adapter
> > Physical id 0:
> >   temp1_input: 37.000
> >   temp1_max: 80.000
> >   temp1_crit: 99.000
> >   temp1_crit_alarm: 0.000
> > Core 0:
> >   temp2_input: 37.000
> >   temp2_max: 80.000
> >   temp2_crit: 99.000
> >   temp2_crit_alarm: 0.000
> > Core 3:
> >   temp5_input: 35.000
> >   temp5_max: 80.000
> >   temp5_crit: 99.000
> >   temp5_crit_alarm: 0.000
> 
> I would be more interested by the output of:
> $ sensors -u -c /dev/null
> 
And I thought -u doesn't use the config file. One never stops learning ...

Guenter

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