From: Joshua Kinard <kumba@gentoo.org>
To: Linux MIPS List <linux-mips@linux-mips.org>
Subject: 16k or 64k PAGE_SIZE and "illegal instruction" (signal -4) errors
Date: Tue, 26 Aug 2014 05:27:28 -0400 [thread overview]
Message-ID: <53FC5300.4070902@gentoo.org> (raw)
Okay, so from the "make kmap cache coloring aware" thread, I've been playing
with larger PAGE_SIZE values on the Octane and O2 for the last few hours.
16k and 64k used to, in the past, never get far after init (usually died
*at* init) That appears to have changed now. Most programs seem to
JustWork(), but very randomly, I am getting a signal -4, illegal instruction
(SIGILL) on the Octane. Both systems are running kernels w/ 64k PAGE_SIZE
at the moment.
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.
Ideas?
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
next reply other threads:[~2014-08-26 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 9:27 Joshua Kinard [this message]
2014-08-26 10:20 ` 16k or 64k PAGE_SIZE and "illegal instruction" (signal -4) errors 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
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=53FC5300.4070902@gentoo.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox