From: Christoph Lameter <cl@linux-foundation.org>
To: Alex Chiang <achiang@hp.com>
Cc: penberg@cs.helsinki.fi, linux-ia64@vger.kernel.org, linux-mm@kvack.org
Subject: Re: SLUB ia64 linux-next crash bisected to 756dee75
Date: Thu, 14 Jan 2010 09:01:33 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.00.1001140858460.14164@router.home> (raw)
In-Reply-To: <20100114005304.GC27766@ldl.fc.hp.com>
On Wed, 13 Jan 2010, Alex Chiang wrote:
> Firmware puts each cell into a NUMA node, so we should really
> only have 2 nodes, but for some reason, that 3rd node gets
> created too. I haven't inspected the SRAT/SLIT on this machine
> recently, but can do so if you want me to.
May not have anything to do with the problem we are looking at but memory
setup is screwed up. Funky effects may follow.
> > Maybe we miscalculated the number of DMA caches needed.
> > Does this patch fix it?
>
> Nope, same oops.
Duh. Have to look at this in more detail.
> ACPI: SLIT table looks invalid. Not used.
> Number of logical nodes in system = 3
> Number of memory chunks in system = 5
SLIT table just contain the distances if I remember correctly. The memory
maps are separate.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-01-14 15:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 0:29 Alex Chiang
2010-01-13 14:59 ` Christoph Lameter
2010-01-14 0:53 ` Alex Chiang
2010-01-14 15:01 ` Christoph Lameter [this message]
2010-01-14 18:01 ` Alex Chiang
2010-01-14 15:18 ` Christoph Lameter
2010-01-14 18:22 ` Alex Chiang
2010-01-14 19:17 ` Pekka Enberg
2010-01-14 20:32 ` Alex Chiang
2010-01-14 20:58 ` Christoph Lameter
2010-01-14 21:29 ` Alex Chiang
2010-01-14 21:31 ` Pekka Enberg
2010-01-14 21:59 ` Christoph Lameter
2010-01-14 22:01 ` Christoph Lameter
2010-01-15 20:07 ` Christoph Lameter
2010-01-15 20:35 ` Lee Schermerhorn
2010-01-15 23:32 ` Christoph Lameter
2010-01-19 18:53 ` Christoph Lameter
2010-01-19 20:02 ` Alex Chiang
2010-01-19 20:29 ` Christoph Lameter
2010-01-19 21:29 ` Alex Chiang
2010-01-19 21:50 ` Christoph Lameter
2010-01-20 22:46 ` Alex Chiang
2010-01-21 21:47 ` Alex Chiang
2010-01-21 22:45 ` Christoph Lameter
2010-01-21 23:05 ` Alex Chiang
2010-01-21 23:43 ` Christoph Lameter
2010-01-22 0:15 ` Alex Chiang
2010-01-22 14:43 ` Christoph Lameter
2010-01-22 16:37 ` Pekka Enberg
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=alpine.DEB.2.00.1001140858460.14164@router.home \
--to=cl@linux-foundation.org \
--cc=achiang@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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