From: Brian Gerst <bgerst@didntduck.org>
To: ebuddington@wesleyan.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: 386 'ls' gets SIGILL iff /proc is mounted
Date: Tue, 27 Mar 2001 09:22:19 -0500 [thread overview]
Message-ID: <3AC0A21B.438EFE02@didntduck.org> (raw)
In-Reply-To: <20010327012709.I59@sparrow.nad.adelphia.net> <3AC09F14.53D06AC7@didntduck.org> <20010327091205.B80@sparrow.nad.adelphia.net>
Eric Buddington wrote:
>
> On Tue, Mar 27, 2001 at 09:09:24AM -0500, Brian Gerst wrote:
> > >
> > > The problems are varied enough that I suspect bad hardware, but would
> > > flaky RAM cause such similar failures repeatedly? And is there a way
> > > to test RAM explicitly?
> > >
> > > Any tips appreciated, either to me (ebuddington@wesleyan.edu) or to
> > > the list.
> >
> > Silly question, but is math emulation enabled?
>
> Yes. I should have mentioned that in the original, since it occurred
> to me also.
>
> -Eric
Try running ls under gdb and find out what instruction is causing SIGILL
(illegal opcode). It is possible that it was compiled to use
instructions available only on later processors, or it could potentially
be a bug in the math emulation code.
--
Brian Gerst
next prev parent reply other threads:[~2001-03-27 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 6:27 386 'ls' gets SIGILL iff /proc is mounted Eric Buddington
2001-03-27 14:09 ` Brian Gerst
2001-03-27 14:12 ` Eric Buddington
2001-03-27 14:22 ` Brian Gerst [this message]
[not found] ` <20010328124845.I80@sparrow.nad.adelphia.net>
[not found] ` <m3wv99vk8o.fsf@otr.mynet.cygnus.com>
2001-03-29 15:05 ` Eric Buddington
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=3AC0A21B.438EFE02@didntduck.org \
--to=bgerst@didntduck.org \
--cc=ebuddington@wesleyan.edu \
--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