Messages in this thread | | | Date | Wed, 23 Jan 2008 10:22:23 +0000 | From | Mel Gorman <> | Subject | Re: [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86 |
| |
On (23/01/08 11:04), KOSAKI Motohiro didst pronounce: > Hi mel > > > Hi > > > > > A fix[1] was merged to the x86.git tree that allowed NUMA kernels to boot > > > on normal x86 machines (and not just NUMA-Q, Summit etc.). I took a look > > > at the restrictions on setting NUMA on x86 to see if they could be lifted. > > > > Interesting! > > > > I will test tomorrow. > > Hmm... > It doesn't works on my machine. > > panic at booting at __free_pages_ok() with blow call trace. > > [<hex number>] free_all_bootmem_core > [<hex number>] mem_init > [<hex number>] alloc_large_system_hash > [<hex number>] inode_init_early > [<hex number>] start_kernel > [<hex number>] unknown_bootoption > > my machine spec > CPU: Pentium4 with HT > MEM: 512M > > I will try more investigate. > but I have no time for a while, sorry ;-) > > > BTW: > when config sparse mem turn on instead discontig mem. > panic at booting at get_pageblock_flags_group() with below call stack. > > free_initrd > free_init_pages > free_hot_cold_page >
To rule it out, can you also try with the patch below applied please? It should only make a difference on sparsemem so if discontigmem is still crashing, there is likely another problem. Assuming it crashes, please post the full dmesg output with loglevel=8 on the command line. Thanks
-- Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab
| |