lkml.org 
[lkml]   [2014]   [Jan]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: Panic on 8-node system in memblock_virt_alloc_try_nid()
From
On Fri, Jan 24, 2014 at 7:01 AM, Dave Hansen <dave.hansen@intel.com> wrote:
> There are two failure modes I'm seeing: one when (failing to) allocate
> the first node's mem_map[], and a second where it oopses accessing the
> numa_distance[] table. This is the numa_distance[] one, and it happens
> even with the patch you suggested applied.
>
>> [ 0.000000] memblock_find_in_range_node():239
>> [ 0.000000] __memblock_find_range_top_down():150
>> [ 0.000000] __memblock_find_range_top_down():152 i: 600000001
>> [ 0.000000] memblock_find_in_range_node():241 ret: 2147479552
>> [ 0.000000] memblock_reserve: [0x0000007ffff000-0x0000007ffff03f] flags 0x0 numa_set_distance+0xd2/0x252

that address is wrong.

Can you post whole log with current linus' tree + two patches that I
sent out yesterday?

>> [ 0.000000] numa_distance phys: 7ffff000
>> [ 0.000000] numa_distance virt: ffff88007ffff000
>> [ 0.000000] numa_distance size: 64
>> [ 0.000000] numa_alloc_distance() accessing numa_distance[] at byte: 0
>> [ 0.000000] BUG: unable to handle kernel paging request at ffff88007ffff000


\
 
 \ /
  Last update: 2014-01-24 19:01    [W:0.065 / U:0.748 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site