mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miklos.Szeredi@eth.ericsson.se (Miklos Szeredi)
To: davej@codemonkey.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA C3 and random SIGTRAP or segfault
Date: Wed, 15 Jan 2003 13:38:58 +0100 (MET)	[thread overview]
Message-ID: <200301151238.h0FCcwh11218@duna48.eth.ericsson.se> (raw)
In-Reply-To: <20030115122324.GC32694@codemonkey.org.uk> (message from Dave Jones on Wed, 15 Jan 2003 12:23:24 +0000)


Thanks, I'll check that out, though I'm a bit sceptical since the
crashes occur randomly not predictably, and that makes me feel it's
not because of an unimplemented instruction.

Also what about trace/breakpoint trap?  Can that be also generated by
an illegal instruction?

Thanks,
Miklos

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


  reply	other threads:[~2003-01-15 12:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15  9:29 Miklos Szeredi
2003-01-15 12:23 ` Dave Jones
2003-01-15 12:38   ` Miklos Szeredi [this message]
2003-01-15 13:23     ` Dave Jones
2003-01-16  5:53   ` Glen Turner
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=200301151238.h0FCcwh11218@duna48.eth.ericsson.se \
    --to=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
all inboxes | Powered by JetHome®