Re: [Xen-ia64-devel] kernel BUG at mm/page_alloc.c:1116!

[Isaku Yamahata <yamahata@xxxxxxxxxxxxx>]

Hello.


Presumably the memory descriptors which Xen/IA64 creates
for the domain doesn't cover xenLinux kernel text area.
If so, it is a bug of Xen/IA64.

Which domain are you trying to create, dom0 or domU?
(maybe domU. just to make sure)


Thanks.

On Mon, Jun 12, 2006 at 10:10:42AM -0400, Rodrigo Lord wrote:
> Hi!
> 
> I`m testing the xen/ia64 and the error below appears when I tryed to boot a
> virtual machine with 80 MB of memory...
> 
> kernel BUG at mm/page_alloc.c:1116!
> swapper[1]: bugcheck! 0 [1]
> Modules linked in:
> 
> Pid: 1, CPU 0, comm:              swapper
> psr : 00000010085a6010 ifs : 8000000000000288 ip  : [<a0000001000dec50>]    
> Not
> tainted
> ip is at free_pages+0xb0/0x100
> unat: 0000000000000000 pfs : 8000000000000288 rsc : 000000000000000b
> rnat: e000000003736d30 bsps: e0000000012b0480 pr  : 0000000000005a41
> ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70433f
> csd : 0000000000000000 ssd : 0000000000000000
> b0  : a0000001000dec50 b6  : 0000000000000000 b7  : a0000001004eb5c0
> f6  : 0fffbccccccccc8c00000 f7  : 0ffd9a200000000000000
> f8  : 0ffff8000000000000000 f9  : 10002a000000000000000
> f10 : 0fffbccccccccc8c00000 f11 : 1003e0000000000000000
> r1  : a000000100d63310 r2  : 0000000000000001 r3  : a000000100b810ec
> r8  : 0000000000000027 r9  : a000000100b810ec r10 : 0000000000000001
> r11 : f100000000000001 r12 : e0000000012efe20 r13 : e0000000012e8000
> r14 : 0000000000000001 r15 : 0000000000000000 r16 : f100000000004c18
> r17 : f100000000004c20 r18 : a000000100b810ec r19 : a000000100b810ec
> r20 : f100000000000001 r21 : 0000000000000001 r22 : f100000000004c18
> r23 : 000000000000000d r24 : 0000000000000001 r25 : 00000000000007ff
> r26 : 0000000000000089 r27 : 0000000000004000 r28 : 0000000000000000
> r29 : a000000100b803b8 r30 : a000000100b80398 r31 : a000000100b77fb8
> 
> Call Trace:
>  [<a000000100019260>] show_stack+0x40/0xa0
>                                 sp=e0000000012ef990 bsp=e0000000012e9108
>  [<a000000100019af0>] show_regs+0x7d0/0x800
>                                 sp=e0000000012efb60 bsp=e0000000012e90c0
>  [<a00000010003fac0>] die+0x1c0/0x3e0
>                                 sp=e0000000012efb60 bsp=e0000000012e9078
>  [<a00000010003fd20>] die_if_kernel+0x40/0x60
>                                 sp=e0000000012efb80 bsp=e0000000012e9048
>  [<a00000010003ff50>] ia64_bad_break+0x210/0x460
>                                 sp=e0000000012efb80 bsp=e0000000012e9020
>  [<a000000100067720>] xen_leave_kernel+0x0/0x3b0
>                                 sp=e0000000012efc50 bsp=e0000000012e9020
>  [<a0000001000dec50>] free_pages+0xb0/0x100
>                                 sp=e0000000012efe20 bsp=e0000000012e8fd8
>  [<a0000001000628f0>] free_initmem+0x150/0x200
>                                 sp=e0000000012efe20 bsp=e0000000012e8fb8
>  [<a000000100011130>] init+0x230/0x400
>  sp=e0000000012efe30 bsp=e0000000012e8f98
>  [<a00000010001b430>] kernel_thread_helper+0x30/0x60
>                                 sp=e0000000012efe30 bsp=e0000000012e8f70
>  [<a000000100010d40>] start_kernel_thread+0x20/0x40
>                                 sp=e0000000012efe30 bsp=e0000000012e8f70
>  <0>Kernel panic - not syncing: Attempted to kill init!
> 
> 
> 
> I tried to boot with 90MB, 128MB, and more... and it`s ok!
> Is there a minimal memory to set? Can It be a possible bug?
> 
> Thanks.

> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel

-- 
yamahata

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel