thr3ads.net - Xen devel - [Xen-devel] BUG: xen-unstable boot stuck after mtrr [Mar 2005]

If this information is useful, please help other people find it:
Share via:

Rik van Riel

2005-Mar-17 21:55 UTC

[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''m digging through the code to try and figure out what
function is called next, but mtrr_init (which displays
this message) doesn''t seem to be called from anywhere.

Arch/x86/smpboot.c, OTOH, has calls to mtrr_init_boot_cpu()
and mtrr_init_secondary_cpu(), which aren''t defined anywhere
and under CONFIG_MTRR, which in turn doesn''t seem to be
defined ;)

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan


-------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Rik van Riel

2005-Mar-17 22:15 UTC

head link

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

On Thu, 17 Mar 2005, Rik van Riel wrote:
> I''m digging through the code to try and figure out what
> function is called next, but mtrr_init (which displays
> this message) doesn''t seem to be called from anywhere.
Found it.  Not the most debuggable wrt calling order though.
Now to find out what function it calls after mtrr_init() ...

static void __init do_initcalls(void)
{
    initcall_t *call;
    for ( call = &__initcall_start; call < &__initcall_end; call++ )
        (*call)();
}


-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan


-------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Rik van Riel

2005-Mar-17 22:28 UTC

head link

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

On Thu, 17 Mar 2005, Rik van Riel wrote:> On Thu, 17 Mar 2005, Rik van Riel wrote:
> 
> > I''m digging through the code to try and figure out what
> > function is called next, but mtrr_init (which displays
> > this message) doesn''t seem to be called from anywhere.
> 
> Found it.  Not the most debuggable wrt calling order though.
> Now to find out what function it calls after mtrr_init() ...
That was the last one in row.  Xen fails to initialise the
secondary CPU, or in my case the secondary thread on my
hyperthreaded CPU.

Booting with ''nosmp'' results in a working system.

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan


-------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Adam Heath

2005-Mar-17 22:41 UTC

head link

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

On Thu, 17 Mar 2005, Rik van Riel wrote:
> Found it.  Not the most debuggable wrt calling order though.
> Now to find out what function it calls after mtrr_init() ...
>
> static void __init do_initcalls(void)
> {
>     initcall_t *call;
>     for ( call = &__initcall_start; call < &__initcall_end;
call++ )
>         (*call)();
> }
The linker script does all this magic; the order of modules is dependant on
the linker being used.


-------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Chris Wedgwood

2005-Mar-18 00:17 UTC

head link

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

