Re: [PATCH] gurantee DMA area for alloc_bootmem_low() ver. 2.

[Yasunori Goto <y-goto@jp.fujitsu.com>]

> >  To avoid this panic, following patch confirm allocated area, and retry
> >  if it is not in DMA.
> >  I tested this patch on my Tiger 4 and our new server.
> 
> It kills my x86_64 box:
> 
>  PID hash table entries: 4096 (order: 12, 131072 bytes)
>  time.c: Using 14.318180 MHz HPET timer.               
>  time.c: Detected 3400.236 MHz processor.
>  Console: colour VGA+ 80x25              
>  Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
>  Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)  
>  bootmem alloc of 67108864 bytes failed!                          
>  Kernel panic - not syncing: Out of memory

Thank you for your notification.

Unfortunately, I don't have x86_64 box. So, I can't trace its cause now.
I guess 67Mbyte allocation size might be trigger of its panic.
Hmm... :-(

Thanks.
-- 
Yasunori Goto 

--
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>