[XenPPC] Cannot boot from local disk
[XenPPC] [xenppc-unstable] [POWERPC][XEN] Remove boot wrapper, and extensive Makefile simplifications. It seems that the above change made my XenPPC unbootable from local disk. I had been booting XenPPC through yaboot by adding the following lines to /etc/yaboot.conf of SLES10. (The /boot/xen-3.0-unstable is copied from xen/xen in the build tree.) image = /boot/xen-3.0-unstable label = xen append = xen -- root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr However, after the patch, yaboot failed to load the image with the following message. Welcome to yaboot version 10.1.14-r716.SuSE booted from '/ht/[EMAIL PROTECTED],1/[EMAIL PROTECTED]' Enter help to get some basic usage information boot: xen Please wait, loading kernel... Can't find a loadable segment ! boot: Is there any workaround to boot the new image from local disk? Kiyokuni Kawachiya / IBM Tokyo Research Lab. ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] Cannot boot from local disk
Kawachiya-san, seems that your problem today is different from yesterday. You have however not answered any of my questions. So here is goes again. Kawachiya-san, can you tell us exactly what kind of js20 is this. I just learned that there are two, the 21X (of which we have some in Yorktown) and the GA2. You can tell from the machine/model type. When you boot the machine, during the firmware bring up, how many processors are reported? (for the list: I am asked this question because there was a problem coming up MP) I assume that yesterday, once you changed xen to boot UP, you were suppling the same command line to dom0 via yaboot, but what did dom0 really get? Your error message yesterday was Root-NFS: No NFS server available, giving up. VFS: Unable to mount root fs via NFS, trying floppy. Obviously today you have regressed, but still we need answers to all those questions. Kiyokuni Kawachiya wrote: [XenPPC] [xenppc-unstable] [POWERPC][XEN] Remove boot wrapper, and extensive Makefile simplifications. It seems that the above change made my XenPPC unbootable from local disk. I had been booting XenPPC through yaboot by adding the following lines to /etc/yaboot.conf of SLES10. (The /boot/xen-3.0-unstable is copied from xen/xen in the build tree.) image = /boot/xen-3.0-unstable label = xen append = xen -- root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr However, after the patch, yaboot failed to load the image with the following message. Welcome to yaboot version 10.1.14-r716.SuSE booted from '/ht/[EMAIL PROTECTED],1/[EMAIL PROTECTED]' Enter help to get some basic usage information boot: xen Please wait, loading kernel... Can't find a loadable segment ! boot: Is there any workaround to boot the new image from local disk? Kiyokuni Kawachiya / IBM Tokyo Research Lab. ___ 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] Cannot boot from local disk
Kawachiya-san, seems that your problem today is different from yesterday. You have however not answered any of my questions. Some people in this list may be confusing, so let me summarize my boot problem. I am using JS20 (884241X) to run XenPPC, which is booted from local disk through the /etc/yaboot.conf like this. # header section partition = 2 timeout = 600 default = xen # image section image = /boot/vmlinux label = linux root = /dev/hda3 append = quiet sysrq=1 insmod=sym53c8xx insmod=ipr initrd = /boot/initrd # kawatiya 2006/08/24 image = /boot/xen-3.0-unstable label = xen append = xen -- root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr However, I have several boot problems with recent versions. 1. I could not boot our internal version which is a little bit old version, but contains the SMP patch. It failed like this. : Sharing PIC with Xen6mpic: Setting up MPIC U3-MPIC version 1.2 at f804, max 4 CPUs mpic: ISU size: 124, shift: 7, mask: 7f mpic: Initializing for 124 sources mpic: Setting up HT PICs workarounds for U3/U4 mpic: - HT:01.0 [0xb8] vendor 1022 device 7450 has 4 irqs mpic: - HT:02.0 [0xb8] vendor 1022 device 7450 has 4 irqs mpic: - HT:03.0 [0xf0] vendor 1022 device 7460 has 24 irqs PID hash table entries: 1024 (order: 10, 8192 bytes) Maple: Found RTC at IO 0x1070 Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode-cache hash table entries: 16384 (order: 5, 131072 bytes) Memory: 185884k/196608k available (5296k kernel code, 10416k reserved, 1240k data, I know this is caused by the SMP patch. 2. When I reverted xen/arch/powerpc/setup.c to non-SMP version, I encountered another problem. : All bugs added by David S. Miller davem@redhat.com Root-NFS: No NFS server available, giving up. VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device NULL or unknown-block(2,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) 0Rebooting in 180 seconds.. It seems that boot parameters (root=/dev/hda3) is not passed to dom0 Linux. 3. I also cannot boot the official XenPPC in XenSource, which I already reported. : Welcome to yaboot version 10.1.14-r716.SuSE booted from '/ht/[EMAIL PROTECTED],1/[EMAIL PROTECTED]' Enter help to get some basic usage information boot: xen Please wait, loading kernel... Can't find a loadable segment ! boot: I think this is related to the boot wrapper removal. Kiyokuni KAWACHIYA / IBM Tokyo Research Laboratory ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] Cannot boot from local disk
Kawachiya-san, thank you for the exhaustive analysis! Could you make sure that you show the cmdline as both Xen _and_ Linux see it? I suspect that perhpas the order by which we evaluate the CMDLINE may be incorrect. On Oct 6, 2006, at 7:38 AM, Kiyokuni Kawachiya wrote: Kawachiya-san, seems that your problem today is different from yesterday. You have however not answered any of my questions. Some people in this list may be confusing, so let me summarize my boot problem. I am using JS20 (884241X) to run XenPPC, which is booted from local disk through the /etc/yaboot.conf like this. # header section partition = 2 timeout = 600 default = xen # image section image = /boot/vmlinux label = linux root = /dev/hda3 append = quiet sysrq=1 insmod=sym53c8xx insmod=ipr initrd = /boot/initrd # kawatiya 2006/08/24 image = /boot/xen-3.0-unstable label = xen append = xen -- root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr However, I have several boot problems with recent versions. This yaboot header looks ok. Is the insmod object comming from the disk or a ramdisk you are imbedding into your Dom0 Image? 1. I could not boot our internal version which is a little bit old version, but contains the SMP patch. It failed like this. : Sharing PIC with Xen6mpic: Setting up MPIC U3-MPIC version 1.2 at f804, max 4 CPUs mpic: ISU size: 124, shift: 7, mask: 7f mpic: Initializing for 124 sources mpic: Setting up HT PICs workarounds for U3/U4 mpic: - HT:01.0 [0xb8] vendor 1022 device 7450 has 4 irqs mpic: - HT:02.0 [0xb8] vendor 1022 device 7450 has 4 irqs mpic: - HT:03.0 [0xf0] vendor 1022 device 7460 has 24 irqs PID hash table entries: 1024 (order: 10, 8192 bytes) Maple: Found RTC at IO 0x1070 Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode-cache hash table entries: 16384 (order: 5, 131072 bytes) Memory: 185884k/196608k available (5296k kernel code, 10416k reserved, 1240k data, I know this is caused by the SMP patch. Could you synchronize the console here, there are two ways to do this: 1) add sync_console to the cmdline _before_ -- 2) apply the follow diff diff -r 701c68921ff3 xen/arch/powerpc/setup.c --- a/xen/arch/powerpc/setup.c Wed Oct 04 14:06:14 2006 -0400 +++ b/xen/arch/powerpc/setup.c Fri Oct 06 07:54:26 2006 -0400 @@ -398,7 +398,7 @@ static void __init __start_xen(multiboot /* Hide UART from DOM0 if we're using it */ serial_endboot(); -console_end_sync(); +//console_end_sync(); domain_unpause_by_systemcontroller(dom0); startup_cpu_idle_loop(); 2. When I reverted xen/arch/powerpc/setup.c to non-SMP version, I encountered another problem. : All bugs added by David S. Miller davem@redhat.com Root-NFS: No NFS server available, giving up. VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device NULL or unknown-block(2,0) Please append a correct root= boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) 0Rebooting in 180 seconds.. It seems that boot parameters (root=/dev/hda3) is not passed to dom0 Linux. this is probably a cmdline problem, almost always is 3. I also cannot boot the official XenPPC in XenSource, which I already reported. : Welcome to yaboot version 10.1.14-r716.SuSE booted from '/ht/[EMAIL PROTECTED],1/[EMAIL PROTECTED]' Enter help to get some basic usage information boot: xen Please wait, loading kernel... Can't find a loadable segment ! boot: I think this is related to the boot wrapper removal. It probably is, which image do you copy for yaboot to use? can you try: $ objcopy -S xen/xen-syms xen/xen.yaboot and have yaboot load xen.yaboot I seem to recall yaboot having difficulties with 32bit images, I'm surprised that the change sa made any difference. -JX ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] Cannot boot from local disk
On Oct 6, 2006, at 8:25 AM, Kiyokuni Kawachiya wrote:
Could you make sure that you show the cmdline as both Xen _and_ Linux
see it? I suspect that perhpas the order by which we evaluate the
CMDLINE may be incorrect.
Jimi,
Let me first say that my analysis is based on our internal version,
since
the official version does not boot from local disk by another problem.
AFAIK, the internal version is Xen with the SMP patch that has been
sent to this list,
Is there more?
Following is the boot log with old XenPPC.
bootargs = xen -- root=/dev/hda3 sysrq=1 insmod=sym53c8xx
insmod=ipr
boot_of_module: Dom0 is linked in: 0x44edbc[size 0x29954d]
[...]
And, this is the log with new XenPPC.
bootargs = xen
boot_of_module: Dom0 is linked in: 0x44f6bc[size 0x29954d]
mod0: 177 E L F
[...]
Yaboot actually re assigns the /chosen/bootargs property in the
firmware.
It is possible that the new logic for selecting which command line to
use is broken.
I'll bet it is this clause in boot_of.c:
464 if (builtin_cmdline[0] == '\0') {
465 rc = of_getprop(bof_chosen, bootargs, builtin_cmdline,
466 CONFIG_CMDLINE_SIZE);
467 if (rc CONFIG_CMDLINE_SIZE)
468 of_panic(bootargs[] not big enough for /chosen/bootargs
\n);
469 }
I assume you are not building with CMDLINE= in you make command?
It seems we have lost the ability to make (builtin_cmdline[0] == '\0')
Kawachiya-san, if you force this if clause to be true you should be
fine. We'll get it fixed soon enuff.
-JX
___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel
insmod? Was: [XenPPC] Cannot boot from local disk
splitting emails On Oct 6, 2006, at 7:59 AM, Jimi Xenidis wrote: Kawachiya-san, thank you for the exhaustive analysis! On Oct 6, 2006, at 7:38 AM, Kiyokuni Kawachiya wrote: Kawachiya-san, seems that your problem today is different from yesterday. You have however not answered any of my questions. Some people in this list may be confusing, so let me summarize my boot problem. I am using JS20 (884241X) to run XenPPC, which is booted from local disk through the /etc/yaboot.conf like this. # header section partition = 2 timeout = 600 default = xen # image section image = /boot/vmlinux label = linux root = /dev/hda3 append = quiet sysrq=1 insmod=sym53c8xx insmod=ipr initrd = /boot/initrd # kawatiya 2006/08/24 image = /boot/xen-3.0-unstable label = xen append = xen -- root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr However, I have several boot problems with recent versions. This yaboot header looks ok. Is the insmod object comming from the disk or a ramdisk you are imbedding into your Dom0 Image? I'd be interested in this answer -JX ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
SMP patch? Was: [XenPPC] Cannot boot from local disk
More splits On Oct 6, 2006, at 7:59 AM, Jimi Xenidis wrote: Kawachiya-san, thank you for the exhaustive analysis! On Oct 6, 2006, at 7:38 AM, Kiyokuni Kawachiya wrote: 1. I could not boot our internal version which is a little bit old version, but contains the SMP patch. It failed like this. : Sharing PIC with Xen6mpic: Setting up MPIC U3-MPIC version 1.2 at f804, max 4 CPUs mpic: ISU size: 124, shift: 7, mask: 7f mpic: Initializing for 124 sources mpic: Setting up HT PICs workarounds for U3/U4 mpic: - HT:01.0 [0xb8] vendor 1022 device 7450 has 4 irqs mpic: - HT:02.0 [0xb8] vendor 1022 device 7450 has 4 irqs mpic: - HT:03.0 [0xf0] vendor 1022 device 7460 has 24 irqs PID hash table entries: 1024 (order: 10, 8192 bytes) Maple: Found RTC at IO 0x1070 Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode-cache hash table entries: 16384 (order: 5, 131072 bytes) Memory: 185884k/196608k available (5296k kernel code, 10416k reserved, 1240k data, I know this is caused by the SMP patch. Could you synchronize the console here, there are two ways to do this: 1) add sync_console to the cmdline _before_ -- 2) apply the follow diff diff -r 701c68921ff3 xen/arch/powerpc/setup.c --- a/xen/arch/powerpc/setup.c Wed Oct 04 14:06:14 2006 -0400 +++ b/xen/arch/powerpc/setup.c Fri Oct 06 07:54:26 2006 -0400 @@ -398,7 +398,7 @@ static void __init __start_xen(multiboot /* Hide UART from DOM0 if we're using it */ serial_endboot(); -console_end_sync(); +//console_end_sync(); domain_unpause_by_systemcontroller(dom0); startup_cpu_idle_loop(); Do you have output for this? -JX ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Yaboot stripped image Was: [XenPPC] Cannot boot from local disk
On Oct 6, 2006, at 7:59 AM, Jimi Xenidis wrote: Kawachiya-san, thank you for the exhaustive analysis! 3. I also cannot boot the official XenPPC in XenSource, which I already reported. : Welcome to yaboot version 10.1.14-r716.SuSE booted from '/ht/[EMAIL PROTECTED],1/[EMAIL PROTECTED]' Enter help to get some basic usage information boot: xen Please wait, loading kernel... Can't find a loadable segment ! boot: I think this is related to the boot wrapper removal. It probably is, which image do you copy for yaboot to use? can you try: $ objcopy -S xen/xen-syms xen/xen.yaboot and have yaboot load xen.yaboot I seem to recall yaboot having difficulties with 32bit images, I'm surprised that the change sa made any difference. can you tell us if this works? -JX ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] Cannot boot from local disk
I took a look at the situation. It boils down to this: 1. In the internal Xen tree, there is a bug (my fault) in which firmware bootargs are overridden by the builtin xen bootarg. This is fixed (by Hollis) in the current public Xen tree. 2. In the internal Xen tree, the SMP patch apparently causes dom0 Linux to fail on Kawachiya's JS20, but no other JS20. 3. In the public Xen tree, the 32-bit objcopy produces an image that Kawachiya's yaboot apparently cannot load. The catch-22 is that if Maria updates the internal tree to get the fixes in the public tree, the bootargs problem will go away, but the yaboot problem will appear. So we really need to know what yaboot is complaining about. ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
CMDLINE Was: [XenPPC] Cannot boot from local disk
I just returned home.
I will answer as much as possible although my remote environment is poor.
Jimi Xenidis [EMAIL PROTECTED] wrote on 2006/10/06 21:46:15:
AFAIK, the internal version is Xen with the SMP patch that has been
sent to this list,
Is there more?
This inernal version is maintained by Maria.
It seems to be a little-bit old than the official tree, but contains the
SMP patch.
I'll bet it is this clause in boot_of.c:
464 if (builtin_cmdline[0] == '\0') {
465 rc = of_getprop(bof_chosen, bootargs, builtin_cmdline,
466 CONFIG_CMDLINE_SIZE);
467 if (rc CONFIG_CMDLINE_SIZE)
468 of_panic(bootargs[] not big enough for /chosen/bootargs
\n);
469 }
I tried this, and it works!
#if 0 //original
if (wrapper_builtin_cmdline[0] != 0) {
strlcpy(bootargs, wrapper_builtin_cmdline, sizeof(bootargs));
} else if (builtin_cmdline[0] != 0) {
strlcpy(bootargs, builtin_cmdline, sizeof(bootargs));
} else {
rc = of_getprop(bof_chosen, bootargs, bootargs, sizeof
(bootargs));
}
#else //modified
of_printf( wrapper_builtin_cmdline=%s\n,
wrapper_builtin_cmdline
);
of_printf( builtin_cmdline=%s\n, builtin_cmdline);
rc = of_getprop(bof_chosen, bootargs, bootargs, sizeof
(bootargs));
#endif
With this, cmdline is correctly passed to dom0 Linux.
The boot message is like this
wrapper_builtin_cmdline=xen
builtin_cmdline=xen
bootargs = xen -- root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr
Kawachiya
___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] Cannot boot from local disk
I took a look at the situation. It boils down to this: 1. In the internal Xen tree, there is a bug (my fault) in which firmware bootargs are overridden by the builtin xen bootarg. This is fixed (by Hollis) in the current public Xen tree. Thanks, I just checked it. 2. In the internal Xen tree, the SMP patch apparently causes dom0 Linux to fail on Kawachiya's JS20, but no other JS20. One possible reason is the difference of JS20 blade. My JS20 is 884241X, and others are 21X. 3. In the public Xen tree, the 32-bit objcopy produces an image that Kawachiya's yaboot apparently cannot load. The catch-22 is that if Maria updates the internal tree to get the fixes in the public tree, the bootargs problem will go away, but the yaboot problem will appear. So we really need to know what yaboot is complaining about. I will try Jimi's suggestion from now. Kawachiya ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: insmod? Was: [XenPPC] Cannot boot from local disk
through the /etc/yaboot.conf like this. # header section partition = 2 timeout = 600 default = xen # image section image = /boot/vmlinux label = linux root = /dev/hda3 append = quiet sysrq=1 insmod=sym53c8xx insmod=ipr initrd = /boot/initrd # kawatiya 2006/08/24 image = /boot/xen-3.0-unstable label = xen append = xen -- root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr This yaboot header looks ok. Is the insmod object comming from the disk or a ramdisk you are imbedding into your Dom0 Image? Actually, the insmod options were just copied from the original boot stub labeled linux, which was created by SLES10 installer. Perhaps they may be unnecessary for dom0 Linux, but old XenPPC's worked well even with this setting. Kawachiya ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] Cannot boot from local disk
On Oct 6, 2006, at 10:38 AM, Kiyokuni Kawachiya wrote:
3. In the public Xen tree, the 32-bit objcopy produces an image that
Kawachiya's yaboot apparently cannot load.
The catch-22 is that if Maria updates the internal tree to get the
fixes
in the public tree, the bootargs problem will go away, but the yaboot
problem will appear.
So we really need to know what yaboot is complaining about.
I will try Jimi's suggestion from now.
Kawachiya-san,
Please try the following patch against the yaboot boot.
diff -r f9631d8c3e3c xen/arch/powerpc/Makefile
--- a/xen/arch/powerpc/Makefile Thu Oct 05 16:06:42 2006 -0500
+++ b/xen/arch/powerpc/Makefile Fri Oct 06 10:57:24 2006 -0400
@@ -96,7 +96,7 @@ cmdline.o: cmdline.dep
cmdline.o: cmdline.dep
cmdline.o: CFLAGS += -DCMDLINE=\$(FULL_CMDLINE)\
-TARGET_OPTS = $(OMAGIC) -Wl,-Ttext,0x40,-T,xen.lds
+TARGET_OPTS = $(OMAGIC) -Wl,-T,xen.lds
TARGET_OPTS += start.o $(ALL_OBJS)
.xen-syms: start.o $(ALL_OBJS) xen.lds
diff -r f9631d8c3e3c xen/arch/powerpc/xen.lds.S
--- a/xen/arch/powerpc/xen.lds.SThu Oct 05 16:06:42 2006 -0500
+++ b/xen/arch/powerpc/xen.lds.SFri Oct 06 10:57:24 2006 -0400
@@ -17,7 +17,7 @@ SECTIONS
SECTIONS
{
/* Read-only sections, merged into text segment: */
- PROVIDE (__executable_start = 0x1000); . = 0x1000 +
SIZEOF_HEADERS;
+ PROVIDE (__executable_start = 0x40); . = 0x40 +
SIZEOF_HEADERS;
.interp : { *(.interp) } :text
.hash : { *(.hash) }
.dynsym : { *(.dynsym) }
___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel
Re: Yaboot stripped image Was: [XenPPC] Cannot boot from local disk
It probably is, which image do you copy for yaboot to use? I usually copied xen/xen to /boot/xen-3.0-unstable, and specified it in yaboot.conf. can you try: $ objcopy -S xen/xen-syms xen/xen.yaboot and have yaboot load xen.yaboot I tried, but the situation is same. Welcome to yaboot version 10.1.14-r716.SuSE booted from '/ht/[EMAIL PROTECTED],1/[EMAIL PROTECTED]' Enter help to get some basic usage information boot: xen Please wait, loading kernel... Can't find a loadable segment ! boot: xen Please wait, loading kernel... Can't find a loadable segment ! boot: One thing I noticed is that objdump -h result is very different between the bootable and non-bootable xen images. (Bootable xen/xen) wsjs4 XenPPC.watson.ok/xen-ppc objdump -h xen/xen xen/xen: file format elf32-powerpc Sections: Idx Name Size VMA LMA File off Algn 0 .text 0040 0040 0040 0078 2**3 CONTENTS, ALLOC, LOAD, CODE 1 .data 00311e98 00400100 00400100 0178 2**3 CONTENTS, ALLOC, LOAD, DATA 2 .debug_aranges 0020 00312010 2**3 CONTENTS, READONLY, DEBUGGING 3 .debug_info 0069 00312030 2**0 CONTENTS, READONLY, DEBUGGING 4 .debug_abbrev 0014 00312099 2**0 CONTENTS, READONLY, DEBUGGING 5 .debug_line 004b 003120ad 2**0 CONTENTS, READONLY, DEBUGGING (Non-bootable xen/xen) wsjs4 XenPPC.xensource/xen-ppc objdump -h xen/xen xen/xen: file format elf32-powerpc Sections: Idx Name Size VMA LMA File off Algn 0 .text 00031a10 0040 0040 0100 2**7 CONTENTS, ALLOC, LOAD, CODE 1 .init.text3e50 00431a10 00431a10 00031b10 2**4 CONTENTS, ALLOC, LOAD, READONLY, CODE 2 .rodata 5670 00435860 00435860 00035960 2**3 CONTENTS, ALLOC, LOAD, READONLY, DATA 3 __ex_table0050 0043aed0 0043aed0 0003afd0 2**3 CONTENTS, ALLOC, LOAD, READONLY, DATA 4 .data 002a8e00 0044b000 0044b000 0004b100 2**8 CONTENTS, ALLOC, LOAD, DATA 5 .data.rel 0080 006f3e00 006f3e00 002f3f00 2**3 CONTENTS, ALLOC, LOAD, DATA 6 .init.data0140 006f3e80 006f3e80 002f3f80 2**3 CONTENTS, ALLOC, LOAD, DATA 7 .data.rel.local 0158 006f3fc0 006f3fc0 002f40c0 2**3 CONTENTS, ALLOC, LOAD, DATA 8 .data.rel.ro 0018 006f4118 006f4118 002f4218 2**3 CONTENTS, ALLOC, LOAD, DATA 9 .data.rel.ro.local 0010 006f4130 006f4130 002f4230 2**3 CONTENTS, ALLOC, LOAD, DATA 10 __builtin_cmdline 0200 006f4140 006f4140 002f4240 2**3 CONTENTS, ALLOC, LOAD, DATA 11 .setup.init 0260 006f4340 006f4340 002f4440 2**3 CONTENTS, ALLOC, LOAD, DATA 12 .initcall.init 0030 006f45a0 006f45a0 002f46a0 2**3 CONTENTS, ALLOC, LOAD, DATA 13 .inithcall.text 00b0 006f45d0 006f45d0 002f46d0 2**3 CONTENTS, ALLOC, LOAD, DATA 14 .data.percpu 0484 006f4680 006f4680 002f4780 2**7 CONTENTS, ALLOC, LOAD, DATA 15 .opd 3a68 00708000 00708000 00308100 2**3 CONTENTS, ALLOC, LOAD, DATA 16 .got 26c8 0070ba68 0070ba68 0030bb68 2**3 CONTENTS, ALLOC, LOAD, DATA 17 .bss 00013ac8 0070e180 0070e180 0030e230 2**7 ALLOC 18 .comment 08f6 0030e230 2**0 CONTENTS, READONLY 19 .debug_aranges 1120 0030eb30 2**4 CONTENTS, READONLY, DEBUGGING 20 .debug_pubnames 2ac4 0030fc50 2**0 CONTENTS, READONLY, DEBUGGING 21 .debug_info 0008c82c 00312714 2**0 CONTENTS, READONLY, DEBUGGING 22 .debug_abbrev e1ff 0039ef40 2**0 CONTENTS, READONLY, DEBUGGING 23 .debug_line 000148ef 003ad13f 2**0 CONTENTS, READONLY, DEBUGGING 24 .debug_frame 5c78 003c1a30 2**3 CONTENTS, READONLY, DEBUGGING 25 .debug_str7841 003c76a8 2**0 CONTENTS, READONLY, DEBUGGING 26 .debug_loc0004418f 003ceee9 2**0 CONTENTS, READONLY, DEBUGGING 27 .debug_ranges 00012f80 00413078 2**0 CONTENTS, READONLY, DEBUGGING Kawachiya ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: Yaboot stripped image Was: [XenPPC] Cannot boot from local disk
On Oct 6, 2006, at 11:05 AM, Kiyokuni Kawachiya wrote: It probably is, which image do you copy for yaboot to use? I usually copied xen/xen to /boot/xen-3.0-unstable, and specified it in yaboot.conf. can you try: $ objcopy -S xen/xen-syms xen/xen.yaboot and have yaboot load xen.yaboot I tried, but the situation is same. One thing I noticed is that objdump -h result is very different between the bootable and non-bootable xen images. (Bootable xen/xen) wsjs4 XenPPC.watson.ok/xen-ppc objdump -h xen/xen xen/xen: file format elf32-powerpc Sections: Idx Name Size VMA LMA File off Algn 0 .text 0040 0040 0040 0078 2**3 CONTENTS, ALLOC, LOAD, CODE (Non-bootable xen/xen) wsjs4 XenPPC.xensource/xen-ppc objdump -h xen/xen xen/xen: file format elf32-powerpc Sections: Idx Name Size VMA LMA File off Algn 0 .text 00031a10 0040 0040 0100 2**7 CONTENTS, ALLOC, LOAD, CODE yeah even weirder is: $ objdump -p xen xen: file format elf32-powerpc Program Header: LOAD off0x vaddr 0x003fff00 paddr 0x003fff00 align 2**8 filesz 0x000ab0d8 memsz 0x000bebc8 flags rwx I sent a patch in a previous mail, could you try that? -JX ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] Cannot boot from local disk
On Fri, 2006-10-06 at 10:08 -0400, Amos Waterland wrote: I took a look at the situation. It boils down to this: 3. In the public Xen tree, the 32-bit objcopy produces an image that Kawachiya's yaboot apparently cannot load. The catch-22 is that if Maria updates the internal tree to get the fixes in the public tree, the bootargs problem will go away, but the yaboot problem will appear. So we really need to know what yaboot is complaining about. Do we really need yaboot? (Just looking for a workaround...) -- 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] Cannot boot from local disk
Kawachiya-san,
Please try the following patch against the yaboot boot.
I rebuilt xen with the patches, and tried to boot with xen/xen, but the
situation was same.
diff -r f9631d8c3e3c xen/arch/powerpc/Makefile
--- a/xen/arch/powerpc/Makefile Thu Oct 05 16:06:42 2006 -0500
+++ b/xen/arch/powerpc/Makefile Fri Oct 06 10:57:24 2006 -0400
@@ -96,7 +96,7 @@ cmdline.o: cmdline.dep
cmdline.o: cmdline.dep
cmdline.o: CFLAGS += -DCMDLINE=\$(FULL_CMDLINE)\
-TARGET_OPTS = $(OMAGIC) -Wl,-Ttext,0x40,-T,xen.lds
+TARGET_OPTS = $(OMAGIC) -Wl,-T,xen.lds
TARGET_OPTS += start.o $(ALL_OBJS)
.xen-syms: start.o $(ALL_OBJS) xen.lds
diff -r f9631d8c3e3c xen/arch/powerpc/xen.lds.S
--- a/xen/arch/powerpc/xen.lds.S Thu Oct 05 16:06:42 2006 -0500
+++ b/xen/arch/powerpc/xen.lds.S Fri Oct 06 10:57:24 2006 -0400
@@ -17,7 +17,7 @@ SECTIONS
SECTIONS
{
/* Read-only sections, merged into text segment: */
- PROVIDE (__executable_start = 0x1000); . = 0x1000 +
SIZEOF_HEADERS;
+ PROVIDE (__executable_start = 0x40); . = 0x40 +
SIZEOF_HEADERS;
.interp : { *(.interp) } :text
.hash : { *(.hash) }
.dynsym : { *(.dynsym) }
___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] Cannot boot from local disk
Do we really need yaboot? (Just looking for a workaround...) Kawachiya cannot netboot for political reasons in his lab, so he actually installs Xen on his Local Disk. We should certainly support this booting model and so he is sorta stuck with a bootloader and yaboot is what we are all stuck with ATM. I'm sorry for it. It is not so easy in our lab to run my own BOOTP server. Is there anyone else here booting XenPPC from locak disk? I thought it is one of the easiest way to work with XenPPC. Kawachiya ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: SMP patch? Was: [XenPPC] Cannot boot from local disk
Could you synchronize the console here, there are two ways to do this: 1) add sync_console to the cmdline _before_ -- 2) apply the follow diff Do you have output for this? I did this with 1), and this is the log. : *** : Setup Done [boot]0015 Setup Done Built 1 zonelists. Total pages: 49152 Kernel command line: root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr Sharing PIC with Xen6mpic: Setting up MPIC U3-MPIC version 1.2 at f804, max 4 CPUs mpic: ISU size: 124, shift: 7, mask: 7f mpic: Initializing for 124 sources mpic: Setting up HT PICs workarounds for U3/U4 mpic: - HT:01.0 [0xb8] vendor 1022 device 7450 has 4 irqs mpic: - HT:02.0 [0xb8] vendor 1022 device 7450 has 4 irqs mpic: - HT:03.0 [0xf0] vendor 1022 device 7460 has 24 irqs PID hash table entries: 1024 (order: 10, 8192 bytes) Maple: Found RTC at IO 0x1070 Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode-cache hash table entries: 16384 (order: 5, 131072 bytes) Memory: 185764k/196608k available (5360k kernel code, 10500k reserved, 1256k data, 562k bss, 244k init) Mount-cache hash table entries: 256 Brought up 1 CPUs smp_xen_setup_cpu(0) migration_cost=0 grant table at c0708000 Grant table initialized NET: Registered protocol family 16 *** : Linux ppc64 *** : 2.6.17-Xen Failed to request PCI IO region on PCI domain IDE Fixup IRQ: Can't find IO-APIC ! IOMMU table initialized, virtual merging enabled - maple_pcibios_fixup - maple_pcibios_fixup SCSI subsystem initialized NET: Registered protocol family 2 (hangs here) I also attach the complete boot log below. (See attached file: bootlog.txt) bootlog.txt Description: Binary data ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: Yaboot stripped image Was: [XenPPC] Cannot boot from local disk
Hollis Blanchard [EMAIL PROTECTED] wrote on 2006/10/07 01:26:38:
On Fri, 2006-10-06 at 11:04 -0500, Hollis Blanchard wrote:
diff -r 48840bbe607d xen/arch/powerpc/xen.lds.S
--- a/xen/arch/powerpc/xen.lds.STue Sep 12 14:28:16 2006 -0500
+++ b/xen/arch/powerpc/xen.lds.SFri Oct 06 10:31:48 2006 -0500
@@ -12,7 +12,7 @@ SEARCH_DIR(=/usr/local/lib64); SEARCH_
__DYNAMIC = 0;*/
PHDRS
{
- text PT_LOAD FILEHDR PHDRS;
+ text PT_LOAD;
}
SECTIONS
{
I take it back; this does indeed solve the problem. Kawachiya-san,
please confirm:
Wow, this fixed the problem. Yaboot can load the image.
Thanks!
Kawachiya
___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel
[XenPPC] [xenppc-unstable] [POWERPC][XEN] Fix yaboot loading and other linker script tweaks.
# HG changeset patch
# User Hollis Blanchard [EMAIL PROTECTED]
# Node ID a41b8cd01ad287d60a5e59ccffa23b5dd8837af8
# Parent f9631d8c3e3c38cd618003487e5bd21b4a0acb5d
[POWERPC][XEN] Fix yaboot loading and other linker script tweaks.
yaboot refuses to load segments at file offset 0, so move the ELF headers out
of our text segment. Also hardcode the link address in the linker script, and
remove the now-inaccurate start/end comments.
Signed-off-by: Hollis Blanchard [EMAIL PROTECTED]
---
xen/arch/powerpc/Makefile |2 +-
xen/arch/powerpc/xen.lds.S |8 ++--
2 files changed, 3 insertions(+), 7 deletions(-)
diff -r f9631d8c3e3c -r a41b8cd01ad2 xen/arch/powerpc/Makefile
--- a/xen/arch/powerpc/Makefile Thu Oct 05 16:06:42 2006 -0500
+++ b/xen/arch/powerpc/Makefile Fri Oct 06 12:15:06 2006 -0500
@@ -96,7 +96,7 @@ cmdline.o: cmdline.dep
cmdline.o: cmdline.dep
cmdline.o: CFLAGS += -DCMDLINE=\$(FULL_CMDLINE)\
-TARGET_OPTS = $(OMAGIC) -Wl,-Ttext,0x40,-T,xen.lds
+TARGET_OPTS = $(OMAGIC) -Wl,-T,xen.lds
TARGET_OPTS += start.o $(ALL_OBJS)
.xen-syms: start.o $(ALL_OBJS) xen.lds
diff -r f9631d8c3e3c -r a41b8cd01ad2 xen/arch/powerpc/xen.lds.S
--- a/xen/arch/powerpc/xen.lds.SThu Oct 05 16:06:42 2006 -0500
+++ b/xen/arch/powerpc/xen.lds.SFri Oct 06 12:15:06 2006 -0500
@@ -12,12 +12,12 @@ SEARCH_DIR(=/usr/local/lib64); SEARCH_
__DYNAMIC = 0;*/
PHDRS
{
- text PT_LOAD FILEHDR PHDRS;
+ text PT_LOAD;
}
SECTIONS
{
+ . = 0x0040;
/* Read-only sections, merged into text segment: */
- PROVIDE (__executable_start = 0x1000); . = 0x1000 + SIZEOF_HEADERS;
.interp : { *(.interp) } :text
.hash : { *(.hash) }
.dynsym : { *(.dynsym) }
@@ -111,8 +111,6 @@ SECTIONS
SORT(CONSTRUCTORS)
}
- /* Xen addition */
-
. = ALIGN(32);
__setup_start = .;
.setup.init : { *(.setup.init) }
@@ -130,8 +128,6 @@ SECTIONS
. = __per_cpu_start + (NR_CPUS PERCPU_SHIFT);
. = ALIGN(STACK_SIZE);
__per_cpu_end = .;
-
- /* end Xen addition */
.data1 : { *(.data1) }
.tdata : { *(.tdata .tdata.* .gnu.linkonce.td.*) }
___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel
[XenPPC] [linux-ppc-2.6] [POWERPC][LINUX][XEN] fix typo in HYPERVISOR_memory_op() message.
# HG changeset patch # User Hollis Blanchard [EMAIL PROTECTED] # Node ID f7363a56e7c7bf0acd2a48a0e056184afc5ee23f # Parent 933613959bf6a8e48a43e1cd93d4afae4a660ec8 [POWERPC][LINUX][XEN] fix typo in HYPERVISOR_memory_op() message. Signed-off-by: Tony Breeds [EMAIL PROTECTED] Signed-off-by: Hollis Blanchard [EMAIL PROTECTED] --- arch/powerpc/platforms/xen/hcall.c |2 +- 1 files changed, 1 insertion(+), 1 deletion(-) diff -r 933613959bf6 -r f7363a56e7c7 arch/powerpc/platforms/xen/hcall.c --- a/arch/powerpc/platforms/xen/hcall.cWed Oct 04 11:20:16 2006 -0400 +++ b/arch/powerpc/platforms/xen/hcall.cFri Oct 06 12:30:31 2006 -0500 @@ -514,7 +514,7 @@ int HYPERVISOR_memory_op(unsigned int cm cmd, NULL); break; default: - printk(KERN_ERR %s: unknown grant table op %d\n, __func__, cmd); + printk(KERN_ERR %s: unknown memory op %d\n, __func__, cmd); ret = -ENOSYS; } xencomm_free(op_desc); ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] xm-test can panic Xen on JS20
Similar panic whenever 'shutdown -h' on JS20 (using local ide for root fs): ... /dev/hda2 umounted done done Shutting down MD Raiddone Stopping udevd: done proc umounted The system will be halted immediately. Synchronizing SCSI cache for disk sda: Shutdown: hdc Shutdown: hda Power down. (XEN) [F960] 004246C4 .debugger_trap_immediate+0x18/0x28 (XEN) [F9E0] 004245E0 .dom0_shutdown+0x20/0xec (XEN) [FA70] 00405ACC .domain_shutdown+0x44/0x128 (XEN) [FB00] 004232DC .do_sched_op+0x15c/0x2e8 (XEN) [FBF0] 00439388 .hcall_xen+0xc4/0xf0 (XEN) [FC90] 004394A4 .do_hcall+0x54/0x84 (XEN) [FD20] 0044C278 ex_hcall_continued+0xe4/0xf4 (XEN) [00437EC8] 800100017C0802A6 (XEN) SP (60004bd8) is not in xen space (XEN) program_exception: type: 0x700 (XEN) [ Xen-3.0-unstable ] (XEN) CPU: DOMID: (XEN) pc 004246c4 msr 90029002 (XEN) lr 004246c4 ctr 0042f15c (XEN) srr0 srr1 (XEN) r00: 004246c4 f960 0074cb38 90009002 (XEN) r04: 0001 (XEN) r08: 0075229c 0075229c 00752228 (XEN) r12: 00439450 9080 1007 0001 (XEN) r16: 100a 100aa0b0 fff6 (XEN) r20: 0001 (XEN) r24: 1001 0001 4000 (XEN) r28: cb5a3b80 fd90 c0542160 f960 (XEN) dar 0xd8008016, dsisr 0x0220 (XEN) hid4 0x6240 (XEN) ---[ backtrace ]--- (XEN) [F9E0] 004245E0 .dom0_shutdown+0x20/0xec (XEN) [FA70] 00405ACC .domain_shutdown+0x44/0x128 (XEN) [FB00] 004232DC .do_sched_op+0x15c/0x2e8 (XEN) [FBF0] 00439388 .hcall_xen+0xc4/0xf0 (XEN) [FC90] 004394A4 .do_hcall+0x54/0x84 (XEN) [FD20] 0044C278 ex_hcall_continued+0xe4/0xf4 (XEN) [00437EC8] 800100017C0802A6 (XEN) SP (60004bd8) is not in xen space (XEN) machine_halt called (XEN) machine_halt failed, manual powercycle required! ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] Cannot boot from local disk
Good question, I think it may do iso-9660 and fat16, and I heard that ext2 might be supported, but I'd be surprised if SLOF can do reiserfs It can do ext2/ext3 and fat12/fat16 (both versions)/fat32. The various CD and DVD filesystems are next on the list of filesystems we want to support, for obvious reasons ;-) Segher ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] xm-test can panic Xen on JS20
Not really similar to Tony's. Dan yours is known, Xen is setup to trap if Dom0 shutsdown _and_ crash_debug=y -JX On Oct 6, 2006, at 5:03 PM, poff wrote: Similar panic whenever 'shutdown -h' on JS20 (using local ide for root fs): ... /dev/hda2 umounted done d one Shutting down MD Raiddone Stopping udevd: done proc umounted The system will be halted immediately. Synchronizing SCSI cache for disk sda: Shutdown: hdc Shutdown: hda Power down. (XEN) [F960] 004246C4 .debugger_trap_immediate +0x18/0x28 (XEN) [F9E0] 004245E0 .dom0_shutdown+0x20/0xec (XEN) [FA70] 00405ACC .domain_shutdown+0x44/0x128 (XEN) [FB00] 004232DC .do_sched_op+0x15c/0x2e8 (XEN) [FBF0] 00439388 .hcall_xen+0xc4/0xf0 (XEN) [FC90] 004394A4 .do_hcall+0x54/0x84 (XEN) [FD20] 0044C278 ex_hcall_continued+0xe4/0xf4 (XEN) [00437EC8] 800100017C0802A6 (XEN) SP (60004bd8) is not in xen space (XEN) program_exception: type: 0x700 (XEN) [ Xen-3.0-unstable ] (XEN) CPU: DOMID: (XEN) pc 004246c4 msr 90029002 (XEN) lr 004246c4 ctr 0042f15c (XEN) srr0 srr1 (XEN) r00: 004246c4 f960 0074cb38 90009002 (XEN) r04: 0001 (XEN) r08: 0075229c 0075229c 00752228 (XEN) r12: 00439450 9080 1007 0001 (XEN) r16: 100a 100aa0b0 fff6 (XEN) r20: 0001 (XEN) r24: 1001 0001 4000 (XEN) r28: cb5a3b80 fd90 c0542160 f960 (XEN) dar 0xd8008016, dsisr 0x0220 (XEN) hid4 0x6240 (XEN) ---[ backtrace ]--- (XEN) [F9E0] 004245E0 .dom0_shutdown+0x20/0xec (XEN) [FA70] 00405ACC .domain_shutdown+0x44/0x128 (XEN) [FB00] 004232DC .do_sched_op+0x15c/0x2e8 (XEN) [FBF0] 00439388 .hcall_xen+0xc4/0xf0 (XEN) [FC90] 004394A4 .do_hcall+0x54/0x84 (XEN) [FD20] 0044C278 ex_hcall_continued+0xe4/0xf4 (XEN) [00437EC8] 800100017C0802A6 (XEN) SP (60004bd8) is not in xen space (XEN) machine_halt called (XEN) machine_halt failed, manual powercycle required! ___ 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] [PATCH] Improve presentation of objcopy output
This makes it easier to grep log files, and just looks a lot better in the console output of a make. Signed-off-by: Amos Waterland [EMAIL PROTECTED] --- Makefile |6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff -r a41b8cd01ad2 xen/arch/powerpc/Makefile --- a/xen/arch/powerpc/Makefile Fri Oct 06 12:15:06 2006 -0500 +++ b/xen/arch/powerpc/Makefile Fri Oct 06 17:45:51 2006 -0400 @@ -119,11 +119,9 @@ xen-syms.o: xen-syms.S $(CC) $(CFLAGS) $(TARGET_OPTS) xen-syms.o -o $@ # our firmware only loads 32-bit ELF files +OCPYFLAGS= --input-target=elf64-powerpc --output-target=elf32-powerpc $(TARGET): $(TARGET)-syms - $(CROSS_COMPILE)objcopy \ - --input-target=elf64-powerpc \ - --output-target=elf32-powerpc \ - $^ $@ + $(CROSS_COMPILE)objcopy $(OCPYFLAGS) $^ $@ asm-offsets.s: $(TARGET_SUBARCH)/asm-offsets.c $(HDRS) $(CC) $(CFLAGS) -S -o $@ $ ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: SMP patch? Was: [XenPPC] Cannot boot from local disk
On Sat, Oct 07, 2006 at 01:36:18AM +0900, Kiyokuni Kawachiya wrote: Could you synchronize the console here, there are two ways to do this: 1) add sync_console to the cmdline _before_ -- 2) apply the follow diff Do you have output for this? I did this with 1), and this is the log. Thanks for the log, it helps. Can you please boot the same kernel (the one that hangs) with the `nosmp' option passed to Xen? ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Fw: SMP patch? Was: [XenPPC] Cannot boot from local disk
(I failed to post this to the ML) From: Kiyokuni Kawachiya on 2006/10/07 11:33 To: Amos Waterland [EMAIL PROTECTED] Subject: Re: SMP patch? Was: [XenPPC] Cannot boot from local disk Could you synchronize the console here, there are two ways to do this: 1) add sync_console to the cmdline _before_ -- 2) apply the follow diff Do you have output for this? I did this with 1), and this is the log. Thanks for the log, it helps. Can you please boot the same kernel (the one that hangs) with the `nosmp' option passed to Xen? It booted correctly. Here is the log with xen nosmp sync_console -- ... with the same image. Kawachiya system power -cycle -c -T blade[4] SLOF *** JS2XBlade Starting Check ROM = OK Build Date = Aug 14 2006 16:51:58 FW Version = JS2XFW6331 Press s to enter Open Firmware. Welcome to JS2x Open Firmware Copyright International Business Machines Corporation 2004 - 2006 US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Online CPUs: #0 #1 0.5 GB of RAM @ 333 MHz Switching top HT bus to 600MHz... Disk drive identifies as: FUJITSU MHT2040AS PCIe: = VPD = Machine Type: 884241X Machine Serial No. : 99FZM3D Hardware Revision : 1 Manuf. Date : 4704 Part Number : 2 : 001 Firmware Build ID : SLOF_633 vpd written The currently active flashside is: 1 (temporary) Stopping BMC watchdog... parse-load disk disk0 Trying to load: from: /ht/[EMAIL PROTECTED],1/[EMAIL PROTECTED] ... Success yaboot starting: loaded at 0020 0022733c (0/0/0111027c; sp: 0111eff0) brokenfirmware did not claim executable memory, fixed it myself Config file '/etc/yaboot.conf' read, 504 bytes Welcome to yaboot version 10.1.14-r716.SuSE booted from '/ht/[EMAIL PROTECTED],1/[EMAIL PROTECTED]' Enter help to get some basic usage information boot: xen Please wait, loading kernel... Allocated 0050 bytes for executable @ 0040 Elf32 kernel loaded... --- OF: Xen/PPC version 3.0-unstable ([EMAIL PROTECTED]) (gcc version 4.1.0 (SUSE Linux)) Sat Oct 7 00:38:48 JST 2006 boot_of_init args: 0x40 0x0 0x111027c 0x0 0x712130 boot msr: 0x10003000 boot_of_init: _start 00400100 _end 00725f50 0x0 boot_of_probemem: memory 0x[0x2000] wrapper_builtin_cmdline=xen builtin_cmdline=xen bootargs = xen nosmp sync_console -- root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr boot_of_module: Dom0 is linked in: 0x44f6bc[size 0x29954d] mod0: 177 E L F boot_of_module: dom0 mod @ 0x0044f6bc[0x6e8c09] boot_of_module: dom0 mod string: root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr find_space base=0x00725f50 eomem=0x2000 size=0x8000 align=0x1000 find_space base=0x00908000 eomem=0x2000 size=0x0003 align=0x1000 creating oftree pkg_save: saved device tree in 0x3298 bytes boot_of_devtree: devtree mod @ 0x00908000[0x938000] OF: timebase-frequency = 14318278 Hz OF: clock-frequency = 220 KHz spinning up secondary processor #1: ping = 0x: pong = 0x1 pruning `/ht/[EMAIL PROTECTED]/[EMAIL PROTECTED]' from devtree pruning `/ht/[EMAIL PROTECTED]/[EMAIL PROTECTED]' from devtree boot_of_serial: ISA base: 0xf400 boot_of_serial: ISRC=0x44, but forcing poll mode Quiescing Open Firmware ... __ ___ ___ _ _ _ \ \/ /___ _ __ |___ / / _ \_ _ _ __ ___| |_ __ _| |__ | | ___ \ // _ \ '_ \|_ \| | | |__| | | | '_ \/ __| __/ _` | '_ \| |/ _ \ / \ __/ | | | ___) | |_| |__| |_| | | | \__ \ || (_| | |_) | | __/ /_/\_\___|_| |_| |(_)___/\__,_|_| |_|___/\__\__,_|_.__/|_|\___| http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 3.0-unstable ([EMAIL PROTECTED]) (gcc version 4.1.0 (SUSE Linux)) Sat Oct 7 00:38:48 JST 2006 Latest ChangeSet: unavailable (XEN) Console output is synchronous. (XEN) Physical RAM map: (XEN) : 2000 (XEN) End of Xen Area: 41MiB (42208KiB) (XEN) End of RAM: 512MiB (524288KiB) (XEN) Xen Heap: 37MiB (38724KiB) (XEN) Dom Heap: 464MiB (475936KiB) (XEN) CPU[PIR:0 IPI:0 Logical:0] Hello World! (XEN) xen_mpic_init: start (XEN) mpic: Setting up MPIC Xen-U3-MPIC version 1.2 at f804, max 4 CPUs (XEN) mpic: ISU size: 124, shift: 7, mask: 7f (XEN) mpic: Initializing for 124 sources (XEN) mpic: Setting up HT PICs workarounds for U3/U4 (XEN) mpic: - HT:01.0 [0xb8] vendor 1022 device 7450 has 4 irqs (XEN) mpic: - HT:02.0 [0xb8] vendor 1022 device 7450 has 4 irqs (XEN) mpic: - HT:03.0 [0xf0] vendor 1022 device 7460 has 24 irqs (XEN)
[XenPPC] Spurious interrupt count
I am having some doubts about this code in external.c:
vec = xen_mpic_get_irq(regs);
if (vec != -1) {
...
spur_count = 0;
} else {
++spur_count;
if (spur_count 100)
panic(Too many (%d) spurrious interrupts in a row\n);
}
When I do this:
--- a/xen/arch/powerpc/external.c Fri Oct 06 12:15:06 2006 -0500
+++ b/xen/arch/powerpc/external.c Sat Oct 07 00:35:01 2006 -0400
@@ -84,6 +84,7 @@ void do_external(struct cpu_user_regs *r
if (vec != -1) {
DBG(EE:0x%lx isrc: %d\n, regs-msr, vec);
+BUG();
regs-entry_vector = vec;
do_IRQ(regs);
I make it all the way to here in dom0 Linux before the BUG asserts:
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
AMD8111: IDE controller at PCI slot :00:04.1
AMD8111: chipset revision 3
AMD8111: :00:04.1 (rev 03) UDMA133 controller
AMD8111: 100% native mode on irq 16
ide0: BM-DMA at 0x8020-0x8027, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0x8028-0x802f, BIOS settings: hdc:pio, hdd:pio
hda: FUJITSU MHT2040AS, ATA DISK drive
ide0 at 0x8000-0x8007,0x800a on irq 16
hda: max request size: 128KiB
(XEN) BUG at external.c:87
The code of concern seems well suited to catch a spurious interrupt
storm, since when a valid external interrupt is recieved, the counter is
reset. But given that we don't take our first external until way into
dom0's boot, we are actually asserting that 100 spurious interrupts
won't be received over a fairly long period of time.
I can't find any documents regarding expected spurious interrupt rates.
Can anyone with knowledge in this area comment about the code of concern?
___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel
