Hi Juerg, hi Antonio, On Sun, 20 Apr 2008 12:00:39 -0700, Juerg Haefliger wrote: > On Sun, Apr 20, 2008 at 1:07 AM, Antonio Exp?sito <aelorenzo at gmail.com> wrote: > > So I decided to restart server because I was making a lot of testing with > > ipmi and sensors last day. > > > > Now, everything is fine (but it is only by now, later we recover the rare > > behaviour): > > > > eye4:~# sensors > > k8temp-pci-00c3 > > Adapter: PCI adapter > > Core0 Temp: +28.0?C > > Core1 Temp: +31.0?C > > > > dme1737-i2c-0-2e > > Adapter: SMBus nForce2 adapter at 1c00 > > V5stby: +2.61 V (min = +0.00 V, max = +6.64 V) > > Vccp: +1.38 V (min = +0.00 V, max = +2.99 V) > > V3.3: +3.38 V (min = +0.00 V, max = +4.38 V) > > > > V5: +5.07 V (min = +0.00 V, max = +6.64 V) > > V12: +11.95 V (min = +0.00 V, max = +15.94 V) > > > > V3.3stby: +3.32 V (min = +0.00 V, max = +4.38 V) > > Vbat: +3.02 V (min = +0.00 V, max = +4.38 V) > > CPU_Fan: 9591 RPM (min = 800 RPM) > > Fan2: 2952 RPM (min = 800 RPM) > > Fan3: 4147 RPM (min = 800 RPM) > > Fan4: 9326 RPM (min = 800 RPM) > > RD1 Temp: +39.2?C (low = -20.0?C, high = +80.0?C) > > Int Temp: +27.2?C (low = -20.0?C, high = +60.0?C) > > CPU Temp: +24.1?C (low = -20.0?C, high = +60.0?C) > > > > cpu0_vid: +1.550 V > > > > > > Only a big temperature offset between k8 and dme drivers, May I calibrate it > > using as reference ipmitool readings? > > Some AMD chips are broken and report incorrect temps via the k8 > driver. You have to ignore those values and trust ipmi or the dme1737 > driver. (...) Broken AMD K8s usually report way weirder temperatures. The ones reported above look relatively sane in comparison. Just because they don't match exactly what the DME1737 reports doesn't mean they are wrong. > > (...) > > Is there any way to know the moduled loading sequence? > > Not that I'm aware of. Watch the log for driver messages. lsmod (and /proc/modules) list the modules in reverse order of loading (i.e. last loaded is listed first, first loaded is listed last.) > > (...) > > AAAAAAAAAAAAAGGGGGGGGGGGGGGGGGG!!!!!!!!!!!!!!!!!! > > > > Same bogus readings, two chips! > > > > Is it random? > > I don't think it's random we just don't know yet what causes this > behavior. My guess is it's the ipmi driver. My own random guess is that the IPMI hardware module is bridging the 2 SMBuses. Maybe the driver is incorrectly instructing it to do so, I really don't know anything about IPMI so I don't know how realistic my guess is. Anyway, using IPMI together with native hardware monitoring drivers doesn't make sense, so I would advise that you just don't do it. -- Jean Delvare
