All of lore.kernel.org
 help / color / mirror / Atom feed
From: GOTO Masanori <gotom@debian.or.jp>
To: Guennadi Liakhovetski <gl@dsa-ac.de>
Cc: <P@draigBrady.com>, <linux-kernel@vger.kernel.org>,
	<debian-glibc@lists.debian.org>
Subject: Re: VIA Ezra CentaurHauls
Date: Sat, 21 Jun 2003 01:57:29 +0900	[thread overview]
Message-ID: <803ci4it52.wl@oris.opensource.jp> (raw)
In-Reply-To: <Pine.LNX.4.33.0306181908190.2967-100000@pcgl.dsa-ac.de>

At Wed, 18 Jun 2003 19:17:11 +0200 (CEST),
Guennadi Liakhovetski wrote:
> So, using the above for libraries I found 3 libraries on the system, that
> use cmov:
> 
> libldap.so.2.0.15
> libcrypto.so.0.9.6
> libqt-mt.so.3.0.5
> 
> So, the libraries have nothing to do with the kernel, the Debian guys
> might take a notice of them (not glibc, but still...). But what I do find
> interesting and noteworthy - is that this problem is specific only to some
> revisions of this CPU, which might be of interest to all.

I think it's not debian glibc problem.  If you hit cmov problem, then
your application says "illegal instruction".  At least debian glibc
2.3.1-16 has trick not to load cmov-contained dynamic libraries.  All
libraries you pointed out are put under /.../lib/.../cmov/* in debian
sid.  I guess it's your CPU or thermal issue.

Regards,
-- gotom

  reply	other threads:[~2003-06-20 16:43 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
2003-06-18 16:15   ` Guennadi Liakhovetski
2003-06-18 17:17   ` Guennadi Liakhovetski
2003-06-20 16:57     ` GOTO Masanori [this message]
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=803ci4it52.wl@oris.opensource.jp \
    --to=gotom@debian.or.jp \
    --cc=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.