Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Joshua Kinard <kumba@gentoo.org>
To: Ralf Baechle <ralf@linux-mips.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 09:16:56 -0400	[thread overview]
Message-ID: <53FC88C8.6000209@gentoo.org> (raw)
In-Reply-To: <20140826120326.GB24146@linux-mips.org>

On 08/26/2014 08:03, Ralf Baechle wrote:
> On Tue, Aug 26, 2014 at 07:06:56AM -0400, Joshua Kinard wrote:
> 
>> 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.
>>
>> Being it's a Gentoo install...the o32 userland is pretty fresh.  Especially
>> on the Octane, where I literally rebuilt the old userland over 2-3 times
>> just to make sure all the old 5-year cruft was gone.  The n32 userland
>> chroot is brand-spanking new.  gcc-4.7.x only for now on both, because of
>> PR61538 in gcc.  Latest binutils.
>>
>> The O2 is chugging away happily so far in updating a bunch of packages.  So
>> I am leaning towards this being another quirk I have to hunt down in the
>> Octane's code again.  There isn't much in the Octane-specific code that
>> deals with memory, though -- it seems the higher-level MIPS memory code
>> handles most things just fine.
> 
> Can you enable core dumps?  I'm wondering about the EPC of the crashed
> process.  If it's at a function entry or the beginning of a page that
> might indicate there is an issue with flushing caches after the containing
> page got loaded.  Also interesting to know if this possibly happened in a
> signal trampoline or VDSO.
> 
> These are just the usual suspects - nothing indicates this case is actually
> related.

(Missed the reply all on the last one)

Enabled coredumps and got the 'shash' program to fail a second time (first
program to do so)...so I'll rebuild that with debugging symbols and try to
trip it up again later on.

Is a core file from a binary w/o debugging of any value?

-- 
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

  reply	other threads:[~2014-08-26 13:17 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
2014-08-26 12:03     ` Ralf Baechle
2014-08-26 13:16       ` Joshua Kinard [this message]
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=53FC88C8.6000209@gentoo.org \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox