From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Joshua Kinard <kumba@gentoo.org>,
Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: 16k or 64k PAGE_SIZE and "illegal instruction" (signal -4) errors
Date: Tue, 26 Aug 2014 11:42:30 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.11.1408261126000.18483@eddie.linux-mips.org> (raw)
In-Reply-To: <20140826102004.GA22221@linux-mips.org>
On Tue, 26 Aug 2014, Ralf Baechle wrote:
> > I cannot reproduce it on demand, so I'm not really sure what the cause could
> > be. PAGE_SIZE should be largely transparent to userland these days, so I am
> > wondering if this might be more oddities w/ an R14000 CPU.
>
> 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?
FWIW, I've been always using the 16k page size exclusively with my 64-bit
userland and my SWARM board using the SB-1/BCM1250 processor (with either
endianness) and never had issues even with stuff as intensive as native
GCC bootstrapping (with all the languages enabled such as Ada and Java) or
glibc builds. It's been like 8 years now and quite recent kernels like
from two months ago gave me no trouble either. So it must be something
specific to the configuration, my first candidates to look at would be the
generated TLB and cache handlers, that are system-specific.
Maciej
next prev parent reply other threads:[~2014-08-26 10:42 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 [this message]
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
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.1408261126000.18483@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=kumba@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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.