Hi lloyd, > I did a debuging link of sensors and got the exact place where it crashes: > > | Program received signal SIGSEGV, Segmentation fault. > | 0x000000000041e910 in sensors_read_one_sysfs_chip (dev=0x550230) > | at lib/sysfs.c:57 > | 57 if (attr->len >= 11 && !strcmp(attr->value + attr->len - 11, This suggests a bug in libsysfs. > (gdb) backtrace > #0 0x000000000041e910 in sensors_read_one_sysfs_chip (dev=0x550230) > at lib/sysfs.c:57 > #1 0x000000000041eb82 in sensors_read_sysfs_chips () at lib/sysfs.c:154 > #2 0x000000000041e609 in sensors_init (input=0x54e6a0) at lib/init.c:45 > #3 0x000000000040210c in main (argc=2, argv=0x7ffffb0a2168) > at prog/sensors/main.c:237 > > > attached is the sensors.conf file generated by sensors-detect Does "sensors -c /dev/null" crash too? If it does, it means that the configuration file is not reponsible. Which hardware monitoring drivers are used? Output of: /sbin/lsmod | grep hwmon cat /sys/class/hwmon/hwmon*/device/name If there are more than one driver, please try each driver individually to see if the crash is related a given driver. > | Which beta is this? > > 10.1 beta 9 Now that 10.1 final is out, I'd suggest that you upgrade to that. -- Jean Delvare
