linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: aglitke <agl@us.ibm.com>
To: michael@ellerman.id.au
Cc: Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: Problems booting a 64k page kernel
Date: Thu, 29 Nov 2007 09:12:56 -0600	[thread overview]
Message-ID: <1196349176.27582.129.camel@localhost.localdomain> (raw)
In-Reply-To: <1196293142.7875.1.camel@concordia>

Michael, thanks for your reply...

I am seeing the segmentation fault both on the default SLES10 initrd and
the default RHEL5.1 initrd.  Therefore, I am reasonably sure this is a
problem with my kernel build and not the initrd itself.

On Thu, 2007-11-29 at 10:39 +1100, Michael Ellerman wrote:
> On Wed, 2007-11-28 at 16:50 -0600, aglitke wrote:
> > Hello all.  I am new to building 64k page kernels and can't seem to get
> > one to boot correctly.  Everything looks okay until init gets a signal
> > 11 while booting.  Attached is my boot log and the kernel config I used.
> > To generate this config I merely enabled the 64k page option in make
> > menuconfig to alter a previously working config.
> > 
> > Any help you can provide would be greatly appreciated.
> 
> I've seen that happen with an init linked with uClibc, its dynamic
> loader was doing mmap with MAP_FIXED on non-64K aligned addresses.
> What user space are you using?
> 
> cheers
> 
-- 
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center

      reply	other threads:[~2007-11-29 15:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28 22:50 Problems booting a 64k page kernel aglitke
2007-11-28 23:39 ` Michael Ellerman
2007-11-29 15:12   ` aglitke [this message]

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=1196349176.27582.129.camel@localhost.localdomain \
    --to=agl@us.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    /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;
as well as URLs for NNTP newsgroup(s).