On Sat, 24 Sep 2011 09:10:17 -0700 (PDT), Audio Phile wrote: > Ah! I didn't read the output carefully. If you notice, the "core id" is what is causing this, nothing wrong with lm-sensors here. Indeed, the unexpected core IDs come straight from /proc/cpuinfo. > We can I think blame HP. Next question would be how to get this on to the lm-sensors wiki so that other HP Z600 users can make this addition to their configs if necessary. What makes you think the system vendor has anything to do with this? I would expect the core IDs to be reported by the CPU itself (someone please correct me if I'm wrong.) > $ grep "core id" cpuinfo.txt > core id : 0 > core id : 1 > core id : 9 > core id : 10 > core id : 0 > core id : 1 > core id : 9 > core id : 10 > core id : 0 > core id : 1 > core id : 9 > core id : 10 > core id : 0 > core id : 1 > core id : 9 > core id : 10 I have no idea if the CPU is just reporting strange values or if the kernel is somehow misbehaving. -- Jean Delvare _______________________________________________ lm-sensors mailing list lm-sensors@xxxxxxxxxxxxxx http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
