From: Dave Jones <davej@codemonkey.org.uk>
To: Miklos Szeredi <Miklos.Szeredi@eth.ericsson.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA C3 and random SIGTRAP or segfault
Date: Wed, 15 Jan 2003 12:23:24 +0000 [thread overview]
Message-ID: <20030115122324.GC32694@codemonkey.org.uk> (raw)
In-Reply-To: <200301150929.h0F9T1I10444@duna48.eth.ericsson.se>
On Wed, Jan 15, 2003 at 10:29:01AM +0100, Miklos Szeredi wrote:
>
> I just bought a VIA C3 866 processor, and under very special
> circumstances some programs (e.g. mplayer, xmms) randomly crash with
> trace/breakpoint trap or segmentation fault. Otherwise the system
> seems stable even under high load.
Be sure that those programs aren't compiled for 686. The C3 lacks
cmov, so it'll segfault when it hits that opcode. You can confirm
this by running it under gdb, and disassembling where it segv's to.
This is still a common problem thats biting some people. The debian
folks had a broken libssl for months up until recently.
Note to userspace developers: If you're compiling something as
a 686 binary, you *NEED* to check the feature flags (in an i386
compiled program) to see if the CPU has cmov before you load 686
optimised parts of your app. This is *NOT* a kernel problem,
it is *NOT* a CPU bug. The cmov extension is optional.
VIA chose to save silicon space by not implementing it.
Gcc unfortunatly always uses cmov when compiling for 686.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2003-01-15 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 9:29 VIA C3 and random SIGTRAP or segfault Miklos Szeredi
2003-01-15 12:23 ` Dave Jones [this message]
2003-01-15 12:38 ` Miklos Szeredi
2003-01-15 13:23 ` Dave Jones
2003-01-16 5:53 ` Glen Turner
-- strict thread matches above, loose matches on Subject: below --
2003-01-15 14:15 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
2003-01-15 16:26 ` Miklos Szeredi
2003-01-20 7:30 ` Alan
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=20030115122324.GC32694@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=Miklos.Szeredi@eth.ericsson.se \
--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