All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Joshua Kinard <kumba@gentoo.org>
Cc: linux-mips@linux-mips.org
Subject: Re: 16k or 64k PAGE_SIZE and "illegal instruction" (signal -4) errors
Date: Tue, 26 Aug 2014 12:50:35 +0100 (BST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1408261240070.18483@eddie.linux-mips.org> (raw)
In-Reply-To: <53FC6A50.9090709@gentoo.org>

On Tue, 26 Aug 2014, Joshua Kinard wrote:

> > This sound very unlikely as the CPU was primarily designed to run IRIX and
> > SGI's systems were using 16k or even 64k page size.
> > 
> > What userland are you running and how old is it?  Are you seeing different
> > results for 16k and 64k?
> 
> o32 userland is the primary on both systems.  However, the last SIGILL was
> under the 64k PAGE_SIZE kernel inside of an n32 chroot compiling the 'boost'
> package on the Octane, which I restarted that and it's not complained since.
>  Also got SIGILL on the 16k PAGE_SIZE kernel when I booted 16k PAGE_SIZE the
> first time and ran 'ps'.  Subsequent runs of 'ps' didn't reproduce the
> error.  Also saw SIGILLs in the bootlog of the 16k PAGE_SIZE kernel when
> "rm" was ran once (couldn't reproduce) and when mdadm tried to put one of
> the arrays back together.  Subsequent runs using similar argument lines
> don't reproduce once I got to a root shell.

 Such intermittent failures look to me remarkably like cache coherency 
problems e.g. D$ vs I$.  You can try making cache invalidation harder, 
e.g. tweak all the writeback calls and invalidation calls so that they 
perform their operation on the whole cache rather than the requested range 
only and see if that makes things better.  You may instead tweak the 
suspected calling site too, of course.

  Maciej

  reply	other threads:[~2014-08-26 11:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26  9:27 16k or 64k PAGE_SIZE and "illegal instruction" (signal -4) errors Joshua Kinard
2014-08-26 10:20 ` Ralf Baechle
2014-08-26 10:42   ` Maciej W. Rozycki
2014-08-26 10:49     ` Maciej W. Rozycki
2014-08-26 11:49     ` Ralf Baechle
2014-08-26 12:03       ` Joshua Kinard
2014-08-26 12:11         ` Ralf Baechle
2014-08-26 11:06   ` Joshua Kinard
2014-08-26 11:50     ` Maciej W. Rozycki [this message]
2014-08-26 12:03     ` Ralf Baechle
2014-08-26 13:16       ` Joshua Kinard
2014-08-26 14:02         ` Ralf Baechle
2014-08-27  0:53           ` Joshua Kinard
2014-09-04  3:35             ` Joshua Kinard
2014-08-26 14:03         ` Ralf Baechle

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=alpine.LFD.2.11.1408261240070.18483@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.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.