lkml.org 
[lkml]   [2013]   [Oct]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 0/63] Basic scheduler support for automatic NUMA balancing V9
On Wed, Oct 09, 2013 at 06:28:01PM +0200, Ingo Molnar wrote:
>
> 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?

> CONFIG_MGEODE_LX=y

It looks like -march=geode generates similar borkage to the
-march=winchip2 like we found earlier today.

Must be randconfig luck to only hit it now.

Very easy to see if you build kernel/task_work.s, the bitops jc label
path fails to initialize the return value.


\
 
 \ /
  Last update: 2013-10-09 20:01    [W:0.571 / U:4.716 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site