From: Mikael Pettersson <mikpe@csd.uu.se>
To: FrankZhu@viatech.com.cn
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM:Illegal instruction when mount nfs file systems using cyr ixIII
Date: Wed, 27 Jun 2001 22:19:37 +0200 (MET DST) [thread overview]
Message-ID: <200106272019.WAA29237@harpo.it.uu.se> (raw)
On Wed, 27 Jun 2001 17:42:01 +0800, Frank Zhu wrote:
>I use a PIII machine as the server and cyrixIII machine as the client.The
>kernel is 2.4.5.The distribute is red hat 7.1
>when i mount the nfs file system at the client it failed.The core file is
>created.using the gdb it report :
>Program terminated with signal 4(SIGILL),Illegal instruction
>#0 0x40003e28 in ??()
>
>If i change the cpu (CyrixIII) to PIII all is ok.
You don't say exactly where the failure occurs, but I suspect
that you're feeding i686-class machine code to your VIA Cyrix III.
The problem is that VIA Cyrix III announces itself (via CPUID)
as a "family 6" processor, i.e. i686 compatible. This is not
completely accurate, since it doesn't implement the conditional
move instruction. [Yeah, I know there's a CPUID feature flag for
CMOV. I also know gcc doesn't check it, and I suspect glibc
doesn't either.]
To make the machine work you'll have to ensure that the kernel,
user-space libraries and programs, and NFS-imported programs
all are compiled for a lesser CPU than i686.
/Mikael
next reply other threads:[~2001-06-27 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 20:19 Mikael Pettersson [this message]
2001-06-27 22:10 ` Alan Cox
2001-06-28 18:39 ` Bernd Schmidt
2001-06-28 19:42 ` PROBLEM:Illegal instruction when mount nfs file systems using Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-06-27 9:42 PROBLEM:Illegal instruction when mount nfs file systems using cyr ixIII Frank Zhu (Shanghai)
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=200106272019.WAA29237@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=FrankZhu@viatech.com.cn \
--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®