Re: [XenPPC] Problems with Xen in hg tree
On Feb 7, 2007, at 5:41 PM, Jerone Young wrote: On Wed, 2007-02-07 at 17:37 -0500, Jimi Xenidis wrote: On Feb 7, 2007, at 12:48 PM, Jerone Young wrote: OK all is well...no fire here...move along. I figured out what happened. I included the vmlinux as the DOM0_IMAGE and not the zImage. It compiled through .. it is a bit surprising the Xen died though and not during loading of Dom0. So ultimately this is a USER error ;-) Thats not user error, that should work, its not smart but is should work, stripped or not stripped. So vmlinux can be like 64M which is bigger that our boo_of allocator can currently handle. This is our bug, we should simply exit gracefully. Jerone, could you file a bug with the specifics? I can though adding a check to try and catch the size (as suggested by Hollis) does not look like it got far enough in the code to catch it. I think it's the tftp limit being 64MB (though I could be wrong). I'll file a bug never the less. If this is indeed a tftp limit than it is a SLOF bug. -JX ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] Problems with Xen in hg tree
On Wed, 2007-02-07 at 17:37 -0500, Jimi Xenidis wrote: > On Feb 7, 2007, at 12:48 PM, Jerone Young wrote: > > > OK all is well...no fire here...move along. I figured out what > > happened. > > I included the vmlinux as the DOM0_IMAGE and not the zImage. It > > compiled > > through .. it is a bit surprising the Xen died though and not during > > loading of Dom0. So ultimately this is a USER error ;-) > > Thats not user error, that should work, its not smart but is should > work, stripped or not stripped. > So vmlinux can be like 64M which is bigger that our boo_of allocator > can currently handle. > This is our bug, we should simply exit gracefully. > > Jerone, could you file a bug with the specifics? I can though adding a check to try and catch the size (as suggested by Hollis) does not look like it got far enough in the code to catch it. I think it's the tftp limit being 64MB (though I could be wrong). I'll file a bug never the less. > > -JX > ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] Problems with Xen in hg tree
On Feb 7, 2007, at 12:48 PM, Jerone Young wrote: OK all is well...no fire here...move along. I figured out what happened. I included the vmlinux as the DOM0_IMAGE and not the zImage. It compiled through .. it is a bit surprising the Xen died though and not during loading of Dom0. So ultimately this is a USER error ;-) Thats not user error, that should work, its not smart but is should work, stripped or not stripped. So vmlinux can be like 64M which is bigger that our boo_of allocator can currently handle. This is our bug, we should simply exit gracefully. Jerone, could you file a bug with the specifics? -JX ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] Problems with Xen in hg tree
OK all is well...no fire here...move along. I figured out what happened. I included the vmlinux as the DOM0_IMAGE and not the zImage. It compiled through .. it is a bit surprising the Xen died though and not during loading of Dom0. So ultimately this is a USER error ;-) On Tue, 2007-02-06 at 17:58 -0600, Jerone Young wrote: > So cloning the Xen tree as of today .. you can no longer bootup Xen :-). > Here is the output on a JS21 > > The currently active flashside is: 1 (temporary) > Stopping BMC watchdog... > Trying to load: sync_console debug || root=/dev/sda3 debug from: > net ... > > Bootloader 1.5 > Reading MAC address from device: 00:14:5E:9C:1C:C5 > Requesting IP address via BOOTP: 9.3.189.7 > Requesting file "leaf4" via TFTP > Receiving data: A###A| > TFTP: Received leaf4 (65359 KBytes) > Successfully loaded > --- > OF: Xen/PPC version 3.0-unstable ([EMAIL PROTECTED]) (gcc version > 4.1.0 (SUSE Linux)) Tue Feb 6 17:18:51 CST 2007 > boot_of_init args: 0x0 0x0 0xe11027c 0xe28bed2 0x2a > boot msr: 0x10003000 > boot_of_init: _start 004000d0 _end 042b0310 0xe28bed2 > boot_of_alloc_init: pg :0x2000 of our image is different > > HANG > > > I'll be looking into this in the morning. But just an FYI to everybody. > > > ___ > Xen-ppc-devel mailing list > Xen-ppc-devel@lists.xensource.com > http://lists.xensource.com/xen-ppc-devel ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] Problems with Xen in hg tree
Last time we saw this it had to do with building optimized and the linker script simplification I attempted, so we were actually missing bits. before you do anything, try a clean build. Another possibility is some corruption, you may want to debug what the boot_of_allocator is reserving. BTW: my JS21, JS2XFW6331, is quite happy. On Feb 6, 2007, at 6:58 PM, Jerone Young wrote: So cloning the Xen tree as of today .. you can no longer bootup Xen :-). Here is the output on a JS21 The currently active flashside is: 1 (temporary) Stopping BMC watchdog... Trying to load: sync_console debug || root=/dev/sda3 debug from: net ... Bootloader 1.5 Reading MAC address from device: 00:14:5E:9C:1C:C5 Requesting IP address via BOOTP: 9.3.189.7 Requesting file "leaf4" via TFTP Receiving data: A###A| TFTP: Received leaf4 (65359 KBytes) Successfully loaded --- OF: Xen/PPC version 3.0-unstable ([EMAIL PROTECTED]) (gcc version 4.1.0 (SUSE Linux)) Tue Feb 6 17:18:51 CST 2007 boot_of_init args: 0x0 0x0 0xe11027c 0xe28bed2 0x2a boot msr: 0x10003000 boot_of_init: _start 004000d0 _end 042b0310 0xe28bed2 boot_of_alloc_init: pg :0x2000 of our image is different HANG I'll be looking into this in the morning. But just an FYI to everybody. ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
[XenPPC] Problems with Xen in hg tree
So cloning the Xen tree as of today .. you can no longer bootup Xen :-). Here is the output on a JS21 The currently active flashside is: 1 (temporary) Stopping BMC watchdog... Trying to load: sync_console debug || root=/dev/sda3 debug from: net ... Bootloader 1.5 Reading MAC address from device: 00:14:5E:9C:1C:C5 Requesting IP address via BOOTP: 9.3.189.7 Requesting file "leaf4" via TFTP Receiving data: A###A| TFTP: Received leaf4 (65359 KBytes) Successfully loaded --- OF: Xen/PPC version 3.0-unstable ([EMAIL PROTECTED]) (gcc version 4.1.0 (SUSE Linux)) Tue Feb 6 17:18:51 CST 2007 boot_of_init args: 0x0 0x0 0xe11027c 0xe28bed2 0x2a boot msr: 0x10003000 boot_of_init: _start 004000d0 _end 042b0310 0xe28bed2 boot_of_alloc_init: pg :0x2000 of our image is different HANG I'll be looking into this in the morning. But just an FYI to everybody. ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
