public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org,
	Christoph Lameter <clameter@engr.sgi.com>
Subject: Re: 2.6.18-rc7-mm1 -- ppc64 crash in slab_node ??
Date: Thu, 21 Sep 2006 19:07:55 +0100	[thread overview]
Message-ID: <4512D4FB.5000803@shadowen.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0609211100350.5959@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Thu, 21 Sep 2006, Andrew Morton wrote:
> 
>> I guess the below will fix it.  But Christoph's machine would have oopsed
>> too, if it had called fallback_alloc() this early.  So presumably it did
>> not.  But yours does.  I wonder why?
> 
> Hmmm... Fallback during boot? Any zones that have no ZONE_NORMAL memory?

I think there is some kind of memory layout issue with the machine (see
my reply to akpm), which I'll look into tommorrow.  But as the machine
is tripping this bug, I'll throw this patch at it also.

-apw

  reply	other threads:[~2006-09-21 18:08 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19  8:28 2.6.18-rc7-mm1 Andrew Morton
2006-09-19 13:08 ` 2.6.18-rc7-mm1 Olivier Galibert
2006-09-19 14:22   ` 2.6.18-rc7-mm1 Greg KH
2006-09-19 14:21 ` 2.6.18-rc7-mm1 Greg KH
2006-09-19 16:36   ` 2.6.18-rc7-mm1 Andrew Morton
2006-09-19 18:36     ` 2.6.18-rc7-mm1 Greg KH
2006-09-19 14:45 ` 2.6.18-rc7-mm1 Martin J. Bligh
2006-09-19 16:31   ` 2.6.18-rc7-mm1 Andrew Morton
2006-09-19 16:57     ` 2.6.18-rc7-mm1 Olaf Hering
2006-09-19 17:00     ` 2.6.18-rc7-mm1 Martin Bligh
2006-09-21 12:55     ` 2.6.18-rc7-mm1 Andy Whitcroft
2006-10-07 20:26       ` 2.6.18-rc7-mm1 Greg KH
2006-10-09 12:31         ` 2.6.18-rc7-mm1 Andy Whitcroft
2006-10-09 16:08           ` 2.6.18-rc7-mm1 Greg KH
2006-09-19 17:39 ` [-mm patch] missing class_dev to dev conversions Frederik Deweerdt
2006-10-04  5:10   ` Greg KH
2006-09-19 20:25 ` 2.6.18-rc7-mm1 Rafael J. Wysocki
2006-09-19 20:36   ` 2.6.18-rc7-mm1 Andrew Morton
2006-09-19 21:30     ` 2.6.18-rc7-mm1: networking breakage on HPC nx6325 + SUSE 10.1 Rafael J. Wysocki
2006-09-19 22:06       ` Rafael J. Wysocki
2006-09-19 22:06         ` David Miller
2006-09-19 22:30           ` Greg KH
2006-09-19 22:56             ` Rafael J. Wysocki
2006-09-20  2:28               ` Greg KH
2006-09-20  1:31             ` Dmitry Torokhov
2006-09-20  1:03       ` Valdis.Kletnieks
2006-09-20 14:23     ` 2.6.18-rc7-mm1 Mike Galbraith
2006-09-20 13:18       ` 2.6.18-rc7-mm1 Rafael J. Wysocki
2006-09-21  9:44       ` 2.6.18-rc7-mm1 Andi Kleen
2006-09-21 13:11 ` 2.6.18-rc7-mm1 -- ppc64 crash in slab_node ?? Andy Whitcroft
2006-09-21 17:28   ` Andrew Morton
2006-09-21 18:02     ` Christoph Lameter
2006-09-21 18:07       ` Andy Whitcroft [this message]
2006-09-21 18:03     ` Andy Whitcroft
2006-09-21 13:40 ` 2.6.18-rc7-mm1 Ian Kent
2006-09-21 21:07 ` 2.6.18-rc7-mm1 Mark Haverkamp
2006-09-21 22:19   ` 2.6.18-rc7-mm1 Arnd Bergmann
2006-09-22 11:47 ` [PATCH -mm] x86_64 mm generic getcpu syscall fix Cedric Le Goater
2006-09-22 12:19   ` Andi Kleen
2006-09-23 11:03 ` 2.6.18-rc7-mm1 - gregkh-driver-pcmcia-device.patch breaks orinoco card Valdis.Kletnieks
2006-09-27  3:29   ` Greg KH

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=4512D4FB.5000803@shadowen.org \
    --to=apw@shadowen.org \
    --cc=akpm@osdl.org \
    --cc=clameter@engr.sgi.com \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.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