All of lore.kernel.org
 help / color / mirror / Atom feed
From: millerlf@telus.net (lloyd)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] lm-sensors Digest, Vol 12, Issue 57
Date: Tue, 02 May 2006 15:10:58 +0000	[thread overview]
Message-ID: <44577682.1000408@telus.net> (raw)

  Jean Delvare <khali at linux-fr.org> wrote | Subject: Re: [lm-sensors] 
user prog "sensors" seg faults on x86_64? |

>| > 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

| 
| Does "sensors" (without -s) work?

also seg faults

| 
| Why don't you use the package which comes with Suse?

also seg faults (I downloaded the package assuming it would be newer, it wasn't)

| 
| Which beta is this?

10.1 beta 9
| 
| I'm using lm_sensors on Suse 10.0 x86_64 myself for quite some time now
| without a problem, so I doubt there is a general 64-bit problem.
| 
it seems it is something in the sysfs that is causing the crash. I tried 
to build sensors with debuging but all gdb would tell me was the seg 
fault was in : Program received signal SIGSEGV, Segmentation fault. 
0x00002af197a9deaf in sensors_read_one_sysfs_chip () from 
/usr/local/lib/libsensors.so.3 I havn't got it to tell me the exact line 
where its crashing (yet).



                 reply	other threads:[~2006-05-02 15:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=44577682.1000408@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.