Re: [XenPPC] DomU panic when accessing ramdisk

[Hollis Blanchard <hollisb@xxxxxxxxxx>]

On Thu, 2006-09-14 at 15:22 -0400, poff wrote:
> Following the wiki for creating a domain, and using ramdisk.image.gz from 
> Amos,
> usually get the following panic... DomU is then repeatedly restarted, see xm 
> list
> also console output at end.
> 
> One time I got the 'Bad page state in process 'swapper''... as described in 
> wiki.
> However, the 'Bad page' dump kept repeating and after a couple pages, the 
> system
> froze.

...
> RAMDISK: Compressed image found at block 0
> Unable to handle kernel paging request for data at address 0x00200200
> Faulting instruction address: 0xc00000000007de34
> Oops: Kernel access of bad area, sig: 11 [#1]
> SMP NR_CPUS=32
> NIP: C00000000007DE34 LR: C00000000007E810 CTR: C000000000217B9C
> REGS: c0000000007fa9e0 TRAP: 0300   Tainted: G    B  (2.6.17-Xen)
> MSR: 8000000000001032 <ME,IR,DR>  CR: 24422524  XER: 60055555
> DAR: 0000000000200200, DSISR: 0000000042000000
> TASK = c0000000007f67e0[1] 'swapper' THREAD: c0000000007f8000 CPU: 0
> GPR00: 000000000000000C C0000000007FAC60 C000000000658050 C000000000740000
> GPR04: 000000000000000B C000000000540A10 0000000000100100 C000000000540A10
> GPR08: 0000000000000000 0000000000100100 C000000000740028 0000000000200200
> GPR12: 0000000000200200 C000000000533200 0000000000000000 0000000000000000
> GPR16: 0000000000000001 0000000000000000 0000000000020030 0000000000000044
> GPR20: 0000000000000001 0000000000000000 C000000000544480 0000000000000000
> GPR24: 0000000000000001 0000000000000003 8000000000009032 0000000000000002
> GPR28: 0000000000000001 0000000000000001 C00000000053F880 0000000000000000
> NIP [C00000000007DE34] .__rmqueue+0x9c/0x180
> LR [C00000000007E810] .get_page_from_freelist+0x4f4/0x564
> Call Trace:
> [C0000000007FAC60] [C0000000007FAD00] 0xc0000000007fad00 (unreliable)
> [C0000000007FAD60] [C00000000007E90C] .__alloc_pages+0x8c/0x338
> [C0000000007FAE50] [C00000000007AA00] .generic_file_buffered_write+0x184/0x864
> [C0000000007FAFF0] [C00000000007B6F0] 
> .__generic_file_aio_write_nolock+0x2b8/0x484
> [C0000000007FB120] [C00000000007BD68] .generic_file_aio_write_nolock+0x30/0xd4
> [C0000000007FB1B0] [C00000000007BE90] .generic_file_write_nolock+0x84/0xd0
> [C0000000007FB310] [C0000000000B3E10] .blkdev_file_write+0x20/0x34
> [C0000000007FB3A0] [C0000000000A6D84] .vfs_write+0xc4/0x1ec
> [C0000000007FB430] [C0000000000A6F88] .sys_write+0x4c/0x90
> [C0000000007FB4D0] [C0000000004EDA80] .flush_window+0x40/0x120
> [C0000000007FB560] [C0000000004EE294] .inflate_codes+0x630/0x65c
> [C0000000007FB670] [C0000000004EECA4] .inflate_dynamic+0x820/0x84c
> [C0000000007FBC80] [C0000000004EFFBC] .rd_load_image+0x12e8/0x1300
> [C0000000007FBDA0] [C0000000004F0224] .initrd_load+0x58/0x3b8
> [C0000000007FBE30] [C0000000004ED214] .prepare_namespace+0xc0/0x18c
> [C0000000007FBEC0] [C0000000000095B0] .init+0x3ec/0x438
> [C0000000007FBF90] [C000000000025BDC] .kernel_thread+0x4c/0x68
> Instruction dump:
> 38600000 eb81ffe0 eba1ffe8 ebc1fff0 ebe1fff8 4e800020 e92a0000 e96a0008
> 7c8407b4 386affd8 7ca72b78 7f84f800 <f92b0000> f9690008 7f892030 e80affd8
>  <0>Kernel panic - not syncing: Attempted to kill init!
>  <0>Rebooting in 180 seconds..lab082:~ #

I haven't seen this. Could you describe your platform (including memory,
steps to reproduce, bug frequency), and attach your xm config file and
boot log to a bug report please?
http://bugzilla.xensource.com/bugzilla/, and assign to me.

Thanks!

-- 
Hollis Blanchard
IBM Linux Technology Center


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