May 25 22:10, 2005 Xen Unstable (xen-unstable-src.tgz) * x86 SLES 9/SP1, RHEL 4 and FC3 on IBM xSeries 305, 235, HS20 (x86) and ThinkCentre * Builds and boots without problems * Able to create functional domains * x86_64 * BUILD BREAK on SLES 9/SP1 HS20 Blades Type 8843 (EMT64) * x86_64 build break in function ''prefetchw'' * Bugzilla #34 * Dom0 DOES NOT BOOT on FC4 - HS20 Blade Type 8843 (EMT64) * Xen built without errors; however, * Dom0 fails to boot. Bugzilla #26 ([Bug 26] Dom0 fails to boot on x86_64) open for this issue. * Note: May be a different error today, but my serial over lan capability on the HS20(EMT64) blade is down at the moment. -- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
In today''s build (2005/05/26) on HS20 x86 SMP, I got a CPU FATAL TRAP 13 error when booting xen. Xen source: May 26 unstable tree ( http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/xen-unstable-src.tgz ). Hardware: HS20 blade (x86) OS: Fedora Core 3 I verified that I used the right level of Xen (xen-3.0-devel.gz) and Xen Linux (vmlinuz-2.6.11.10-xen0) and initrd (initrd-2.6.11.10-xen0.img). Here is the boot message: __ __ _____ ___ _ _ \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| | \ // _ \ ''_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ | / \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ | /_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_| http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 3.0-devel (root@ltc.austin.ibm.com) (gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) Thu May 26 09:24:25 CDT 2005 Latest ChangeSet: information unavailable (XEN) Physical RAM map: (XEN) 0000000000000000 - 000000000009e000 (usable) (XEN) 000000000009e000 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000003ffed040 (usable) (XEN) 000000003ffed040 - 000000003fff0000 (ACPI data) (XEN) 000000003fff0000 - 0000000040000000 (reserved) (XEN) 00000000fec00000 - 0000000100000000 (reserved) (XEN) System RAM: 1023MB (1048108kB) (XEN) Xen heap: 10MB (10768kB) (XEN) CPU0: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0 (XEN) CPU#0: Physical ID: 0, Logical ID: 0 (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 (XEN) found SMP MP-table at 0009e140 (XEN) DMI 2.3 present. (XEN) Using APIC driver default (XEN) ACPI: RSDP (v000 IBM ) @ 0x000fdfc0 (XEN) ACPI: RSDT (v001 IBM SERBLADE 0x00001000 IBM 0x45444f43) @ 0x3ffeff80 (XEN) ACPI: FADT (v001 IBM SERBLADE 0x00001000 IBM 0x45444f43) @ 0x3ffeff00 (XEN) ACPI: MADT (v001 IBM SERBLADE 0x00001000 IBM 0x45444f43) @ 0x3ffefe40 (XEN) ACPI: DSDT (v001 IBM SERBLADE 0x00001000 INTL 0x02002025) @ 0x00000000 (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) Processor #0 15:2 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled) (XEN) Processor #6 15:2 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) (XEN) Processor #1 15:2 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled) (XEN) Processor #7 15:2 APIC version 20 (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) (XEN) ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1]) (XEN) ACPI: IOAPIC (id[0x0e] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 14, version 17, address 0xfec00000, GSI 0-15 (XEN) ACPI: IOAPIC (id[0x0d] address[0xfec01000] gsi_base[16]) (XEN) IOAPIC[1]: apic_id 13, version 17, address 0xfec01000, GSI 16-31 (XEN) ACPI: IOAPIC (id[0x0c] address[0xfec02000] gsi_base[32]) (XEN) IOAPIC[2]: apic_id 12, version 17, address 0xfec02000, GSI 32-47 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) Enabling APIC mode: Flat. Using 3 I/O APICs (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Initializing CPU#0 (XEN) Detected 3065.856 MHz processor. (XEN) Using scheduler: Borrowed Virtual Time (bvt) (XEN) CPU0: booted. (XEN) Booting processor 1/1 eip 90000 (XEN) Initializing CPU#1 (XEN) CPU1: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0 (XEN) CPU#1: Physical ID: 0, Logical ID: 1 (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 (XEN) CPU1: booted. (XEN) Booting processor 2/6 eip 90000 (XEN) Initializing CPU#2 (XEN) CPU2: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0 (XEN) CPU#2: Physical ID: 3, Logical ID: 0 (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 (XEN) CPU2: booted. (XEN) Booting processor 3/7 eip 90000 (XEN) Initializing CPU#3 (XEN) CPU3: Before vendor init, caps: bfebfbff 00000000 00000000, vendor = 0 (XEN) CPU#3: Physical ID: 3, Logical ID: 1 (XEN) CPU caps: bfebfbff 00000000 00000000 00000000 (XEN) CPU3: booted. (XEN) Total of 4 processors activated.(XEN) ENABLING IO-APIC IRQs (XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1 (XEN) checking TSC synchronization across 4 CPUs: passed. (XEN) Time init: (XEN) .... cpu_freq: 00000000:B6BD4050 (XEN) .... scale: 00000001:4E0056FC (XEN) .... Wall Clock: 1117100289s 180000us (XEN) CPU: 1 (XEN) EIP: e008:[<ff105085>] (XEN) EFLAGS: 00210092 CONTEXT: hypervisor (XEN) eax: ffffffff ebx: fffff801 ecx: fffffe00 edx: f000b1fb (XEN) esi: fffff800 edi: 00000016 ebp: 00000000 esp: ffbf9ef8 (XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ffbf9ef8: (XEN) f000b1fa f000b1fb 000007b2 00000000 f000b1fa f000b1fb 00000b2c 0000b1fa (XEN) fffffc00 ffffffff 00200092 00000000 f000b1fb 042cef63 00000000 [ff105589] (XEN) 00000000 00200097 00000000 [ff119716] 00000080 00000080 00000001 00000080 (XEN) CPU: 3 (XEN) EIP: e008:[<ff105085>] (XEN) EFLAGS: 00210096 CONTEXT: hypervisor (XEN) eax: ffffffff ebx: fffff801 ecx: fffffe00 edx: f000b1fb (XEN) esi: fffff800 edi: 00000016 ebp: 00000000 esp: ffbf3ef8 (XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 cs: e008 (XEN) CPU: 2 (XEN) EIP: e008:[<ff105085>] (XEN) EFLAGS: 00210092 CONTEXT: hypervisor (XEN) eax: ffffffff ebx: fffff801 ecx: fffffe00 edx: f000b1fb (XEN) esi: fffff800 edi: 00000016 ebp: 00000000 esp: ffbf5ef8 (XEN) ds: e010 es: e010 fs: e010 gs: e010 ss: e010 cs: e008 (XEN) Xen stack trace from esp=ffbf3ef8: (XEN) f000b1f8 f000b1fb 000007b2 00000000 f000b1f8 f000b1fb 0074f4a2 0000b1f8 (XEN) fffffc00 ffffffff 00200092 00000000 f000b1fb 055e0ea3 00000000 [ff105589] (XEN) 00000000 00200097 00000000 [ff119716] 00000180 00000180 00000003 00000180 (XEN) 00000180 00000180 00000000 [ff110a02] 00ef0000 [ff117146] ffbf3fb4 [ff117185] (XEN) 00000003 ff172840 ffbef880 [ff143dc5] 00104000 00000004 00000000 00000000 (XEN) f08007ff 0000ffbe 00000000 00000000 a5a5a5a5 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 (XEN) 00000003 ffbf6080 (XEN) Xen call trace from esp=ffbf3ef8: (XEN) Brought up 4 CPUs (XEN) [<ff105589>] [<ff119716>] [<ff110a02>] [<ff117146>] [<ff117185>] [<ff143dc5>] (XEN) ************************************ (XEN) CPU3 FATAL TRAP 13 (general protection fault), ERROR_CODE 0000, IN INTERRUPT CONTEXT. (XEN) System shutting down -- need manual reset. (XEN) ************************************ Li dfbp@us.ltcfwd.li nux.ibm.com Sent by: To xen-devel-bounces xen-devel @lists.xensource. <xen-devel@lists.xensource.com> com cc Subject 05/26/2005 10:12 [Xen-devel] Xen Daily Builds AM May 25 22:10, 2005 Xen Unstable (xen-unstable-src.tgz) * x86 SLES 9/SP1, RHEL 4 and FC3 on IBM xSeries 305, 235, HS20 (x86) and ThinkCentre * Builds and boots without problems * Able to create functional domains * x86_64 * BUILD BREAK on SLES 9/SP1 HS20 Blades Type 8843 (EMT64) * x86_64 build break in function ''prefetchw'' * Bugzilla #34 * Dom0 DOES NOT BOOT on FC4 - HS20 Blade Type 8843 (EMT64) * Xen built without errors; however, * Dom0 fails to boot. Bugzilla #26 ([Bug 26] Dom0 fails to boot on x86_64) open for this issue. * Note: May be a different error today, but my serial over lan capability on the HS20(EMT64) blade is down at the moment. -- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> In today''s build (2005/05/26) on HS20 x86 SMP, I got a CPU FATAL TRAP > 13 error when booting xen.I think this is a bug that I already fixed in the repository. Should be in tonight''s snapshot tarballs. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Thanks. I will give it a try tomorrow. Li Keir Fraser <Keir.Fraser@cl.c am.ac.uk> To Li Ge/Austin/IBM@IBMUS 05/26/2005 12:03 cc PM xen-devel <xen-devel@lists.xensource.com>, dfbp@us.ltcfwd.linux.ibm.com, xen-devel-bounces@lists.xensource.c om Subject Re: [Xen-devel] Xen Daily Builds> In today''s build (2005/05/26) on HS20 x86 SMP, I got a CPU FATAL TRAP > 13 error when booting xen.I think this is a bug that I already fixed in the repository. Should be in tonight''s snapshot tarballs. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
You are right. I just tested it with the latest repository source and the problem is gone. I can boot domain0 and create domainU without a problem. Thanks, Li Keir Fraser <Keir.Fraser@cl.c am.ac.uk> To Li Ge/Austin/IBM@IBMUS 05/26/2005 12:03 cc PM xen-devel <xen-devel@lists.xensource.com>, dfbp@us.ltcfwd.linux.ibm.com, xen-devel-bounces@lists.xensource.c om Subject Re: [Xen-devel] Xen Daily Builds> In today''s build (2005/05/26) on HS20 x86 SMP, I got a CPU FATAL TRAP > 13 error when booting xen.I think this is a bug that I already fixed in the repository. Should be in tonight''s snapshot tarballs. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I think the problem on x86-64 has the same cause. Jun --- Intel Open Source Technology Center ________________________________ From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Li Ge Sent: Thursday, May 26, 2005 12:51 PM To: Keir Fraser Cc: dfbp@us.ibm.com; xen-devel; xen-devel-bounces@lists.xensource.com Subject: Re: [Xen-devel] Xen Daily Builds You are right. I just tested it with the latest repository source and the problem is gone. I can boot domain0 and create domainU without a problem. Thanks, Li Keir Fraser <Keir.Fraser@cl.cam.ac.uk> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 05/26/2005 12:03 PM To Li Ge/Austin/IBM@IBMUS cc xen-devel <xen-devel@lists.xensource.com>, dfbp@us.ltcfwd.linux.ibm.com, xen-devel-bounces@lists.xensource.com Subject Re: [Xen-devel] Xen Daily Builds> In today''s build (2005/05/26) on HS20 x86 SMP, I got a CPU FATAL TRAP > 13 error when booting xen.I think this is a bug that I already fixed in the repository. Should be in tonight''s snapshot tarballs. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, 2005-05-26 at 13:33 -0700, Nakajima, Jun wrote:> I think the problem on x86-64 has the same cause.Unfortunately, the x86_64 build is broken, so I cannot test it.> gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing - > iwithprefix include-Wall -Werror -Wno-pointer-arith -pipe -I/tmp/xen-unstable/xen/include -I/tmp/x en-unstable/xen/include/asm-x86/mach-generic -I/tmp/xen-unstable/xen/include/asm -x86/mach-default -O3 -fomit-frame-pointer -msoft-float -m64 -mno-red-zone -fpic -fno-reorder-blocks -fno-asynchronous-unwind-tables -DNDEBUG -c cpu/common.c -o cpu/common.o cc1: warnings being treated as errors cpu/common.c: In function ‘early_cpu_detect’: cpu/common.c:209: warning: pointer targets in passing argument 2 of ‘cpuid’ diff er in signedness cpu/common.c:209: warning: pointer targets in passing argument 3 of ‘cpuid’ diff er in signedness cpu/common.c:209: warning: pointer targets in passing argument 4 of ‘cpuid’ diff er in signedness cpu/common.c:209: warning: pointer targets in passing argument 5 of ‘cpuid’ diff er in signedness cpu/common.c: In function ‘generic_identify’: cpu/common.c:241: warning: pointer targets in passing argument 2 of ‘cpuid’ diff er in signedness cpu/common.c:241: warning: pointer targets in passing argument 3 of ‘cpuid’ diff er in signedness cpu/common.c:241: warning: pointer targets in passing argument 4 of ‘cpuid’ diff er in signedness cpu/common.c:241: warning: pointer targets in passing argument 5 of ‘cpuid’ diff er in signedness cpu/common.c:250: warning: pointer targets in passing argument 3 of ‘cpuid’ diff er in signedness make[3]: *** [cpu/common.o] Error 1 make[3]: Leaving directory `/tmp/xen-unstable/xen/arch/x86'' make[2]: *** [/tmp/xen-unstable/xen/xen] Error 2 make[2]: Leaving directory `/tmp/xen-unstable/xen'' make[1]: *** [xen] Error 2 make[1]: Leaving directory `/tmp/xen-unstable'' make: *** [world] Error 2> Jun > --- > Intel Open Source Technology Center > > > > > ______________________________________________________________________ > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > bounces@lists.xensource.com] On Behalf Of Li Ge > Sent: Thursday, May 26, 2005 12:51 PM > To: Keir Fraser > Cc: dfbp@us.ibm.com; xen-devel; xen-devel-bounces@lists.xensource.com > Subject: Re: [Xen-devel] Xen Daily Builds > > > > You are right. I just tested it with the latest repository source and > the problem is gone. I can boot domain0 and create domainU without a > problem. > > Thanks, > Li > Inactive hide details for Keir Fraser <Keir.Fraser@cl.cam.ac.uk>Keir > Fraser <Keir.Fraser@cl.cam.ac.uk> > > > Keir Fraser <Keir.Fraser@cl.cam.ac.uk> > > 05/26/2005 12:03 PM > > > To > > Li > Ge/Austin/IBM@IBMUS > > cc > > xen-devel <xen- > devel@lists.xensource.com>, dfbp@us.ltcfwd.linux.ibm.com, xen-devel-bounces@lists.xensource.com > > Subject > > Re: [Xen-devel] > Xen Daily Builds > > > > > > > In today''s build (2005/05/26) on HS20 x86 SMP, I got a CPU FATAL > TRAP > > 13 error when booting xen. > > I think this is a bug that I already fixed in the repository. Should > be > in tonight''s snapshot tarballs. > > -- Keir > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
I don''t have the problem. I guess that''s a gcc4-related issue or fixed now? Jun --- Intel Open Source Technology Center -----Original Message----- From: David F Barrera [mailto:dfbp@us.ibm.com] Sent: Friday, May 27, 2005 8:38 AM To: Nakajima, Jun Cc: Li Ge; Keir Fraser; xen-devel Subject: RE: [Xen-devel] Xen Daily Builds On Thu, 2005-05-26 at 13:33 -0700, Nakajima, Jun wrote:> I think the problem on x86-64 has the same cause.Unfortunately, the x86_64 build is broken, so I cannot test it.> gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing - > iwithprefix include-Wall -Werror -Wno-pointer-arith -pipe -I/tmp/xen-unstable/xen/include -I/tmp/x en-unstable/xen/include/asm-x86/mach-generic -I/tmp/xen-unstable/xen/include/asm -x86/mach-default -O3 -fomit-frame-pointer -msoft-float -m64 -mno-red-zone -fpic -fno-reorder-blocks -fno-asynchronous-unwind-tables -DNDEBUG -c cpu/common.c -o cpu/common.o cc1: warnings being treated as errors cpu/common.c: In function ''early_cpu_detect'': cpu/common.c:209: warning: pointer targets in passing argument 2 of ''cpuid'' diff er in signedness cpu/common.c:209: warning: pointer targets in passing argument 3 of ''cpuid'' diff er in signedness cpu/common.c:209: warning: pointer targets in passing argument 4 of ''cpuid'' diff er in signedness cpu/common.c:209: warning: pointer targets in passing argument 5 of ''cpuid'' diff er in signedness cpu/common.c: In function ''generic_identify'': cpu/common.c:241: warning: pointer targets in passing argument 2 of ''cpuid'' diff er in signedness cpu/common.c:241: warning: pointer targets in passing argument 3 of ''cpuid'' diff er in signedness cpu/common.c:241: warning: pointer targets in passing argument 4 of ''cpuid'' diff er in signedness cpu/common.c:241: warning: pointer targets in passing argument 5 of ''cpuid'' diff er in signedness cpu/common.c:250: warning: pointer targets in passing argument 3 of ''cpuid'' diff er in signedness make[3]: *** [cpu/common.o] Error 1 make[3]: Leaving directory `/tmp/xen-unstable/xen/arch/x86'' make[2]: *** [/tmp/xen-unstable/xen/xen] Error 2 make[2]: Leaving directory `/tmp/xen-unstable/xen'' make[1]: *** [xen] Error 2 make[1]: Leaving directory `/tmp/xen-unstable'' make: *** [world] Error 2> Jun > --- > Intel Open Source Technology Center > > > > > ______________________________________________________________________ > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > bounces@lists.xensource.com] On Behalf Of Li Ge > Sent: Thursday, May 26, 2005 12:51 PM > To: Keir Fraser > Cc: dfbp@us.ibm.com; xen-devel; xen-devel-bounces@lists.xensource.com > Subject: Re: [Xen-devel] Xen Daily Builds > > > > You are right. I just tested it with the latest repository source and > the problem is gone. I can boot domain0 and create domainU without a > problem. > > Thanks, > Li > Inactive hide details for Keir Fraser <Keir.Fraser@cl.cam.ac.uk>Keir > Fraser <Keir.Fraser@cl.cam.ac.uk> > > > Keir Fraser <Keir.Fraser@cl.cam.ac.uk>> > 05/26/2005 12:03 PM > > > To > > Li > Ge/Austin/IBM@IBMUS > > cc > > xen-devel <xen- > devel@lists.xensource.com>, dfbp@us.ltcfwd.linux.ibm.com,xen-devel-bounces@lists.xensource.com> > Subject > > Re: [Xen-devel] > Xen Daily Builds > > > > > > > In today''s build (2005/05/26) on HS20 x86 SMP, I got a CPU FATAL > TRAP > > 13 error when booting xen. > > I think this is a bug that I already fixed in the repository. Should > be > in tonight''s snapshot tarballs. > > -- Keir > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel