From: millerlf@telus.net (lloyd)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] user prog sensors seg faults
Date: Mon, 08 May 2006 13:48:54 +0000 [thread overview]
Message-ID: <445F4C46.8000800@telus.net> (raw)
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,
(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
| > We have a dual Opteron 285 system on a Tyan Tiger K8WE (S2877)
| > motherboard. The make user ; make user_install went fine. The
| > sensor-detect script seemed to run ok and the modprobes seemed to work
| > but the "sensors -s" command segfaults. Is it a 64 bit problem? Using
| > Suse 10.1 x86_64 beta atm.
|
|
| Which version of lm_sensors is this?
2.10.0
| Which beta is this?
10.1 beta 9
> uname -a
Linux wsiopt64 2.6.16-8-smp #1 SMP Tue Mar 28 11:00:06 UTC 2006 x86_64 x86_64 x86_64 GNU/Linux
thanks
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sensors.conf
Url: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060508/3da23e83/sensors-0001.pl
next reply other threads:[~2006-05-08 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 13:48 lloyd [this message]
2006-05-10 3:51 ` [lm-sensors] user prog sensors seg faults Mark M. Hoffman
2006-05-13 22:17 ` Jean Delvare
2006-05-16 6:06 ` lloyd
2006-05-16 6:31 ` lloyd
2006-05-16 21:23 ` Jean Delvare
2006-05-17 3:24 ` Mark M. Hoffman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=445F4C46.8000800@telus.net \
--to=millerlf@telus.net \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.