Re: SMP issue (Re: Status summary Was: [XenPPC] Cannot boot from local disk)
Amos, > I can confirm that the JS20 of Kawachiya-san does not boot current > Xen/PPC without the nosmp option. I got some time on the blade and > narrowed the point of failure down to somewhere in the synchronize_rcu > call that synchronize_net makes in dom0 Linux init. I will work on > it tomorrow during JST night. Thank you for the investigation. Since no one complains about this, the problem (XenPPC does not boot with SMP) seems to be my local problem. I am afraid that I did some trivial mistake in setting up my JS20 blade. Kiyokuni Kawachiya IBM Tokyo Research Laboratory ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
SMP issue (Re: Status summary Was: [XenPPC] Cannot boot from local disk)
Amos, I tried, but it failed on my JS20 at the same point. I attach the boot log. (The message "mpic.c" is added by me to check that the modified version is actually used.) (See attached file: bootlog3.txt) Kiyokuni KAWACHIYA / IBM Tokyo Research Laboratory [EMAIL PROTECTED] wrote on 2006/10/12 02:30:46: > On Sat, Oct 07, 2006 at 01:56:56AM +0900, Kiyokuni Kawachiya wrote: > > > 2. The SMP patch apparently causes dom0 Linux to fail > > > on Kawachiya's JS20, but no other JS20. > > > > > is not solved yet, may depend on my JS20. sent the boot log > > Hi Kawachiya. If you get a chance, could you please apply this patch to > the Linux tree you use for dom0 and boot without the "nosmp" option? > > diff -r b9e38b262f64 arch/powerpc/sysdev/mpic.c > --- a/arch/powerpc/sysdev/mpic.c Sun Oct 08 14:22:12 2006 -0400 > +++ b/arch/powerpc/sysdev/mpic.c Wed Oct 11 13:22:07 2006 -0400 > @@ -619,6 +619,7 @@ struct mpic * __init mpic_alloc(unsigned > mpic->tmregs = mpic->gregs + ((MPIC_TIMER_BASE - MPIC_GREG_BASE) >> 2); > BUG_ON(mpic->gregs == NULL); > > +#if 0 > /* Reset */ > if (flags & MPIC_WANTS_RESET) { >mpic_write(mpic->gregs, MPIC_GREG_GLOBAL_CONF_0, > @@ -628,6 +629,7 @@ struct mpic * __init mpic_alloc(unsigned > & MPIC_GREG_GCONF_RESET) > mb(); > } > +#endif > > /* Read feature register, calculate num CPUs and, for non-ISU > * MPICs, num sources as well. On ISU MPICs, sources are counted > bootlog3.txt Description: Binary data ___ 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= builtin_cmdline= 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
Status summary Was: [XenPPC] Cannot boot from local disk
Thank you for the quick action. Let me summarize the latest situation before I go to bed (it's 2am in Japan). > 1. In the internal Xen tree, there is a bug in which > firmware bootargs are overridden by the builtin "xen" bootarg. > was a problem in our local tree, will be fixed. > 2. The SMP patch apparently causes dom0 Linux to fail > on Kawachiya's JS20, but no other JS20. > is not solved yet, may depend on my JS20. sent the boot log > 3. In the public Xen tree, the 32-bit objcopy produces an image that > Kawachiya's yaboot apparently cannot load. > was solved by Hollis's patch to Makefile. 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
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
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 Xen<6>mpic: 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: [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: [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: 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: 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
> 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
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= builtin_cmdline= 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
> 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. Following is the boot log with old XenPPC. 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)) Mon Oct 2 10:06:25 JST 2006 boot_of_init args: 0x40 0x0 0x111027c 0x0 0x0 boot msr: 0x10003000 boot_of_init: _start 00400100 _end 00725b88 0x0 boot_of_probemem: memory 0x[0x2000] bootargs = xen -- root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr boot_of_module: Dom0 is linked in: 0x44edbc[size 0x29954d] mod0: 177 E L F boot_of_module: mod[0] @ 0x0044edbc[0x6e8309] boot_of_module: mod[0].string: root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr find_space base=0x00725b88 eomem=0x2000 size=0x0003 align=0x1000 creating oft pkg_save: saved device tree in 0x3288 bytes boot_of_module: mod[1] @ 0x0090[0x93] 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 OF: timebase-frequency = 14318278 Hz OF: clock-frequency = 220 KHz : zImage starting: loaded at 0x0040 (sp: 0x0190) Allocating 0x7348b8 bytes for kernel ... OF version = 'IBM,XenOF0.1' gunzipping (0x140 <- 0x407000:0x688751)...done 0x6a8578 bytes OF stdout device is: /xen/console command line: root=/dev/hda3 sysrq=1 insmod=sym53c8xx insmod=ipr memory layout at init: alloc_bottom : 01b39000 alloc_top: 0400 alloc_top_hi : 0c00 rmo_top : 0400 ram_top : 0c00 : And, this is the log with new XenPPC. 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)) Fri Oct 6 19:49:34 JST 2006 boot_of_init args: 0x40 0x0 0x111027c 0x0 0x712120 boot msr: 0x10003000 boot_of_init: _start 00400100 _end 00725f48 0x0 boot_of_probemem: memory 0x[0x2000] bootargs = xen boot_of_module: Dom0 is linked in: 0x44f6bc[size 0x29954d] mod0: 177 E L F boot_of_module: dom0 mod @ 0x0044f6bc[0x6e8c09] find_space base=0x00725f48 eomem=0x2000 size=0x8000 align=0x1000 find_space base=0x00908000 eomem=0x2000 size=0x0003 align=0x1000 creating oftree pkg_save: saved device tree in 0x3288 bytes boot_of_devtree: devtree mod @ 0x00908000[0x938000] OF: timebase-frequency = 14318278 Hz OF: clock-frequency = 220 KHz : zImage starting: loaded at 0x0040 (sp: 0x0190) Allocating 0x7348b8 bytes for kernel ... OF version = 'IBM,XenOF0.1' gunzipping (0x140 <- 0x407000:0x688751)...done 0x6a8578 bytes OF stdout device is: /xen/console command line: memory layout at init: alloc_bottom : 01b39000 alloc_top: 0400 alloc_top_hi : 0c00 rmo_top : 0400 ram_top : 0c00 : You can see that "bootargs" and "command line" lines are differnt. 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
> 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 Xen<6>mpic: 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 Root-NFS: No NFS server available, giving up. VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "" 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) <0>Rebooting 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
[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] [PATCH] fix allocation bug in xen console
Hi Hollis, I reported the bug to Maria and she kindly posted the patch here. [EMAIL PROTECTED] wrote on 2006/09/09 00:30:18: > > summary: fixes allocation error for xen console area > > > > details: previous code worked correctly only if the > > allocated structure fitted in same page as the base address. > > If the allocated structure did not fit, the > > computation for the allocation was incorrect. > > By the way, how did this bug manifest itself, > i.e. what were the symptoms? In my case, the domU system hanged when we use many printf's. I found that a specific memory area was broken after a specific printf, and narrowed down where it was broken. Kiyokuni Kawachiya ___ Xen-ppc-devel mailing list Xen-ppc-devel@lists.xensource.com http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] 128 meg domU???
(Just for logging the forgotten part here) xen_init_early() in hard-codes the address of xen_start_info as 64MB-16KB, so this should also be modified for 128MB. From chat with Orran, he already modified it, but 128MB domU still didn't work. Kiyokuni KAWACHIYA, Ph.D. / IBM Tokyo Research Laboratory Orran Y Krieger <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 2006/09/01 15:02 To xen-ppc-devel@lists.xensource.com cc Subject [XenPPC] 128 meg domU??? Been trying to increase the memory used for our library OS to 128Meg, In ppc970.c switched the rma size to 128 meg: unsigned int cpu_default_rma_order_pages(void) { - return rma_orders[0].order - PAGE_SHIFT; + return rma_orders[1].order - PAGE_SHIFT; } Also, modified the configuraiton # Initial memory allocation (in megabytes) for the new domain. memory = 128 I got a series of hypervisor calls, but console output no longer worked. My assumption was that start_info was moved, but as far as I can tell the memory location is hardcoded in the domain builder. Got from amos a linux, and modified its configuraiton the same way. It hit a bug in Xen: (XEN) BUG at mm.c:383 I also changed xen to have an rma of 64Meg (i.e., undid the change above) and changed just the configuraiton file, and got the same BUG at mm.c:383 is there anything else needed to support 128 meg domu?___ 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