public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mike Kravetz <kravetz@us.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>, Andrew Morton <akpm@osdl.org>,
	linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
	Linus Torvalds <torvalds@osdl.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ppc64: 64K pages support
Date: Thu, 10 Nov 2005 07:32:15 +1100	[thread overview]
Message-ID: <1131568336.24637.91.camel@gaston> (raw)
In-Reply-To: <20051109201720.GB5443@w-mikek2.ibm.com>

On Wed, 2005-11-09 at 12:17 -0800, Mike Kravetz wrote:
> On Wed, Nov 09, 2005 at 06:21:25PM +0100, Christoph Hellwig wrote:
> > Booting current mainline with 64K pagesize enabled gives me a purple (!)
> > screen early during boot.
> 
> I seem to also be having problems with this patch.  My OpenPOWER 720
> stopped booting with 2.6.14-git10(and later).  Just using defconfig.
> 64k page size NOT enabled.  If I back out the 64k page size patch,
> 2.6.14-git10 boots.  I'm trying to get more info but it is painful.
> It dies before xmon is initialized.

There  have been a couple of fixes, try the very latest git. Also, try
enabling early debug in arch/ppc64/kernel/setup.c

> I could have sworn that I booted 2.6.14-git7 with the 64k page size
> patch applied.  But, I can't do that now either.
> 
> Some co-workers have successfully booted other POWER systems with these
> kernels.  So, it must be specific to my hardware/LPAR configuration.

Ok, i'll do more tests here too.

Ben.



  reply	other threads:[~2005-11-09 20:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1130915220.20136.14.camel@gaston>
2005-11-02  7:23 ` [PATCH] ppc64: 64K pages support Benjamin Herrenschmidt
2005-11-03  3:16   ` Paul Mackerras
2005-11-03  5:26     ` ppc64: Fix bug in SLB miss handler for hugepages David Gibson
2005-11-05  0:38   ` [PATCH] ppc64: 64K pages support Christoph Hellwig
2005-11-05  0:44     ` Benjamin Herrenschmidt
2005-11-05  6:37       ` Dave Airlie
2005-11-09 17:21   ` Christoph Hellwig
2005-11-09 20:17     ` Mike Kravetz
2005-11-09 20:32       ` Benjamin Herrenschmidt [this message]
2005-11-09 21:59         ` Badari Pulavarty
2005-11-09 22:01           ` Benjamin Herrenschmidt
2005-11-09 22:07             ` Badari Pulavarty
2005-11-16 23:08               ` Olaf Hering
2005-11-16 23:16                 ` Badari Pulavarty
2005-11-16 23:27                   ` Olaf Hering
2005-11-17  1:32                     ` Andreas Schwab
     [not found]                   ` <ac0de0c00511161557o379fbc71le6d5c5e2ff9a314b@mail.gmail.com>
2005-11-17  0:33                     ` Badari Pulavarty
2005-11-09 20:36     ` Benjamin Herrenschmidt
2005-11-09 22:15     ` Paul Mackerras
2005-11-09 23:42     ` Benjamin Herrenschmidt

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=1131568336.24637.91.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=hch@lst.de \
    --cc=kravetz@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=torvalds@osdl.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