public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Padraig@Linux.ie
To: Larry Sendlosky <Larry.Sendlosky@storigen.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
	Miklos Szeredi <Miklos.Szeredi@eth.ericsson.se>,
	linux-kernel@vger.kernel.org
Subject: Re: VIA C3 and random SIGTRAP or segfault
Date: Wed, 15 Jan 2003 14:47:36 +0000	[thread overview]
Message-ID: <3E257488.3000006@Linux.ie> (raw)
In-Reply-To: <7BFCE5F1EF28D64198522688F5449D5AC63352@xchangeserver2.storigen.com>

Larry Sendlosky wrote:
> We're seeing the same thing on a mini-ITX based system.
> init is segfaulting :(( .  We've never seen this on our
> other non-C3 systems running the same codebase. We've instrumented
> the kernel to help catch the initial problem, hopefully it will
> trigger soon.
> 
> Dave, will the cmov generate a segfault or illegal instr trap (SIGILL?) ?

segfault is what I saw. Something seems to be corrupted (by a cmov
SIGILL?) and from then the app will crash in the same
(arbitrary) place until the machine is restarted. Some apps
are more susceptible than others. Note a Samuel II would work fine?

Hmm, just checking an ssh binary and associated libs that I know
crashed every so often (only in interactive mode, not with ssh -c),
I noticed that libnsl.so.1 (network services lib (part of glibc))
had cmov instructions. Other things noticed to crash were bash,
vi, php, snmpd. So I guess libnsl could be the root of our probs?
Note we built the whole system from SRPMs with the appropriate
flags for C3, but obviously these were ignored for libnsl anyway!
Also possibly related is that most problematic binaries
(php/snmpd/ssh) were linked to libcrypto.so.2 which may be relevant?

To find if a binary has CMOV instructions:
   objdump --disassemble binary | grep cmov

Pádraig.


  reply	other threads:[~2003-01-15 14:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 14:15 VIA C3 and random SIGTRAP or segfault Larry Sendlosky
2003-01-15 14:47 ` Padraig [this message]
2003-01-15 15:56   ` Miklos Szeredi
2003-01-15 16:12     ` Jens Axboe
2003-01-15 16:13     ` Padraig
2003-01-15 16:26       ` Miklos Szeredi
2003-01-20  7:30 ` Alan
  -- strict thread matches above, loose matches on Subject: below --
2003-01-15  9:29 Miklos Szeredi
2003-01-15 12:23 ` Dave Jones
2003-01-15 12:38   ` Miklos Szeredi
2003-01-15 13:23     ` Dave Jones
2003-01-16  5:53   ` Glen Turner

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=3E257488.3000006@Linux.ie \
    --to=padraig@linux.ie \
    --cc=Larry.Sendlosky@storigen.com \
    --cc=Miklos.Szeredi@eth.ericsson.se \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox