public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Padraig@Linux.ie
To: Miklos.Szeredi@eth.ericsson.se
Cc: Larry.Sendlosky@storigen.com, davej@codemonkey.org.uk,
	linux-kernel@vger.kernel.org
Subject: Re: VIA C3 and random SIGTRAP or segfault
Date: Wed, 15 Jan 2003 16:13:58 +0000	[thread overview]
Message-ID: <3E2588C6.4020906@Linux.ie> (raw)
In-Reply-To: <200301151556.h0FFupx12324@duna48.eth.ericsson.se>

Miklos.Szeredi@eth.ericsson.se wrote:
>>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?
> 
> Do you mean that after a cmov is encountered other applications will
> also randomly crash?  That would explain what I've been seeing.

Well I never got SIGILL as would be expected. I got SEGFAULTs
and I'm only speculating that a CMOV was encountered.
But yes that does seem to be what's happening, the
CMOV corrupts something global to many apps, and
"every now and then" SEGFAULT.

You could quickly check your system with something like:

find /bin -perm +111 -type f |
while read bin; do
     objdump --disassemble $bin 2>/dev/null |
     grep -q cmov && echo "$bin has cmov"
done

Pádraig.


  parent reply	other threads:[~2003-01-15 16:08 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
2003-01-15 15:56   ` Miklos Szeredi
2003-01-15 16:12     ` Jens Axboe
2003-01-15 16:13     ` Padraig [this message]
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=3E2588C6.4020906@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