From: Christoph Lameter <clameter@sgi.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: lee.schermerhorn@hp.com, Linux MM <linux-mm@kvack.org>,
Mel Gorman <mel@csn.ul.ie>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
Pekka Enberg <penberg@cs.helsinki.fi>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
hanth Aravamudan <nacc@us.ibm.com>,
akpm@linux-foundation.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: crash in kmem_cache_init
Date: Tue, 22 Jan 2008 14:23:18 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0801221417480.1912@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20080122214505.GA15674@aepfle.de>
On Tue, 22 Jan 2008, Olaf Hering wrote:
> It crashes now in a different way if the patch below is applied:
Yup no l3 structure for the current node. We are early in boostrap. You
could just check if the l3 is there and if not just skip starting the
reaper? This will be redone later anyways. Not sure if this will solve all
your issues though. An l3 for the current node that we are booting on
needs to be created early on for SLAB bootstrap to succeed. AFAICT SLUB
doesnt care and simply uses whatever the page allocator gives it for the
cpu slab. We may have gotten there because you only tested with SLUB
recently and thus changes got in that broke SLAB boot assumptions.
> 0xc0000000000fe018 is in setup_cpu_cache (/home/olaf/kernel/git/linux-2.6-numa/mm/slab.c:2111).
> 2106 BUG_ON(!cachep->nodelists[node]);
> 2107 kmem_list3_init(cachep->nodelists[node]);
> 2108 }
> 2109 }
> 2110 }
if (cachep->nodelists[numa_node_id()])
return;
> 2111 cachep->nodelists[numa_node_id()]->next_reap =
> 2112 jiffies + REAPTIMEOUT_LIST3 +
> 2113 ((unsigned long)cachep) % REAPTIMEOUT_LIST3;
> 2114
> 2115 cpu_cache_get(cachep)->avail = 0;
>
>
next prev parent reply other threads:[~2008-01-22 22:23 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 15:09 crash in kmem_cache_init Olaf Hering
2008-01-15 15:58 ` Olaf Hering
2008-01-17 12:14 ` Pekka Enberg
2008-01-17 14:30 ` Christoph Lameter
2008-01-17 18:12 ` Olaf Hering
2008-01-17 18:58 ` Christoph Lameter
2008-01-17 19:54 ` Olaf Hering
2008-01-17 20:20 ` Olaf Hering
2008-01-19 4:56 ` Christoph Lameter
2008-01-17 21:15 ` Olaf Hering
2008-01-18 6:56 ` Olaf Hering
2008-01-18 18:42 ` Christoph Lameter
2008-01-19 4:55 ` Christoph Lameter
2008-01-18 18:47 ` Christoph Lameter
2008-01-18 21:30 ` Mel Gorman
2008-01-18 21:43 ` Christoph Lameter
2008-01-18 22:16 ` Christoph Lameter
2008-01-18 22:19 ` Nish Aravamudan
2008-01-18 22:38 ` Christoph Lameter
2008-01-18 22:57 ` Olaf Hering
2008-01-22 19:54 ` Mel Gorman
2008-01-22 20:11 ` Christoph Lameter
2008-01-22 21:26 ` Mel Gorman
2008-01-22 21:34 ` Christoph Lameter
2008-01-22 22:50 ` Mel Gorman
2008-01-22 22:57 ` Christoph Lameter
2008-01-22 23:10 ` Mel Gorman
2008-01-22 23:14 ` Christoph Lameter
2008-01-22 22:59 ` Pekka Enberg
2008-01-22 23:12 ` Christoph Lameter
2008-01-22 23:18 ` Christoph Lameter
2008-01-23 8:19 ` Pekka Enberg
2008-01-23 8:40 ` Olaf Hering
2008-01-22 21:45 ` Olaf Hering
2008-01-22 22:12 ` Nish Aravamudan
2008-01-22 22:23 ` Christoph Lameter [this message]
2008-01-23 7:58 ` Olaf Hering
2008-01-23 10:50 ` Mel Gorman
2008-01-23 12:14 ` Olaf Hering
2008-01-23 12:52 ` Olaf Hering
2008-01-23 13:55 ` [PATCH] Fix boot problem in situations where the boot CPU is running on a memoryless node Mel Gorman
2008-01-23 14:18 ` Pekka J Enberg
2008-01-23 14:32 ` Pekka J Enberg
2008-01-23 14:49 ` Pekka J Enberg
2008-01-23 15:56 ` Mel Gorman
2008-01-23 17:29 ` Pekka J Enberg
2008-01-23 17:42 ` Pekka J Enberg
2008-01-23 18:51 ` Christoph Lameter
2008-01-23 19:52 ` Nishanth Aravamudan
2008-01-23 21:02 ` Pekka Enberg
2008-01-23 21:14 ` Christoph Lameter
2008-01-23 21:36 ` Nishanth Aravamudan
2008-01-24 3:13 ` Christoph Lameter
2008-01-23 18:36 ` Christoph Lameter
2008-01-23 18:35 ` Christoph Lameter
2008-01-23 14:27 ` Olaf Hering
2008-01-23 14:42 ` Mel Gorman
2008-01-23 18:41 ` Christoph Lameter
2008-01-23 13:41 ` crash in kmem_cache_init Mel Gorman
2008-01-18 18:51 ` Christoph Lameter
2008-01-17 19:03 ` Christoph Lameter
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=Pine.LNX.4.64.0801221417480.1912@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mel@csn.ul.ie \
--cc=nacc@us.ibm.com \
--cc=olaf@aepfle.de \
--cc=penberg@cs.helsinki.fi \
/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).