LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gerhard Pircher <gerhard_pircher@gmx.net>
Cc: Mel Gorman <mel@csn.ul.ie>, linux-kernel@vger.kernel.org
Subject: Re: Commit for mm/page_alloc.c breaks boot process on my machine
Date: Tue, 05 Feb 2008 11:07:51 +1100	[thread overview]
Message-ID: <1202170071.7079.22.camel@pasglop> (raw)
In-Reply-To: <20080201210656.174030@gmx.net>


On Fri, 2008-02-01 at 22:06 +0100, Gerhard Pircher wrote:
> > Could you try booting with 16MB less memory using mem=?
> I started the kernel with 512MB RAM (mem=496) and 1.5GB (mem=1520).
> The
> kernel oopes in both cases with a "Unable to handle kernel paging
> request
> for data address 0xbffff000", followed by a "Oops: kernel access of
> bad
> area, sig 11" message. The end of the stack trace shows the
> start_here()
> function.
> I'm not a PowerPC expert, but if 0xbffff000 is a virtual address, then
> it would be in the user program address space, right? If it is a
> physical
> address, then it is somewhere in the unallocated PCI address space

Have you tried DEBUG_PAGEALLOC ? It might fault earlier which might give
us better informations. Also, a stactrace from the oops might be useful,
along with a copy of your device-tree.

Ben.



  parent reply	other threads:[~2008-02-05  0:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01 18:42 Commit for mm/page_alloc.c breaks boot process on my machine Gerhard Pircher
2008-02-01 19:11 ` Mel Gorman
2008-02-01 20:05   ` Gerhard Pircher
2008-02-01 20:25     ` Mel Gorman
2008-02-01 21:06       ` Gerhard Pircher
2008-02-04 10:42         ` Mel Gorman
2008-02-04 22:20           ` Gerhard Pircher
2008-02-04 23:30             ` Michael Ellerman
2008-02-05  0:01           ` Benjamin Herrenschmidt
2008-02-05 10:23             ` Mel Gorman
2008-02-05 20:50               ` Benjamin Herrenschmidt
2008-02-05  0:07         ` Benjamin Herrenschmidt [this message]
2008-02-05  0:06     ` Benjamin Herrenschmidt
2008-02-05 23:17       ` Gerhard Pircher

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=1202170071.7079.22.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=gerhard_pircher@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    /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).