From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Scott Parish" Subject: Re: x86_64 - Dom0 will not boot on EMT64 Date: Wed, 15 Jun 2005 15:52:12 +0000 Message-ID: <20050615155208.GB2909@us.ibm.com> References: <1118852662.3974.7.camel@dyn95394152.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <1118852662.3974.7.camel@dyn95394152.austin.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: David F Barrera Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org I've been seeing the same thing on my 8843s (or was on saturday). I'm hunting another bug at the moment, and don't multitask very well; if nobody has figured this out by the time i get done with the other bug i'm planning on looking into this. sRp On Wed, Jun 15, 2005 at 11:24:22AM -0500, David F Barrera wrote: > I am unable to boot Dom0 on my IBM eServer BladeCenter HS20, type 8843, > EMT64 blades. I have read reports that Dom0 boots on Opteron boxes, but > on my EMT64 blades, it does not. Has anyone else encountered this > problem on EMT64 hardware? >=20 > Here are the errors I am getting: >=20 >=20 > This is on a SLES 9 box, gcc version 3.3.3 (SuSE Linux): >=20 > kernel (hd0,0)/boot/xen.gz dom0_mem=3D256000 com2=3D19200,8n1 console=3D= vga,com2 nor > eboot > [Multiboot-elf, <0x100000:0x5e358:0x22ca8>, shtab=3D0x181078, entry=3D= 0x100000] > module (hd0,0)/boot/vmlinuz-2.6-xen0 root=3D/dev/sda6 ro console=3Dtty0 > [Multiboot-module @ 0x182000, 0x67e5f0 bytes] > module (hd0,0)/initrd-2.6.11.12-xen0 >=20 > __ __ _____ ___ _ _ > \ \/ /___ _ __ |___ / / _ \ __| | _____ _____| | > \ // _ \ '_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ | > / \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ | > /_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_| >=20 > http://www.cl.cam.ac.uk/netos/xen > University of Cambridge Computer Laboratory >=20 > Xen version 3.0-devel (root@ltc.austin.ibm.com) (gcc version 3.3.3 (SuSE > Linux)) Wed Jun 15 08:19:06 CDT 2005 > Latest ChangeSet: information unavailable >=20 > (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 heap: 14MB (14812kB) > (XEN) found SMP MP-table at 0009d540 > (XEN) DMI 2.3 present. > (XEN) Using APIC driver default > (XEN) ACPI: RSDP (v000 IBM ) @ 0x000000= 00000fdfc0 > (XEN) ACPI: RSDT (v001 IBM SERBLADE 0x00001000 IBM 0x45444f43) @ > 0x000000003ffcff80 > (XEN) ACPI: FADT (v002 IBM SERBLADE 0x00001000 IBM 0x45444f43)P) > =20 > \uffff\uffff\u0255\uffff\uffff\u1655\uffffXEN) 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) Processor #6 15:4 APIC version 20 > (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) > (XEN) Processor #1 15:4 APIC version 20 > (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x07] enabled) > (XEN) Processor #7 15:4 APIC version 20 > (XEN) ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1]) > (XEN) ACPI: LAPIC_NMI > (acpi_id[5%\uffffe%B\uffff\u0349\uffff\uffff}\uffff\uffff\u015d\uffff\uff= ff\uffff\uffff\uffff}\uffff\uffff\u0161\uffff\uffff\uffff\uffff\uffff\u0655= \uffffXEN) > 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 > (XEN) Detected 3600.316 MHz processor. > (XEN) Using scheduler: Borrowed Virtual Time (bvt) > (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K > (XEN) CPU: L2 cache: 1024K > (XEN) CPU: Physical Processor ID: 0 > (XEN) CPUU 3.60GHz stepping 01 > (XEN) Total of 4 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) ..TIMER: vector=3D0x31 pin1=3D2 pin2=3D-1 > (XEN) checking TSC synchronization across 4 CPUs: passed. > (XEN) Time init: > (XEN) .... cpu_freq: 00000000:D6987764 > (XEN) .... scale: 00000001:1C6B619C > (XEN) .... Wall Clock: 1118847138s 160000us > (XEN) Brought up 4 CPUs > (XEN) mtrr: v2.0 (20020519) > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen-ELF header found: > 'GUEST_OS=3Dlinux,GUEST_VER=3D2.6,XEN_VER=3D3.0,VIRT_BASE=3D0xffffffff801= 00000,LOADER=3Dgeneric' > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000008000000->0000000010000000 (31232 pages to = be > allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff80100000->ffffffff80578086 > (XEN) Init. ramdisk: ffffffff80(XEN) Start info: =20 > ffffffff805bf000->ffffffff805c0000 > (XEN) Boot stack: ffffffff805c0000->ffffffff805c1000 > (XEN) TOTAL: ffffffff80000000->ffffffff80800000 > (XEN) ENTRY ADDRESS: ffffffff80100000 > (XEN) Scrubbing Free RAM: ...........done. > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input= to Xen). > Linux version 2.6.11.12-xen0 (root@bl2-1) (gcc version 3.3.3 (SuSE Linux)= ) #1 > Wed Jun 15 08:25:11 CDT 2005 > kernel direct mapping tables upto > ffff88000fa00000L&SVB\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uff= ff\uffff\uffff\uffff\uffff\uffff\uffff\uffffJr > = =20 > \u024d\uffff\u1579\uffff}\uffff\uffff\uffff\uffff\uffff\u044d\uffff\uffff= \uffff\uffff\u0455\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\u024d\uf= fff\u1579\uffff}\uffff\uffff\uffff\uffff\uffff\u044d\uffff\uffff\uffff\ufff= f\u0455\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\u024d\uffff\u1579\u= ffff}\uffff\uffff\uffff\uffff\uffff\u044d\uffff\uffff\uffff\uffff\u0455\uff= ff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\u024d\uffff\u1579\uffff}\uffff= \uffff\uffff\uffff\uffff\u044d\uffff\uffff\uffff\uffff\u0455\uffff\uffff\uf= fff\uffff\uffff\uffff\uffff\uffff\u024d\uffff\u1579\uffff}\uffff\uffff\ufff= f\uffff\uffff\u044d\uffff\uffff\uffff\uffff\u0455\uffff\uffff\uffff\uffff\u= ffff\uffff\uffff\uffff\u024d\uffff\u1579\uffff}\uffff\uffff\uffff\uffff\uff= ff\u044d\uffff\uffff\uffff\uffff\u0455\uffff\uffff\uffff\uffff\uffff\uffff\= uffff\uffff\u024d\uffff\u1579\uffff}\uffff\uffff\uffff\uffff\uffff\u044d\uf= fff\uffff\uffff\uffff\u0455\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff= \u024d\uffff\u1579\uffff}\uffff\uffff\uffff\uffff}fec10000] > gsi_base[24])\uffff\uffff\uffff\uffff\uffff\uffff\u0455\uffff\uffff\uffff= \uffff\uffff\uffff\uffff\uffff\u024d\uffff\u1579\uffff}\uffff\uffff\uffff\u= ffff\uffff\u044d\uffff\uffff\uffff\uffff\u0455\uffff\uffff\uffff\uffff\ufff= f\uffff\uffff\uffff\u024d\uffff\u1579\uffff}\uffff\uffff\uffff\uffff\uffff\= u044d\uffff\uffff\uffff\uffff\u0455\uffff\uffff\uffff\uffff\uffff\uffff\uff= ff > IOAPIC[1]: apic_id 13, version 32, address 0xfec10000, GSI 24-47 > ACPI: IOAPIC (id[0x0c] address[0xfec81000] gsi_base[48]) > IOAPIC[2]: apic_id 12, version 32, address 0xfec81000, GSI 48-71 > ACPI: IOAPIC (id[0x0b] address[0xfec81400] gsi_base[72]) > IOAPIC[3]: apic_id 11, version 32, address 0xfec81400, GSI 72-95 > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level) > Setting APIC routing to flat > %%\uffff\u0455\uffff\uffff\uffffkaround, the "pci=3Drouteirq" argument re= stores > the old > ** behavior. If this argument makes the device work again, > ** please email the output of "lspci" to bjorn.helgaas@hp.com > ** so I can fix the driver. > PCI: IRQ init > Grant table initialized > Initializing Cryptographic API > Real Time Clock Driver v1.12 > i8042.c: Can't read CTR while initializing i8042. > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered > Floppy dfloppy0: no floppy controllers found > RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize > loop: loaded (max 8 devices) > HP CISS Driver (v 2.6.4) > Intel(R) PRO/1000 Network Driver - version 5.6.10.1-k2 > Copyright (c) 1999-2004 Intel Corporation. > pcnet32.c:v1.30i 06.28.2004 tsbogend@alpha.franken.de > e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI > e100: Copyright(c) 1999-2004 Intel Corporation > tg3.c:v3.23 (February 15, 2005) > ACPI: PCI interrupt 0000:05:01.0[A] -> GSI 77 (level, low) -> IRQ 77 > Unable to handle kernel NULL pointer dereference at 0000000000000880 RIP: > {do_page_fault+370} > Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: > {dump_pagetable+47} > Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: > {dump_pagetable+47} > Unable to handle kernel NULL pointer dereferentable+47} > Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: > {dump_pagetable+47} > Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: > {dump_pagetable+47} > Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: > {dump_pagetable+47} > Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: > {dump_pagetable+47} > The errors repeat ad nauseum at this point..... > ---------------------------------------------------------------------- >=20 >=20 > And this one from a GCC 4.0 Xen build (FC4)--the offset is different >=20 > tg3.c:v3.23 (February 15, 2005) > ACPI: PCI interrupt 0000:05:01.0[A] -> GSI 77 (level, low) -> IRQ 77 > Unable to handle kernel NULL pointer dereference at 0000000000000880 RIP: > {do_page_fault+432} > Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: > {dump_pagetable+51} > Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: > {dump_pagetable+51} > Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: > {dump_pagetable+51} > Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: > {dump_pagetable+51} > Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: > {dump_pagetable+51} > Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: > The errors repeat ad nauseum at this point..... > ---------------------------------------------------------------------- >=20 >=20 > --=20 > Regards, >=20 > David F Barrera > Linux Technology Center > Systems and Technology Group, IBM >=20 > "The wisest men follow their own direction. " > Euripides >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >=20 --=20 Scott Parish Signed-off-by: srparish@us.ibm.com