All of lore.kernel.org
 help / color / mirror / Atom feed
From: P@draigBrady.com
To: Guennadi Liakhovetski <gl@dsa-ac.de>
Cc: linux-kernel@vger.kernel.org, debian-glibc@lists.debian.org
Subject: Re: VIA Ezra CentaurHauls
Date: Wed, 18 Jun 2003 15:42:11 +0100	[thread overview]
Message-ID: <3EF07A43.8000505@draigBrady.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0306181205180.2967-100000@pcgl.dsa-ac.de>

Guennadi Liakhovetski wrote:
> Hello
> 
> We have a platform with the above processor, and we happened to have 2
> revisions thereof: stepping 8 and 10. With stepping 8 we are getting
> "random" application crashes (segfaults), sometimes with kernel-Oopses.
> The distribution is Debian-Woody.

Interesting, so stepping 10 is OK?

> I saw some messages on the Debian
> mailing list about problems with exactly this CPU, however, it was not
> related to different revisions (stepping), perhaps, the author only had
>  / tried stepping 8. The fix was to upgrade libc.

so is it a glibc bug or CPU bug?

> I've done this (to
> version libc6_2.3.1-16, but it didn't help. Any ideas?

You could search for CMOV instructions on your system,
which could cause wierdness, like:

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

Note C3 Nehemiah do have CMOV (but no 3dnow).

Pádraig.


  reply	other threads:[~2003-06-18 14:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 14:18 VIA Ezra CentaurHauls Guennadi Liakhovetski
2003-06-18 14:42 ` P [this message]
2003-06-18 16:15   ` Guennadi Liakhovetski
2003-06-18 17:17   ` Guennadi Liakhovetski
2003-06-20 16:57     ` GOTO Masanori
2003-06-20 11:11 ` Daniel Egger
2003-06-27  6:18 ` Alex Belits
  -- strict thread matches above, loose matches on Subject: below --
2003-06-27  9:18 Miklos Szeredi

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=3EF07A43.8000505@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=debian-glibc@lists.debian.org \
    --cc=gl@dsa-ac.de \
    --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 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.