Sensors - "Is this all I get?"

[Chilly Willy]

OK, no problem, & I wasn't picking on you. (or anyone else) I know you all are trying to help & it's much appreciated.
Just trying to keep from beating a dead horse. (now to figure out why my readouts changed.)

[Chilly Willy]

Any more ideas - anyone?

[Dutchy]

Probably just a kernel update like you said and if so probably way too much digging to do to get to the bottom of it.

[Chilly Willy]

On that hunch I booted into the 3.1.9 kernel & I got my old readout back - booted into both the 3.2.x kernels & get the lesser one, so it IS the kernel. The question now is, what can I do about it? (short of filing a bug report)

[glennzo]

Hope this is relevant. I've been pulling my hair out over sensors issues. Lack of information for my board / CPU. I stumbled across a post that I belive was from the Ubuntu Forum. The poster suggested adding acpi_enforce_resources=lax to /etc/default/grub. I thought it worth a try so I added it to mine.

GRUB_TIMEOUT=30
GRUB_DISTRIBUTOR="Fedora"
GRUB_DEFAULT=saved
GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0  KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8 acpi_enforce_resources=lax"
GRUB_DISABLE_RECOVERY="true"
GRUB_FONT=/boot/grub2/DejaVuSansMono.pf2
GRUB_GFXMODE=1024x768
GRUB_GFXPAYLOAD_LINUX=keep
GRUB_BACKGROUND=/usr/share/backgrounds/verne/default/wide/verne.png

As you can see I just added it to the end of the line. Rebooted and now I have a ton more information than I've had in the past.

[root@phenom16 glenn>$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +40.0°C  (crit = +95.0°C)

it8718-isa-0290
Adapter: ISA adapter
in0:          +1.12 V  (min =  +0.00 V, max =  +4.08 V)
in1:          +1.22 V  (min =  +0.00 V, max =  +4.08 V)
in2:          +3.31 V  (min =  +0.00 V, max =  +4.08 V)
+5V:          +2.96 V  (min =  +0.00 V, max =  +4.08 V)
in4:          +3.02 V  (min =  +0.00 V, max =  +4.08 V)
in5:          +1.84 V  (min =  +0.00 V, max =  +4.08 V)
in6:          +1.22 V  (min =  +0.00 V, max =  +4.08 V)
5VSB:         +2.91 V  (min =  +0.00 V, max =  +4.08 V)
Vbat:         +3.22 V  
fan1:        1155 RPM  (min =    0 RPM)
fan2:           0 RPM  (min =   32 RPM)  ALARM
fan3:           0 RPM  (min =    0 RPM)
temp1:        +46.0°C  (low  = +127.0°C, high = +97.0°C)  sensor = thermal diode
temp2:       +127.0°C  (low  = +127.0°C, high = +97.0°C)  ALARM  sensor = thermistor
temp3:       +127.0°C  (low  = +127.0°C, high = +97.0°C)  ALARM  sensor = thermistor
cpu0_vid:    +0.375 V
intrusion0:  OK

Before the change all I had was the acpitz-virtual-0 section. Nothing else.

I'm sure you need to run grub2-mkconfig -o /boot/grub2/grub.cfg before you reboot.

[marko]

Originally Posted by Chilly Willy

On that hunch I booted into the 3.1.9 kernel & I got my old readout back - booted into both the 3.2.x kernels & get the lesser one, so it IS the kernel. The question now is, what can I do about it? (short of filing a bug report)

Did you re-try with the just released 3.2.7 kernel ? (Built on Feb 20). My guess is we'll see a updated package soon for lm_sensors that will catch up to something that changed in the 3.2 kernel

[Chilly Willy]

MARKO
The 3.2.7 gave the same as 3.2.6

GLENNZO
I tried your suggestion & it DID give me more sensors output,
BUT it also added a bunch of useless (to me) "kernels" in the boot list.
(where you choose which to boot - if this makes sense)
How do I edit those out?


BTW: here is what I get now, so which is my CPU temp? I'm not sure... (I think it is in red)
(from the blue down is new stuff - blue is what I though was CPU on old readout)
--- it would be nice to know what ALL of them are, actually... ---

nouveau-pci-0500
Adapter: PCI adapter
temp1:       +123.8°F  (high = +212.0°F, crit = +221.0°F)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:       +110.1°F  (high = +158.0°F)

f71889ed-isa-0600
Adapter: ISA adapter
+3.3V:        +3.26 V  
in1:          +1.41 V  (max =  +2.04 V)
in2:          +1.10 V  
in3:          +0.96 V  
in4:          +0.69 V  
in5:          +1.29 V  
in6:          +1.57 V  
3VSB:         +3.26 V  
Vbat:         +3.22 V  
fan1:        3432 RPM
fan2:         692 RPM
fan3:         669 RPM
temp1:        +98.6°F  (high = +491.0°F, hyst = +483.8°F)  ALARM (CRIT)
                       (crit = +491.0°F, hyst = +483.8°F)  sensor = transistor
temp2:          FAULT  (high = +491.0°F, hyst = +483.8°F)
                       (crit = +491.0°F, hyst = +483.8°F)  sensor = transistor
temp3:        +84.2°F  (high = +491.0°F, hyst = +487.4°F)  ALARM (CRIT)
                       (crit = +491.0°F, hyst = +487.4°F)  sensor = transistor

[glennzo]

Don't know why that change would add more kernels to the boot menu. I usually create a temp folder under boot and move all but the newest kernel stuff into that folder. Then I rerun grub2-mkconfig. Of course, that's after I've booted into the new kernel a few times to make sure it's working.

[Chilly Willy]

Well I'm totally hosed right now - see my post on it.... (& BTW: its no bad reflection on YOU, so PLEASE don't take it as such)

