Re: [XenPPC] DomU panic when accessing ramdisk

2006-09-14 Thread Hollis Blanchard
On Thu, 2006-09-14 at 17:52 -0400, poff wrote:
> > 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.
> 
> Submitted, please let me know if need additional info 

Thanks Dan. In the future, it would be easier to read the report if you
supplied the config file and boot log as attachments (click that "Create
a New Attachment" link).

I'm not looking at this at the moment, so if anyone else wants to step
up, you're welcome:
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=768

-- 
Hollis Blanchard
IBM Linux Technology Center


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


Re: [XenPPC] DomU panic when accessing ramdisk

2006-09-14 Thread poff
> 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.

Submitted, please let me know if need additional info 

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


Re: [XenPPC] DomU panic when accessing ramdisk

2006-09-14 Thread Hollis Blanchard
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: 0xc007de34
> Oops: Kernel access of bad area, sig: 11 [#1]
> SMP NR_CPUS=32
> NIP: C007DE34 LR: C007E810 CTR: C0217B9C
> REGS: c07fa9e0 TRAP: 0300   Tainted: GB  (2.6.17-Xen)
> MSR: 80001032   CR: 24422524  XER: 6005
> DAR: 00200200, DSISR: 4200
> TASK = c07f67e0[1] 'swapper' THREAD: c07f8000 CPU: 0
> GPR00: 000C C07FAC60 C0658050 C074
> GPR04: 000B C0540A10 00100100 C0540A10
> GPR08:  00100100 C0740028 00200200
> GPR12: 00200200 C0533200  
> GPR16: 0001  00020030 0044
> GPR20: 0001  C0544480 
> GPR24: 0001 0003 80009032 0002
> GPR28: 0001 0001 C053F880 
> NIP [C007DE34] .__rmqueue+0x9c/0x180
> LR [C007E810] .get_page_from_freelist+0x4f4/0x564
> Call Trace:
> [C07FAC60] [C07FAD00] 0xc07fad00 (unreliable)
> [C07FAD60] [C007E90C] .__alloc_pages+0x8c/0x338
> [C07FAE50] [C007AA00] .generic_file_buffered_write+0x184/0x864
> [C07FAFF0] [C007B6F0] 
> .__generic_file_aio_write_nolock+0x2b8/0x484
> [C07FB120] [C007BD68] .generic_file_aio_write_nolock+0x30/0xd4
> [C07FB1B0] [C007BE90] .generic_file_write_nolock+0x84/0xd0
> [C07FB310] [C00B3E10] .blkdev_file_write+0x20/0x34
> [C07FB3A0] [C00A6D84] .vfs_write+0xc4/0x1ec
> [C07FB430] [C00A6F88] .sys_write+0x4c/0x90
> [C07FB4D0] [C04EDA80] .flush_window+0x40/0x120
> [C07FB560] [C04EE294] .inflate_codes+0x630/0x65c
> [C07FB670] [C04EECA4] .inflate_dynamic+0x820/0x84c
> [C07FBC80] [C04EFFBC] .rd_load_image+0x12e8/0x1300
> [C07FBDA0] [C04F0224] .initrd_load+0x58/0x3b8
> [C07FBE30] [C04ED214] .prepare_namespace+0xc0/0x18c
> [C07FBEC0] [C00095B0] .init+0x3ec/0x438
> [C07FBF90] [C0025BDC] .kernel_thread+0x4c/0x68
> Instruction dump:
> 3860 eb81ffe0 eba1ffe8 ebc1fff0 ebe1fff8 4e800020 e92a e96a0008
> 7c8407b4 386affd8 7ca72b78 7f84f800  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@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel