WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: BUG: xen-unstable boot stuck after mtrr

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: BUG: xen-unstable boot stuck after mtrr
From: Matt Cowan <cowan@xxxxxxx>
Date: Fri, 25 Mar 2005 14:11:23 -0500 (EST)
Delivery-date: Fri, 25 Mar 2005 19:13:39 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
On 2005-03-18 at 21:06 Wim, Coekaerts wrote:
I got same as Rik on an ibm x440 6cpu HT
...
On Fri, Mar 18, 2005 at 12:27:00AM -0000, Ian Pratt wrote:
Works for me on an SMP Pentium 4 Xeon with HT -- see attached boot log.
...
-----Original Message-----
...
[mailto:xen-devel-admin@xxxxx] On Behalf Of Rik van Riel
...
Subject: [Xen-devel] BUG: xen-unstable boot stuck after mtrr

Current xen-unstable bootup on a P4 doesn"t get as far as
to start up domain 0, on my test systems.  The last line
it prints out is:

(XEN) mtrr: v2.0 (20020519)


I have had the same issue on both a dell pe2650 and pe2850 2cpu w/ ht
running the fedora devel packages
(xen-2-20050308,kernel-xen{0,U}-devel-2.6.11-1.1177_FC4); boot log
appended at end.

It comes up fine if I give xen a "nosmp" from grub
...
kernel /boot/xen.gz dom0_mem=512000 nosmp watchdog console=com1 com1=9600,8n1
...
but that sucks.


I haven't experienced any hangs or other instability so far.  I do
have a perc4 embedded raid controller, which michal urbanski thinks
he's having trouble with in his pe2850:
http://sourceforge.net/mailarchive/forum.php?thread_id=6884811&forum_id=35600
The system runs beautifully when I boot regular, non-xen fc3 aswell.

-matt


here's the grub entry used
----------------------------------------------------------------------
        root (hd0,1)
        kernel /boot/xen.gz dom0_mem=512000 watchdog com1=9600,8n1
        module /boot/vmlinuz-2.6.11-1.1177_FC4xen0 ro root=LABEL=/ console=ttyS0
        module /boot/initrd-2.6.11-1.1177_FC4xen0.img

this grub entry boots successfully, but of couse just w/ 1cpu
----------------------------------------------------------------------
        root (hd0,1)
        kernel /boot/xen.gz dom0_mem=512000 nosmp watchdog com1=9600,8n1
        module /boot/vmlinuz-2.6.11-1.1177_FC4xen0 ro root=LABEL=/ console=ttyS0
        module /boot/initrd-2.6.11-1.1177_FC4xen0.img