Also, to fill you in on the problem in this thread, I added that stuff to the end of the line & then ran that command & then rebooted.
I though this was what I was supposed to do, did I do it WRONG? - It way past bedtime, so after a good nights sleep, I'll try to post what that boot list looks like.

Thanks for your help...

[Chilly Willy]

The boot list is as follows: (sorry my camera batteries are dead or I'd post a picture)

kernel 3.2.7
kernel 3.2.7 (recovery mode)
kernel 3.2.6
kernel 3.2.6 (recovery mode)
kernel 3.2.5
kernel 3.2.5 (recovery mode)
Win 7
fedora 14 (on /dev/mapper/ vg_bigtux-lv_root) - this is listed 3 times, same kernel

So it seems that that grub command hooked the F14 & F16 together.

---------- Post added 27th February 2012 at 02:56 AM ---------- Previous post was 26th February 2012 at 07:32 PM ----------

After I get my F16 back up & running, I MAY opt to try this again, but I'd like to know if I did anything wrong first, or at least try to pin down what happened with that list before hand. If all looks OK then I may. It DID give me the readout that I DO want.

[sonoran]

Originally Posted by Chilly Willy

After I get my F16 back up & running, I MAY opt to try this again, but I'd like to know if I did anything wrong first, or at least try to pin down what happened with that list before hand. If all looks OK then I may. It DID give me the readout that I DO want.

http://www.lm-sensors.org/wiki/FAQ/C...inkernel2.6.31

Banging IO-ports of a chip from 2 different drivers, the Linux hwmon driver and the ACPI
code is a really bad idea and can cause all sort of issues (including things like changing CPU / RAM
voltage or clock speed). So the old behaviour was a really bad idea.

So acpi_enforce_resources=lax might or might not fry your cpu or ram modules. The question you have to ask yourself is...
http://www.youtube.com/watch?v=Gmijl...eature=related

[Chilly Willy]

Well, now, isn't THAT interesting! - I have to wonder if this is all interrelated somehow to my corrupted system.

Anyway, given this, I DON'T think I will be retrying it... The whole point of the readout is to KEEP FROM burning up the CPU, not add to it. For ME anyway!

---------- Post added at 11:55 PM ---------- Previous post was at 03:21 PM ----------

Please, I need to know what readout this represents, I thought it was the CPU but I need to know for sure!

 k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +87.8°F  (high = +158.0°F)