On Thu, Mar 17, 2005 at 05:15:05PM -0500, Rik van Riel wrote:
> Found it.  Not the most debuggable wrt calling order though.  Now to
> find out what function it calls after mtrr_init() ...
i''ve had funnies here before too
> static void __init do_initcalls(void)
> {
>     initcall_t *call;
>     for ( call = &__initcall_start; call < &__initcall_end;
call++ )
+ {
+ printk("about call %p\n", ...);
>         (*call)();
sorta thing is what i resorted to



-------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Ian Pratt

2005-Mar-18 00:27 UTC

head link

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

Works for me on an SMP Pentium 4 Xeon with HT -- see attached boot log.

Ian
> -----Original Message-----
> From: xen-devel-admin@lists.sourceforge.net 
> [mailto:xen-devel-admin@lists.sourceforge.net] On Behalf Of 
> Rik van Riel
> Sent: 17 March 2005 21:55
> To: xen-devel@lists.sourceforge.net
> 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''m digging through the code to try and figure out what
> function is called next, but mtrr_init (which displays
> this message) doesn''t seem to be called from anywhere.
> 
> Arch/x86/smpboot.c, OTOH, has calls to mtrr_init_boot_cpu()
> and mtrr_init_secondary_cpu(), which aren''t defined anywhere
> and under CONFIG_MTRR, which in turn doesn''t seem to be
> defined ;)

Starting new kernel       
 __  __            _____  ___         _                _ 
 \ \/ /___ _ __   |___ / / _ \     __| | _____   _____| |
  \  // _ \ ''_ \    |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
  /  \  __/ | | |  ___) | |_| |__| (_| |  __/\ V /  __/ |
 /_/\_\___|_| |_| |____(_)___/    \__,_|\___| \_/ \___|_|
                                                         
 http://www.cl.cam.ac.uk/netos/xen
 University of Cambridge Computer Laboratory

 Xen version 3.0-devel (iap10@cl.cam.ac.uk) (gcc version 3.3.3 20040412
(Red Hat Linux 3.3.3-7)) Thu Mar 17 23:07:54 GMT 2005
 Latest ChangeSet: 2005/03/17 19:50:54 1.1347
4239df9exBuYyfIcI7IkAhaxoiouoA

(XEN) Physical RAM map:
(XEN)  0000000000000000 - 00000000000a0000 (usable)
(XEN)  0000000000100000 - 000000007fff0000 (usable)
(XEN)  000000007fff0000 - 000000007ffff000 (reserved)
(XEN)  00000000fec00000 - 00000000fec10000 (reserved)
(XEN)  00000000fee00000 - 00000000fee10000 (reserved)
(XEN)  00000000fff80000 - 0000000100000000 (reserved)
(XEN) System RAM: 2047MB (2096704kB)
(XEN) Xen heap: 10MB (10684kB)
(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 000fe710
(XEN) ACPI: RSDP (v000 DELL                                      ) @
0x000fdc60
(XEN) ACPI: RSDT (v001 DELL   PE2650   0x00000001 MSFT 0x0100000a) @
0x000fdc74
(XEN) ACPI: FADT (v001 DELL   PE2650   0x00000001 MSFT 0x0100000a) @
0x000fdca4
(XEN) ACPI: MADT (v001 DELL   PE2650   0x00000001 MSFT 0x0100000a) @
0x000fdd18
(XEN) ACPI: SPCR (v001 DELL   PE2650   0x00000001 MSFT 0x0100000a) @
0x000fdda0
(XEN) ACPI: DSDT (v001 DELL   PE2650   0x00000001 MSFT 0x0100000a) @
0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 Pentium 4(tm) XEON(tm) APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
(XEN) Processor #2 Pentium 4(tm) XEON(tm) APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
(XEN) Processor #1 Pentium 4(tm) XEON(tm) APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
(XEN) Processor #3 Pentium 4(tm) XEON(tm) 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 0121      APIC at: 0xFEE00000
(XEN) I/O APIC #4 Version 17 at 0xFEC00000.
(XEN) I/O APIC #5 Version 17 at 0xFEC01000.
(XEN) I/O APIC #6 Version 17 at 0xFEC02000.
(XEN) Enabling APIC mode: Flat. Using 3 I/O APICs
(XEN) Processors: 4
(XEN) Using scheduler: Borrowed Virtual Time (bvt)
(XEN) Initializing CPU#0
(XEN) Detected 2389.259 MHz processor.
(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) CPU0 booted
(XEN) enabled ExtINT on CPU#0
(XEN) ESR value before enabling vector: 00000040
(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 00000000 00000000, vendor
= 0
(XEN) CPU#1: Physical ID: 0, Logical ID: 1
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) CPU1 has booted.
(XEN) Booting processor 2/2 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 00000000 00000000, vendor
= 0
(XEN) CPU#2: Physical ID: 3, Logical ID: 0
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) CPU2 has booted.
(XEN) Booting processor 3/3 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 00000000 00000000, vendor
= 0
(XEN) CPU#3: Physical ID: 3, Logical ID: 1
(XEN) CPU caps: bfebfbff 00000000 00000000 00000000
(XEN) CPU3 has booted.
(XEN) Total of 4 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) Setting 4 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 4 ... ok.
(XEN) Setting 5 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 5 ... ok.
(XEN) Setting 6 in the phys_id_present_map
(XEN) ...changing IO-APIC physical APIC ID to 6 ... ok.
(XEN) init IO_APIC IRQs
(XEN) vector_irq[49] = 1
(XEN) vector_irq[51] = 3
(XEN) vector_irq[59] = 4
(XEN) vector_irq[61] = 6
(XEN) vector_irq[69] = 8
(XEN) vector_irq[71] = 9
(XEN) vector_irq[79] = 12
(XEN) vector_irq[81] = 14
(XEN) vector_irq[89] = 15
(XEN) vector_irq[91] = 16
(XEN) vector_irq[99] = 17
(XEN) vector_irq[a1] = 18
(XEN) vector_irq[a9] = 19
(XEN) vector_irq[b1] = 20
(XEN) vector_irq[b9] = 21
(XEN) vector_irq[c1] = 22
(XEN) vector_irq[c9] = 23
(XEN) vector_irq[d1] = 24
(XEN) vector_irq[d9] = 25
(XEN) vector_irq[e1] = 26
(XEN) vector_irq[e9] = 27
(XEN) vector_irq[42] = 28
(XEN) vector_irq[4a] = 29
(XEN) vector_irq[52] = 30
(XEN) vector_irq[5a] = 31
(XEN) ..TIMER: vector=0x41 pin1=2 pin2=0
(XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
(XEN) ...trying to set up timer (IRQ0) through the 8259A ... 
(XEN) ..... (found pin 0) ...works.
(XEN) Using local APIC timer interrupts.
(XEN) Calibrating APIC timer for CPU0...
(XEN) ..... CPU speed is 2389.1777 MHz.
(XEN) ..... Bus speed is 99.5489 MHz.
(XEN) ..... bus_scale = 0x000065F0
(XEN) checking TSC synchronization across CPUs: passed.
(XEN) Time init:
(XEN) .... System Time: 12961896ns
(XEN) .... cpu_freq:    00000000:8E6935F0
(XEN) .... scale:       00000001:AC95AA08
(XEN) .... Wall Clock:  1111102599s 150000us
(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 0xfc97e, last bus=5
(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:0f.1
(XEN) PCI: Discovered primary peer bus 01 [IRQ]
(XEN) PCI: Discovered primary peer bus 02 [IRQ]
(XEN) PCI: Discovered primary peer bus 03 [IRQ]
(XEN) PCI: Discovered primary peer bus 04 [IRQ]
(XEN) PCI: Using IRQ router ServerWorks [1166/0201] at 00:0f.0
(XEN) PCI->APIC IRQ transform: (B0,I4,P0) -> 19
(XEN) PCI->APIC IRQ transform: (B0,I4,P1) -> 23
(XEN) PCI->APIC IRQ transform: (B0,I4,P2) -> 27
(XEN) PCI->APIC IRQ transform: (B3,I6,P0) -> 28
(XEN) PCI->APIC IRQ transform: (B3,I8,P0) -> 29
(XEN) PCI->APIC IRQ transform: (B4,I8,P0) -> 30
(XEN) PCI->APIC IRQ transform: (B5,I6,P0) -> 30
(XEN) PCI->APIC IRQ transform: (B5,I6,P1) -> 31
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found:
''GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,LOADER=ge
neric,PT_MODE_WRITABLE''
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0100000->c0543ac4
(XEN)  Init. ramdisk: c0544000->c0544000
(XEN)  Phys-Mach map: c0544000->c0583000
(XEN)  Page tables:   c0583000->c0586000
(XEN)  Start info:    c0586000->c0587000
(XEN)  Boot stack:    c0587000->c0588000
(XEN)  TOTAL:         c0000000->c0800000
(XEN)  ENTRY ADDRESS: c0100000
(XEN) Scrubbing Free RAM: .....................done.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch
input to Xen).
Linux version 2.6.11-xen0 (iap10@freefall.cl.cam.ac.uk) (gcc version
3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 Thu Mar 17 23:14:33 GMT 2005
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 000000000fc00000 (usable)
252MB LOWMEM available.
DMI 2.3 present.
IRQ lockup detection disabled
Allocating PCI resources starting at 0fc00000 (gap: 0fc00000:f0400000)
Built 1 zonelists
Kernel command line:
ip=128.232.38.50:128.232.32.20:128.232.32.1:255.255.240.0:commando-0.xen
o.cl.cam.ac.uk:eth0:off root=/dev/sda8 ro console=ttyS0 nosegfixup
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 16384 bytes)
Xen reported: 2389.259 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 250752k/258048k available (2868k kernel code, 7128k reserved,
937k data, 320k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode...
Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Intel(R) Xeon(TM) CPU 2.40GHz stepping 07
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking ''hlt'' instruction... disabled
NET: Registered protocol family 16
PCI: Using configuration type Xen
xen_mem: Initialising balloon driver.
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:0f.1
PCI: Probing PCI hardware (bus 03)
PCI: Probing PCI hardware (bus 04)
PCI: Probing PCI hardware (bus 05)
PCI: Probing PCI hardware
IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com>
Initializing Cryptographic API
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Floppy drive(s): fd0 is 1.44M
floppy0: no floppy controllers found
RAMDISK driver initialized: 16 RAM disks of 4096K 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)
PCI: Obtained IRQ 28 for device 0000:03:06.0
eth0: Tigon3 [partno(BCM95701A10) rev 0105 PHY(5701)]
(PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:06:5b:f6:90:b3
eth0: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1]
TSOcap[0] 
PCI: Obtained IRQ 29 for device 0000:03:08.0
eth1: Tigon3 [partno(BCM95701A10) rev 0105 PHY(5701)]
(PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:06:5b:f6:90:b4
eth1: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1]
TSOcap[0] 
Xen virtual console successfully installed as ttyS
Event-channel device installed.
Initialising Xen netif backend
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
SvrWks CSB5: IDE controller at PCI slot 0000:00:0f.1
SvrWks CSB5: chipset revision 147
SvrWks CSB5: not 100% native mode: will probe irqs later
SvrWks CSB5: simplex device: DMA forced
    ide0: BM-DMA at 0x08b0-0x08b7, BIOS settings: hda:DMA, hdb:pio
SvrWks CSB5: simplex device: DMA forced
    ide1: BM-DMA at 0x08b8-0x08bf, BIOS settings: hdc:DMA, hdd:DMA
hda: SAMSUNG CD-ROM SN-124, ATAPI CD/DVD-ROM drive
hda: Disabling (U)DMA for SAMSUNG CD-ROM SN-124 (blacklisted)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: ATAPI 24X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.20
Red Hat/Adaptec aacraid driver (1.1.2-lk2 Mar 17 2005)
PCI: Obtained IRQ 30 for device 0000:04:08.1
AAC0: kernel 2.7.4 build 3170
AAC0: monitor 2.7.4 build 3170
AAC0: bios 2.7.0 build 3170
AAC0: serial e65010d3fafaf001
scsi0 : percraid
  Vendor: DELL      Model: xeno-root-16      Rev: V1.0
  Type:   Direct-Access                      ANSI SCSI revision: 02
3ware Storage Controller device driver for Linux v1.26.02.000.
SCSI device sda: 286716544 512-byte hdwr sectors (146799 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write through
SCSI device sda: 286716544 512-byte hdwr sectors (146799 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write through
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 sda10 >
Attached scsi removable disk sda at scsi0, channel 0, id 1, lun 0
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard on isa0060/serio0
input: PS/2 Generic Mouse on isa0060/serio1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: automatically using best checksumming function: pIII_sse
   pIII_sse  :  1244.000 MB/sec
raid5: using function: pIII_sse (1244.000 MB/sec)
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
Bridge firewalling registered
IP-Config: Complete:
      device=eth0, addr=128.232.38.50, mask=255.255.240.0,
gw=128.232.32.1,
     host=commando-0, domain=, nis-domain=xeno.cl.cam.ac.uk,
     bootserver=128.232.32.20, rootserver=128.232.32.20, rootpathmd:
Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
EXT3-fs: recovery complete.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 320k freed
modprobe: FATAL: Could not load /lib/modules/2.6.11-xen0/modules.dep: No
such file or directory

INIT: version 2.85 booting
tg3: eth0: Link is up at 1000 Mbps, full duplex.
tg3: eth0: Flow control is off for TX and off for RX.
                Welcome to Fedora Core
                Press ''I'' to enter interactive startup.
Configuring kernel parameters:  [  OK  ]
modprobe: FATAL: Could not load /lib/modules/2.6.11-xen0/modules.dep: No
such file or directory

Setting clock  (utc): Thu Mar 17 23:37:00 GMT 2005 [  OK  ]
Setting hostname commando:  [  OK  ]
Your system appears to have shut down uncleanly
Press Y within 1 seconds to force file system integrity check...
Checking root filesystem
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda8 
/dev/sda8: clean, 110092/1052480 files, 440758/2104507 blocks (check in
5 mounts)
[  OK  ]
Remounting root filesystem in read-write mode:  [  OK  ]
Setting up Logical Volume Management: [  OK  ]
Activating swap partitions:  [  OK  ]
Checking filesystems
Checking all file systems.
[  OK  ]
Mounting local filesystems:  [  OK  ]
Enabling local filesystem quotas:  [  OK  ]
Enabling swap space:  [  OK  ]
INIT: Entering runlevel: 3
Entering non-interactive startup
Applying Intel IA32 Microcode update: (XEN) microcode: No suitable data
for CPU3
(XEN) microcode: No suitable data for CPU1
(XEN) microcode: No suitable data for CPU2
(XEN) microcode: No suitable data for CPU0
[  OK  ]
Checking for new hardware [  OK  ]
Updating /etc/fstab [  OK  ]
Setting network parameters:  [  OK  ]
Bringing up loopback interface:  [  OK  ]
Starting system logger: [  OK  ]
Starting kernel logger: [  OK  ]
Starting irqbalance: [  OK  ]
Starting portmapper: [  OK  ]
Starting NFS statd: [  OK  ]
Starting NFS4 idmapd: Error: RPC MTAB does not exist.
Initializing random number generator:  [  OK  ]
Starting pcmcia:  [  OK  ]
Mounting NFS filesystems:  mount to NFS server ''labyrinth''
failed:
server is down.
[FAILED]
Mounting other filesystems:  [  OK  ]
Starting automount: No Mountpoints Defined[  OK  ]
Starting smartd: [FAILED]
Starting sshd:[  OK  ]
Starting xinetd: [  OK  ]
Starting sendmail: [  OK  ]
Starting sm-client: [  OK  ]
Starting console mouse services: [  OK  ]
Starting crond: [  OK  ]
Starting anacron: [  OK  ]
Starting atd: [FAILED]
Starting mdmpd: Kernel md module does not support events
[FAILED]

Fedora Core release 2 (Tettnang)
Kernel 2.6.11-xen0 on an i686

commando login: root
Password: 
You have new mail.
[root@commando root]# xend start
[root@commando root]# xm info
system                 : Linux
host                   : commando
release                : 2.6.11-xen0
version                : #1 Thu Mar 17 23:14:33 GMT 2005
machine                : i686
cores                  : 2
hyperthreads_per_core  : 2
cpu_mhz                : 2389
memory                 : 2047
free_memory            : 1772


-------------------------------------------------------
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_ide95&alloc_id396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Wim Coekaerts

2005-Mar-19 02:03 UTC

head link

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

I got same as Rik on an ibm x440 6cpu HT
Wim

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.
> 
> Ian
> 
> > -----Original Message-----
> > From: xen-devel-admin@lists.sourceforge.net 
> > [mailto:xen-devel-admin@lists.sourceforge.net] On Behalf Of 
> > Rik van Riel
> > Sent: 17 March 2005 21:55
> > To: xen-devel@lists.sourceforge.net
> > 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)

-------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Ian Pratt

2005-Mar-19 22:22 UTC

head link

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

> I got same as Rik on an ibm x440 6cpu HT
> Wim
Are you using gcc-3.4.0 like Rik?

Ian
> 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.
> > 
> > Ian
> > 
> > > -----Original Message-----
> > > From: xen-devel-admin@lists.sourceforge.net 
> > > [mailto:xen-devel-admin@lists.sourceforge.net] On Behalf Of 
> > > Rik van Riel
> > > Sent: 17 March 2005 21:55
> > > To: xen-devel@lists.sourceforge.net
> > > 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)
> 

-------------------------------------------------------
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_ide95&alloc_id396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Wim Coekaerts

2005-Mar-19 22:32 UTC

head link

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

his rpms :)

On Sat, Mar 19, 2005 at 10:22:28PM -0000, Ian Pratt
wrote:>   
> > I got same as Rik on an ibm x440 6cpu HT
> > Wim
> 
> Are you using gcc-3.4.0 like Rik?
> 
> Ian
> 
> > 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.
> > > 
> > > Ian
> > > 
> > > > -----Original Message-----
> > > > From: xen-devel-admin@lists.sourceforge.net 
> > > > [mailto:xen-devel-admin@lists.sourceforge.net] On Behalf Of 
> > > > Rik van Riel
> > > > Sent: 17 March 2005 21:55
> > > > To: xen-devel@lists.sourceforge.net
> > > > 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)
> > 


-------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Rik van Riel

2005-Mar-20 03:00 UTC

head link

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

On Sat, 19 Mar 2005, Ian Pratt wrote:
> > I got same as Rik on an ibm x440 6cpu HT
> > Wim
> 
> Are you using gcc-3.4.0 like Rik?
gcc-3.4 is kind-of ok.  The real problems happen with gcc-4.0

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan


-------------------------------------------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Matt Cowan

2005-Mar-25 19:11 UTC

head link

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

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@li...] 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@build.redhat.com) (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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel

Xen devel - Mar 2005 - BUG: xen-unstable boot stuck after mtrr

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

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

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

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

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

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

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

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

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

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

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