----------------------------------------------------------------------
here's the log where it hangs at mtrr
(note: there's some previous screen garbage interspersed at the
beginning due to the serial console setup).
----------------------------------------------------------------------
 \ \/ /___ _ __   |___ / / _ \     __| | _____   _____| |
  \  // _ \ '_ \    |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
  /  \  __/ | | |  ___) | |_| |__| (_| |  __/\ V /  __/ |
 /_/\_\___|_| |_| |____(_)___/    \__,_|\___| \_/ \___|_|

 http://www.cl.cam.ac.uk/netos/xen        e     e  !
 University of Cambridge Computer Laboratory
"stock           o      h   f    a   s  l
 Xen version 3.0-devel (bhcompile@xxxxxxxxxxxxxxxx) (gcc version 4.0.0 20050302 
(Red Hat 4.0.5 Latest ChangeSet: information unavailablenel] [F5-Rescue]
boo
(XEN) WARNING: Only the first 4GB of the physical memory map can be accessed
(XEN)          by Xen in 32-bit mode. Truncating the memory map...
(XEN) Physical RAM map:
(XEN)  0000000000000000 - 00000000000a0000 (usable)
(XEN)  0000000000100000 - 00000000cffc0000 (usable)
(XEN)  00000000cffc0000 - 00000000cffcfc00 (ACPI data)
(XEN)  00000000cffcfc00 - 00000000cffff000 (reserved)
(XEN)  00000000e0000000 - 00000000fec90000 (reserved)
(XEN)  00000000fed00000 - 00000000fed00400 (reserved)
(XEN)  00000000fee00000 - 00000000fee10000 (reserved)
(XEN)  00000000ffb00000 - 0000000100000000 (reserved)
(XEN) System RAM: 3327MB (3407232kB)
(XEN) Xen heap: 10MB (10644kB)
(XEN) CPU0: Before vendor init, caps: bfebfbff 20100000 00000000, vendor = 0
(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 20100000 00000000 00000000
(XEN) found SMP MP-table at 000fe710
(XEN) ACPI: RSDP (v000 DELL                                      ) @ 0x000fd650
(XEN) ACPI: RSDT (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000a) @ 0x000fd664
(XEN) ACPI: FADT (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000a) @ 0x000fd6b0
(XEN) ACPI: MADT (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000a) @ 0x000fd724
(XEN) ACPI: SPCR (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000a) @ 0x000fd7cc
(XEN) ACPI: HPET (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000a) @ 0x000fd81c
(XEN) ACPI: MCFG (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000a) @ 0x000fd854
(XEN) ACPI: DSDT (v001 DELL   PE BKC   0x00000001 MSFT 0x0100000e) @ 0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 Unknown CPU [15:4] APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x06] enabled)
(XEN) Processor #6 Unknown CPU [15:4] APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
(XEN) Processor #1 Unknown CPU [15:4] APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] enabled)
(XEN) Processor #7 Unknown CPU [15:4] APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
(XEN) Using ACPI for processor (LAPIC) configuration information
(XEN) Intel MultiProcessor Specification v1.4
(XEN)     Virtual Wire compatibility mode.
(XEN) OEM ID: DELL     Product ID: PE 016D      APIC at: 0xFEE00000
(XEN) I/O APIC #8 Version 32 at 0xFEC00000.
(XEN) I/O APIC #9 Version 32 at 0xFEC80000.
(XEN) I/O APIC #10 Version 32 at 0xFEC83000.
(XEN) I/O APIC #11 Version 32 at 0xFEC84000.
(XEN) Enabling APIC mode: Flat. Using 4 I/O APICs
(XEN) Processors: 4
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 3591.165 MHz processor.
(XEN) CPU0: Before vendor init, caps: bfebfbff 20100000 00000000, vendor = 0
(XEN) CPU#0: Physical ID: 0, Logical ID: 0
(XEN) CPU caps: bfebfbff 20100000 00000000 00000000
(XEN) CPU0 booted
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) masked ExtINT on CPU#1
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) CPU1: Before vendor init, caps: bfebfbff 20100000 00000000, vendor = 0
(XEN) CPU#1: Physical ID: 0, Logical ID: 1
(XEN) CPU caps: bfebfbff 20100000 00000000 00000000
(XEN) CPU1 has booted.
(XEN) Booting processor 2/6 eip 90000
(XEN) Initializing CPU#2
(XEN) masked ExtINT on CPU#2
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) CPU2: Before vendor init, caps: bfebfbff 20100000 00000000, vendor = 0
(XEN) CPU#2: Physical ID: 3, Logical ID: 0
(XEN) CPU caps: bfebfbff 20100000 00000000 00000000
(XEN) CPU2 has booted.
(XEN) Booting processor 3/7 eip 90000
(XEN) Initializing CPU#3
(XEN) masked ExtINT on CPU#3
(XEN) ESR value before enabling vector: 00000000
(XEN) ESR value after enabling vector: 00000000
(XEN) CPU3: Before vendor init, caps: bfebfbff 20100000 00000000, vendor = 0
(XEN) CPU#3: Physical ID: 3, Logical ID: 1
(XEN) CPU caps: bfebfbff 20100000 00000000 00000000
(XEN) CPU3 has booted.
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) Setting 8 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 8 ... ok.
(XEN) Setting 9 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 9 ... ok.
(XEN) Setting 10 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 10 ... ok.
(XEN) Setting 11 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 11 ... ok.
(XEN) init IO_APIC IRQs
(XEN) vector_irq[49] = 1
(XEN) vector_irq[51] = 4
(XEN) vector_irq[59] = 6
(XEN) vector_irq[61] = 8
(XEN) vector_irq[69] = 9
(XEN) vector_irq[71] = 12
(XEN) vector_irq[79] = 14
(XEN) vector_irq[81] = 15
(XEN) vector_irq[89] = 16
(XEN) vector_irq[91] = 18
(XEN) vector_irq[99] = 19
(XEN) vector_irq[a1] = 20
(XEN) vector_irq[a9] = 21
(XEN) vector_irq[b1] = 23
(XEN) vector_irq[b9] = 25
(XEN) vector_irq[c1] = 26
(XEN) vector_irq[c9] = 38
(XEN) vector_irq[d1] = 48
(XEN) vector_irq[d9] = 49
(XEN) vector_irq[e1] = 72
(XEN) vector_irq[e9] = 73
(XEN) vector_irq[42] = 74
(XEN) vector_irq[4a] = 75
(XEN) vector_irq[52] = 76
(XEN) vector_irq[5a] = 77
(XEN) vector_irq[62] = 78
(XEN) vector_irq[6a] = 79
(XEN) vector_irq[72] = 80
(XEN) vector_irq[7a] = 81
(XEN) vector_irq[8a] = 82
(XEN) vector_irq[92] = 83
(XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 3591.0153 MHz.
(XEN) ..... Bus speed is 199.5008 MHz.
(XEN) ..... bus_scale = 0x0000CC4F
(XEN) Time init:SC synchronization across CPUs: passed.
(XEN) .... System Time: 994014551ns
(XEN) .... cpu_freq:    00000000:D60CD5EC
(XEN) .... scale:       00000001:1D24EA75
(XEN) .... Wall Clock:  1111757316s 470000us
(XEN) Testing NMI watchdog --- CPU#0 okay. CPU#1 okay. CPU#2 okay. CPU#3 okay.
(XEN) PCI: PCI BIOS revision 2.10 entry at 0xfbf0e, last bus=11
(XEN) PCI: Using configuration type 1
(XEN) PCI: Probing PCI hardware
(XEN) PCI: Probing PCI hardware (bus 00)
(XEN) PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
(XEN) Transparent bridge - PCI device 8086:244e
(XEN) PCI: Using IRQ router PIIX/ICH [8086/24d0] at 00:1f.0
(XEN) PCI->APIC IRQ transform: (B0,I2,P0) -> 16
(XEN) PCI->APIC IRQ transform: (B0,I4,P0) -> 16
(XEN) PCI->APIC IRQ transform: (B0,I5,P0) -> 16
(XEN) PCI->APIC IRQ transform: (B0,I6,P0) -> 16
(XEN) PCI->APIC IRQ transform: (B0,I29,P0) -> 16
(XEN) PCI->APIC IRQ transform: (B0,I29,P1) -> 19
(XEN) PCI->APIC IRQ transform: (B0,I29,P2) -> 18
(XEN) PCI->APIC IRQ transform: (B0,I29,P3) -> 23
(XEN) PCI->APIC IRQ transform: (B2,I14,P0) -> 38
(XEN) PCI->APIC IRQ transform: (B6,I7,P0) -> 48
(XEN) PCI->APIC IRQ transform: (B7,I8,P0) -> 49
(XEN) PCI->APIC IRQ transform: (B11,I13,P0) -> 18
(XEN) mtrr: v2.0 (20020519)
----------------------------------------------------------------------



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Re: BUG: xen-unstable boot stuck after mtrr, Matt Cowan <=