All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bob Picco" <bob.picco@hp.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Mel Gorman <mel@csn.ul.ie>,
	linuxppc-dev@ozlabs.org, ak@suse.de,
	linux-kernel@vger.kernel.org, davej@codemonkey.org.uk
Subject: Re: [PATCH 0/6] [RFC] Sizing zones and holes in an architecture independent manner
Date: Tue, 11 Apr 2006 19:29:44 -0400	[thread overview]
Message-ID: <20060411232944.GE23742@localhost> (raw)
In-Reply-To: <20060411222029.GA7743@agluck-lia64.sc.intel.com>

luck wrote:	[Tue Apr 11 2006, 06:20:29PM EDT]
> On Tue, Apr 11, 2006 at 11:39:46AM +0100, Mel Gorman wrote:
> 
> > The patches have only been *compile tested* for ia64 with a flatmem
> > configuration. At attempt was made to boot test on an ancient RS/6000
> > but the vanilla kernel does not boot so I have to investigate there.
> 
> The good news: Compilation is clean on the ia64 config variants that
> I usually build (all 10 of them).
> 
> The bad (or at least consistent) news: It doesn't boot on an Intel
> Tiger either (oops at kmem_cache_alloc+0x41).
> 
> -Tony
I had a reply queued to report the same failure with
DISCONTIG+NUMA+VIRTUAL_MEM_MAP.  This was 2 CPU HP rx2600. I'll take a closer 
look at the code tomorrow. 

bob

WARNING: multiple messages have this Message-ID (diff)
From: "Bob Picco" <bob.picco@hp.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Mel Gorman <mel@csn.ul.ie>,
	linuxppc-dev@ozlabs.org, davej@codemonkey.org.uk,
	linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: [PATCH 0/6] [RFC] Sizing zones and holes in an architecture independent manner
Date: Tue, 11 Apr 2006 19:29:44 -0400	[thread overview]
Message-ID: <20060411232944.GE23742@localhost> (raw)
In-Reply-To: <20060411222029.GA7743@agluck-lia64.sc.intel.com>

luck wrote:	[Tue Apr 11 2006, 06:20:29PM EDT]
> On Tue, Apr 11, 2006 at 11:39:46AM +0100, Mel Gorman wrote:
> 
> > The patches have only been *compile tested* for ia64 with a flatmem
> > configuration. At attempt was made to boot test on an ancient RS/6000
> > but the vanilla kernel does not boot so I have to investigate there.
> 
> The good news: Compilation is clean on the ia64 config variants that
> I usually build (all 10 of them).
> 
> The bad (or at least consistent) news: It doesn't boot on an Intel
> Tiger either (oops at kmem_cache_alloc+0x41).
> 
> -Tony
I had a reply queued to report the same failure with
DISCONTIG+NUMA+VIRTUAL_MEM_MAP.  This was 2 CPU HP rx2600. I'll take a closer 
look at the code tomorrow. 

bob

  parent reply	other threads:[~2006-04-11 23:50 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-11 10:39 [PATCH 0/6] [RFC] Sizing zones and holes in an architecture independent manner Mel Gorman
2006-04-11 10:40 ` [PATCH 1/6] Introduce mechanism for registering active regions of memory Mel Gorman
2006-04-11 10:40 ` [PATCH 2/6] Have Power use add_active_range() and free_area_init_nodes() Mel Gorman
2006-04-11 10:40 ` [PATCH 3/6] Have x86 use add_active_range() and free_area_init_nodes Mel Gorman
2006-04-11 10:41 ` [PATCH 4/6] Have x86_64 " Mel Gorman
2006-04-11 10:41 ` [PATCH 5/6] Have ia64 " Mel Gorman
2006-04-11 10:41 ` [PATCH 6/6] Break out memory initialisation code from page_alloc.c to mem_init.c Mel Gorman
2006-04-11 11:07   ` Nick Piggin
2006-04-11 11:07     ` Nick Piggin
2006-04-11 16:59     ` Mel Gorman
2006-04-11 16:59       ` Mel Gorman
2006-04-11 22:20 ` [PATCH 0/6] [RFC] Sizing zones and holes in an architecture independent manner Luck, Tony
2006-04-11 22:20   ` Luck, Tony
2006-04-11 23:23   ` Mel Gorman
2006-04-11 23:23     ` Mel Gorman
2006-04-12  0:05     ` Luck, Tony
2006-04-12  0:05       ` Luck, Tony
2006-04-12 10:50       ` Mel Gorman
2006-04-12 10:50         ` Mel Gorman
2006-04-12 15:46         ` Luck, Tony
2006-04-12 15:46           ` Luck, Tony
2006-04-12 16:00           ` Mel Gorman
2006-04-12 16:00             ` Mel Gorman
2006-04-12 16:36             ` Luck, Tony
2006-04-12 16:36               ` Luck, Tony
2006-04-12 17:50               ` Mel Gorman
2006-04-12 17:50                 ` Mel Gorman
2006-04-12 17:07             ` Luck, Tony
2006-04-12 17:07               ` Luck, Tony
2006-04-12 17:18               ` Bob Picco
2006-04-12 17:18                 ` Bob Picco
2006-04-12 17:32               ` Mel Gorman
2006-04-12 17:32                 ` Mel Gorman
2006-04-12 15:54         ` Luck, Tony
2006-04-12 15:54           ` Luck, Tony
2006-04-11 23:29   ` Bob Picco [this message]
2006-04-11 23:29     ` Bob Picco
2006-04-12  0:02     ` Mel Gorman
2006-04-12  0:02       ` Mel Gorman
2006-04-12  1:38       ` Bob Picco
2006-04-12  1:38         ` Bob Picco
2006-04-12 10:59         ` Mel Gorman
2006-04-12 10:59           ` Mel Gorman

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=20060411232944.GE23742@localhost \
    --to=bob.picco@hp.com \
    --cc=ak@suse.de \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mel@csn.ul.ie \
    --cc=tony.luck@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.