[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131009162801.GA10452@gmail.com>
Date: Wed, 9 Oct 2013 18:28:01 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Mel Gorman <mgorman@...e.de>
Cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Rik van Riel <riel@...hat.com>,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
Andrea Arcangeli <aarcange@...hat.com>,
Johannes Weiner <hannes@...xchg.org>,
Linux-MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/63] Basic scheduler support for automatic NUMA
balancing V9
Hm, so I'm seeing boot crashes with the config attached:
INIT: version 2.86 booting
BUG: unable to handle kernel BUG: unable to handle kernel paging
requestpaging request at eaf10f40
at eaf10f40
IP:IP: [<b103e0ef>] task_work_run+0x52/0x87
[<b103e0ef>] task_work_run+0x52/0x87
*pde = 3fbf9067 *pde = 3fbf9067 *pte = 3af10060 *pte = 3af10060
Oops: 0000 [#1] Oops: 0000 [#1] DEBUG_PAGEALLOCDEBUG_PAGEALLOC
CPU: 0 PID: 171 Comm: hostname Tainted: G W
3.12.0-rc4-01668-gfd71a04-dirty #229484
CPU: 0 PID: 171 Comm: hostname Tainted: G W
3.12.0-rc4-01668-gfd71a04-dirty #229484
task: eaf157a0 ti: eacf2000 task.ti: eacf2000
Note that the config does not have NUMA_BALANCING enabled. With another
config I also had a failed bootup due to the OOM killer kicking in. That
didn't have NUMA_BALANCING enabled either.
Yet this all started today, after merging the NUMA patches.
Any ideas?
Thanks,
Ingo
View attachment "config" of type "text/plain" (112298 bytes)
Powered by blists - more mailing lists