[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] Daily Xen Builds
On Wed, 2005-05-25 at 09:14 -0700, Nakajima, Jun wrote: > David F Barrera wrote: > > May 24 22:14, 2005 Xen Unstable (xen-unstable-src.tgz) > > * x86 > > * SLES 9/SP1, RHEL 4 and FC3 on IBM xSeries 305, 235, > > HS20 and ThinkCentre > > * Builds and boots without problems > > * Able to create functional domains > > * x86_64 > > * SLES 9/SP1 HS20 Blades Type 8843 (EMT64) > > * Still broken- x86_64 build break in function > > 'prefetchw' > > * Bugzilla #34 > > * FC4 - HS20 Blade Type 8843 (EMT64) > > * Xen built without error; however, > > * Dom0 fails to boot. Bugzilla #26 ([Bug 26] > > Dom0 fails to boot on x86_64) open for this > > issue. * ------- Additional Comment #5 From > > Arun Sharma 2005-05-21 04:57 ------- > > I just posted a patch to xen-devel. It > > doesn't fix all the problems, but brings it > > one step closer. > > > > We still need: > > > > - Jun's patch to arch/xen/x86_64/mm/init.c > > - Fix xen to create the L4, L3 entries > > correctly for the readonly MPT > It will be more useful if you provide Latest ChangeSet info there. The > above two are already in this week. Our expectation is that dom0 on > x86-64 does not fail to boot. It does on my machine, which is an EMT64 based IBM HS20 Blade. Here's the log: \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| | \ // _ \ '_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ | / \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ | /_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_| http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 3.0-devel (root@xxxxxxxxxxxxxxxxxx) (gcc version 4.0.0 20050405 (Red Hat 4.0.0-0.40)) Thu May 26 08:30:02 CDT 2005 Latest ChangeSet: information unavailable (XEN) Physical RAM map: (XEN) 0000000000000000 - 000000000009d400 (usable) (XEN) 000000000009d400 - 00000000000a0000 (reserved) (XEN) 00000000000e0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 000000003ffbe680 (usable) (XEN) 000000003ffbe680 - 000000003ffd0000 (ACPI data) (XEN) 000000003ffd0000 - 0000000040000000 (reserved) (XEN) 00000000fec00000 - 0000000100000000 (reserved) (XEN) System RAM: 1023MB (1047916kB) (XEN) Xen he\uffff%\uffff\uffff% 5\uffff\uffff\u1659\uffff\uffff\uffff\uffff (XEN) ACPI: MADT (v001 IBM SERBLADE 0x00001000 IBM 0x45444f43) @ 0x000000003ffcfe00 (XEN) ACPI: MCFG (v001 IBM SERBLADE 0x00001000 IBM 0x45444f43) @ 0x000000003ffcfdc0 (XEN) ACPI: DSDT (v001 IBM SERBLADE 0x00001000 INTL 0x02002025) @ 0x0000000000000000 (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) (XEN) Processor #0 15:4 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x06] enabled) (XEN) ProcessIC (id[0x0b] address[0xfec81400] gsi_base[72]) (XEN) IOAPIC[3]: apic_id 11, version 32, address 0xfec81400, GSI 72-95 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ11 used by override. (XEN) Enabling APIC mode: Flat. Using 4 I/O APICs (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Initializing CPU#0 AUXEN) CPU2: Before vendor init, caps: bfebfbff 20000800 00000000, vendor = 0 (XEN) CPU#2: Physical ID: 3, Logical ID: 0 (XEN) CPU caps: bfebfbff 20000800 00000000 00000000 (XEN) CPU2: booted. (XEN) Booting processor 3/7 eip 90000 (XEN) Initializing CPU#3 (XEN) CPU3: Before vendor init, caps: bfebfbff 20000800 00000000, vendor = 0 (XEN) CPU#3: Physical ID: 3, Logical ID: 1 (XEN) CPU caps: bfebfbff 20000800 00000000 00000000 (XEN) CPU3: booted. (XEN) Total of 4 processo(XEN) Time init: (XEN) .... cpu_freq: 00000000:D697CA6C (XEN) .... scale: 00000001:1C6C46DD (XEN) .... Wall Clock: 1117105520s 180000us (XEN) CPU: 1 (XEN) EIP: e010:[<ffff8300001072c7>] (XEN) EFLAGS: 0000000000010086 (XEN) rax: 00000000042c3184 rbx: 0000000000000000 rcx: 0000000000001204 rdx: 0000000000000008 (XEN) rsi: 0000000000000046 rdi: 0000000000000000 rbp: f000b171f000e2c3 rsp: ffff83000018fea0 (XEN) r8: 000000000000000a r9: 0000000000000002 (XEN) r12: 00000000042cf4d4 r13: ffff83000015a380 r14: 0000000000000080 r15: ffff83000015a300 (XEN) Xen stack trace from rsp=ffff83000018fea0: (XEN) 000000000000000a ffff830000163480 0000000000000001 ffff830000164400 ffff830000179a60 0000000000000000 0000000000000000 [ffff830000111ac6] (XEN) 0000000000000080 ffff83000018ff28 ffff830000153580 [ffff830000119272] 0000000000000000 00000000a5a5a5a5 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000\uffff\uffff00119272>] (XEN) ************************************ (XEN) CPU1 FATAL TRAP 12 (stack error), ERROR_CODE 0000, IN INTERRUPT CONTEXT. (XEN) System shutting down -- need manual reset. (XEN) ************************************ > The latest one: Latest ChangeSet: > 2005/05/25 14:43:27 1.1552 429480ffbijN4G0QJScaV1h7mcJ23Q boots fine as > far as we tested. > > Jun > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@xxxxxxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |