Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Joshua Kinard <kumba@gentoo.org>
Cc: linux-mips@linux-mips.org
Subject: Re: ARCS can't load CONFIG_DEBUG_LOCK_ALLOC kernel
Date: Thu, 16 Mar 2017 15:09:18 +0100	[thread overview]
Message-ID: <20170316140918.GH5512@linux-mips.org> (raw)
In-Reply-To: <a639551b-4338-e1fb-0cc7-e6ea34b94c2c@gentoo.org>

On Wed, Mar 15, 2017 at 11:50:44PM -0400, Joshua Kinard wrote:

> On 03/15/2017 16:11, Joshua Kinard wrote:
> > I've reported in the past that turning on CONFIG_DEBUG_LOCK_ALLOC produces a
> > kernel that can't boot on several SGI platforms.  It turns out that using
> > arcload (Stan's bootloader originally written for IP30), I can get some
> > debugging out on why.  I am still puzzled, but maybe this information can be
> > interpreted by someone else into something meaningful?
> > 
> > All addresses printed out of arcload are physical address.
> > 
> > ARCS Memory Map as printed by some debugging I added to the arcload binary:
> > 
> > 0x00000000 - 0x00001000 ExceptionBlock
> > 0x00001000 - 0x00002000 SystemParameterBlock
> > 0x00002000 - 0x00004000 FirmwarePermanent
> > 0x20004000 - 0x20f00000 FreeMemory***
> > 0x20f00000 - 0x21000000 FirmwareTemporary
> > 0x21000000 - 0x5fff0000 FreeMemory
> > 0x5fff0000 - 0x5ffff000 LoadedProgram
> > 0x5ffff000 - 0x60000000 FreeMemory
> > 0x60000000 - 0xa0000000 FirmwarePermanent
> 
> So it turns out I can get away, on Octane at least, by changing the load
> address from 0x20004000 to an arbitrary value in the other FreeMemory segment
> from 0x21000000 - 0x5fff0000.  Specifically, using 0x21004000 appears to work
> without any ill effects.
> 
> The 0x20004000 value is the address used by IRIX to load (with symon, it
> becomes 0x200800000 instead).  I'll have to try this on the IP27 later on as
> well.  On Octane, CONFIG_DEBUG_LOCK_ALLOC didn't toss up any major locking
> issues yet.  Probably need to hammer the disks with bonnie++ or such.  At least
> I can get back to the BRIDGE/PCI mess now...

I'm wondering where the ARC stack is on kernel entry if maybe the
ARC stack has corrupted the kernel?  If possible, can you get your
kernel or a test program to compute a checksum over itself to see
if it has been corrupted?

Let me repeat my ARC(S) mantra again, ARC(S) is broken, ARC(S) lies.
Trust is futile.  Even if ARC(S) claims something is free I'd rather
not rely on it.

  Ralf

  reply	other threads:[~2017-03-16 14:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15 20:11 ARCS can't load CONFIG_DEBUG_LOCK_ALLOC kernel Joshua Kinard
2017-03-16  3:50 ` Joshua Kinard
2017-03-16 14:09   ` Ralf Baechle [this message]
2017-03-16 17:50     ` Joshua Kinard
2017-03-16 19:06       ` Ralf Baechle
2017-03-16 20:02         ` Joshua Kinard
2017-03-16 20:50           ` Ralf Baechle
2017-03-17  3:01             ` Joshua Kinard
2017-03-18 23:42               ` Joshua Kinard
2017-03-19  7:23                 ` Joshua Kinard
2017-03-19  8:55                   ` Ralf Baechle
2017-03-21 21:52                     ` Joshua Kinard

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=20170316140918.GH5512@linux-mips.org \
    --to=ralf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox