Ticket #2254 (closed defect: worksforme)

Opened 7 years ago

Last modified 7 years ago

Segmentation fault

Reported by: ticket Owned by: khali
Priority: major Milestone:
Component: sensors Version: 2.10.4
Keywords: Cc: shengmai_goh@…

Description (last modified by khali) (diff)

[root@ALPHASVR01 lm_sensors-2.10.4]# uname -a Linux ALPHASVR01 2.6.9-55.0.6.EL #1 Tue Sep 4 21:10:58 EDT 2007 i686 i686 i386

i successfully installed lm_sensors (and syslibs) and successfully passed sensor-detect state and was asked to add the following...

vi /etc/modprobe.conf :

alias eth0 e100
alias snd-card-0 snd-intel8x0
options snd-card-0 index=0
install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 && /usr/sbin/alsactl restore >/dev/null 2>&1 || :
remove snd-intel8x0 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0
alias usb-controller ehci-hcd
alias usb-controller1 uhci-hcd

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

vi /etc/rc.local :

#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.
#
touch /var/lock/subsys/local
#/home/ntsadmin/radius/run_NTSradius

#----cut here----
modprobe i2c-isa
# Chip drivers
modprobe w83627hf
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----

PROBLEM : I have rebooted the system twice but I'm still getting segmentation fault!

[root@ALPHASVR01 lm_sensors-2.10.4]# sensors
Segmentation fault

Question : how can i get rid of this problem ?

Cheers Goh CentOS 4.4 <-> Redhat 4

Change History

Changed 7 years ago by khali

  • owner changed from somebody to khali
  • status changed from new to assigned
  • description modified (diff)

Which version of sysfsutils did you install? How?

What does "sensors -v" return? We want to make sure that "sensors" is not linking with an older version of the library.

Do you get a core dump on the disk (with "ulimit -c unlimited")? Or a backtrace in the kernel logs?

For a Red Hat system (or equivalent) you can get packages from atrpms.net:
 http://atrpms.net/dist/el4/lm_sensors/
So you don't need to build lm-sensors by yourself.

Changed 7 years ago by ticket

[root@ALPHASVR01 ntsadmin]# sensors -v sensors version 2.10.4 with libsensors version 2.10.4

i don't understand : Do you get a core dump on the disk (with "ulimit -c unlimited")? Or a backtrace in the kernel logs?

currently trying packages from atrpms.net

cheers

Changed 7 years ago by ticket

root@HOST zabbix]# uname -a Linux SINSERVER01 2.6.9-34.EL #1 Wed Mar 8 00:07:35 CST 2006 i686 i686 i386 GNU/Linux

[root@HOST zabbix]# sensors No sensors found!

[root@HOST zabbix]# rpm -ivh --force libsensors3-2.10.4-50.el4.i386.rpm warning: libsensors3-2.10.4-50.el4.i386.rpm: V3 DSA signature: NOKEY, key ID 66534c2b Preparing... ########################################### [100%]

1:libsensors3 ########################################### [100%]

[root@HOST zabbix]# rpm -ivh --force lm_sensors-devel-2.10.4-50.el4.i386.rpm warning: lm_sensors-devel-2.10.4-50.el4.i386.rpm: V3 DSA signature: NOKEY, key ID 66534c2b Preparing... ########################################### [100%]

1:lm_sensors-devel ########################################### [100%]

[root@HOST zabbix]# rpm -ivh --force lm_sensors-2.10.4-50.el4.i386.rpm warning: lm_sensors-2.10.4-50.el4.i386.rpm: V3 DSA signature: NOKEY, key ID 66534c2b Preparing... ########################################### [100%]

1:lm_sensors ########################################### [100%]

[root@HOST zabbix]# sensors No sensors found! Make sure you loaded all the kernel drivers you need. Try sensors-detect to find out which these are.

[root@SINSERVER01 zabbix]# /sbin/sensors-detect

Now follows a summary of the probes I have just done. Just press ENTER to continue:

Driver `lm78' (should be inserted):

Detects correctly:

  • ISA bus, address 0x290 (Busdriver `i2c-isa') Chip `National Semiconductor LM78-J' (confidence: 6)

I will now generate the commands needed to load the required modules. Just press ENTER to continue:

To make the sensors modules behave correctly, add these lines to /etc/modprobe.conf:

#----cut here---- # I2C module options alias char-major-89 i2c-dev #----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here---- modprobe i2c-isa # Chip drivers modprobe lm78 # sleep 2 # optional /usr/bin/sensors -s # recommended #----cut here----

If you have some drivers built into your kernel, the list above will contain too many modules. Skip the appropriate ones! You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until the needed modules are loaded.

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): YES

Question: up to here, i have added into modprobe.conf...BUT the 2nd part, what u mean by "some /etc/rc* file" ??

Changed 7 years ago by ticket

close this ticket.... i managed to get the rpm packages to work on a new system !

thanks dude

[root@HOST bin]# sensors lm78-j-i2c-0-2d Adapter: SMBus PIIX4 adapter at 0540 VCore 1: +1.52 V (min = +1.55 V, max = +0.82 V) ALARM VCore 2: +1.98 V (min = +0.32 V, max = +0.26 V) ALARM +3.3V: +3.26 V (min = +1.58 V, max = +2.40 V) ALARM +5V: +4.89 V (min = +2.61 V, max = +1.51 V) ALARM +12V: +12.04 V (min = +0.79 V, max = +1.95 V) ALARM -12V: -12.13 V (min = -3.56 V, max = -0.22 V) ALARM -5V: -0.00 V (min = -1.54 V, max = -3.08 V) ALARM fan1: 8437 RPM (min = 168750 RPM, div = 2) ALARM fan2: 0 RPM (min = 3409 RPM, div = 2) ALARM fan3: 0 RPM (min = 39705 RPM, div = 2) ALARM temp: +54.0°C (high = +4°C, hyst = +1°C) vid: +3.40 V

Changed 7 years ago by khali

How old is your system? The LM78 is a very old hardware monitoring chip and I would be very surprised to see it used in a recent design. Also, your original report was mentioning the w83627hf driver rather than the lm78 driver. So I'm not sure if the sensors have been properly detected on your system, even though the output of sensors makes some sense. If you unload both the lm78 driver and the w8627hf driver, and run sensors-detect again, and attach the whole output to this bug, I can take a look at it.

Changed 7 years ago by khali

  • status changed from assigned to closed
  • resolution set to worksforme

No answer, closing.

Note: See TracTickets for help on using tickets.