Re: [3.0 regression?] coretemp driver output has seemingly broken

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Artem,

On Tue, 28 Jun 2011 08:42:40 +0000 (GMT), Artem S. Tashkinov wrote:
> On Jun 28, 2011, Guenter Roeck <guenter.roeck@xxxxxxxxxxxx> 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@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors


[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux