On Fri June 12 2009, Michael S. Zick wrote: > > The tool does not report read failures. > **BUT** if you remember to "modprobe msr" or have it built in... > Translation: Cockpit error. ;) > > root at cb01:~# for r in 0x1160 0x1161 0x1162 0x1163 0x1164 0x1165 0x1166 0x1167 0x1168 0x1169 0x116a 0x116b 0x116c 0x1152 0x1153 ; do ./rdmsrll $r ; done > MSR register 0x1160 => 00:00:00:00:00:00:05:dc > MSR register 0x1161 => 00:00:00:00:00:00:03:e8 > MSR register 0x1162 => 00:00:00:00:00:00:00:00 > MSR register 0x1163 => 00:00:00:00:00:00:00:00 > MSR register 0x1164 => 00:00:00:00:00:00:00:5f > MSR register 0x1165 => 00:00:00:00:00:00:00:64 > MSR register 0x1166 => 00:00:00:00:00:00:00:7d > MSR register 0x1167 => 00:00:00:00:00:00:00:00 > MSR register 0x1168 => 00:00:00:00:00:00:01:8d > MSR register 0x1169 => 00:00:00:00:00:00:00:32 > MSR register 0x116a => 00:00:00:00:00:00:00:03 > MSR register 0x116b => 00:00:00:00:00:00:01:a6 > MSR register 0x116c => 00:00:00:00:00:00:03:34 > MSR register 0x1152 => e7:2c:b3:9f:fb:ff:ff:ff > MSR register 0x1153 => 04:06:0c:09:fe:ff:ff:ff > > Which is the same data as reported by msr-tools. > And the output of sensors with H.W. driver built-in: root at cb01:~# sensors acpitz-virtual-0 Adapter: Virtual device temp1: +48.8?C (crit = +94.8?C) via-cputemp-isa-0000 Adapter: ISA adapter Core 0: +50.0?C Which looks reasonable to me, on this machine. Mike > Mike
