LKML Archive on
help / color / mirror / Atom feed
From: Mel Gorman <>
To: Gerhard Pircher <>
Subject: Re: Commit for mm/page_alloc.c breaks boot process on my machine
Date: Mon, 4 Feb 2008 10:42:32 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On (01/02/08 22:06), Gerhard Pircher didst pronounce:
> -------- Original-Nachricht --------
> > Datum: Fri, 1 Feb 2008 20:25:18 +0000
> > Von: Mel Gorman <>
> > An: Gerhard Pircher <>
> > CC:
> > Betreff: Re: Commit for mm/page_alloc.c breaks boot process on my machine
> > I meant uninitialised memory but I also wonder could something like this
> > happen if you are trying to use memory that doesn't exist. i.e. you are
> > trying to access more memory than you really have but you indicate later
> > that this is not the case.
> Good question. The memory is in the physical address range from 0x00000000
> to 0x60000000 (1536MB).
> > > > 2. Any chance of seeing a dmesg log?
> > > That's a little bit of a problem. The kernel log in memory doesn't show
> > > any kernel oops, but is also fragmented (small fragments seem to have
> > > been overwritten with 0x0).
> > 
> > err, that doesn't sound very healthy.
> Yeah, I know. But the platform code hasn't changed much when porting it
> from arch/ppc to arch/powerpc. That's why I'm a little bit lost in this
> case. :-)

I'm at a bit of a loss to guess what might have changed in powerpc code
that would explain this. I've added the linuxppc-dev mailing list in
case they can make a guess.

I think you are also going to need to start bisecting searching
specifically for the patch that causes these overwrites.

> > > Well, I can't answer this question. The kernel currently locks up when
> > > loading the INIT program. But that is another problem (I still have to
> > > bisect it) and doesn't seem to be related to this problem.
> > 
> > INIT would be the first MOVABLE allocation so it would be using memory
> > at the end of the physical adddress range. i.e. the crash happens when
> > memory towards the end and the only difference between the patch applied
> > and reverted is when it happens.
> Oh, that sounds interesting!
> > 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.

It's a virtual address so it depends on the value of CONFIG_KERNEL_START
as to whether this is a user program address or not.

Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

  reply	other threads:[~2008-02-04 10:42 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 [this message]
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
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).