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

RE: [Xen-devel] booting on a Compaq Proliant 1600

To: "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] booting on a Compaq Proliant 1600
From: "James Harper" <JamesH@xxxxxxxxxxxxxxxx>
Date: Sat, 12 Jun 2004 14:04:50 +1000
Cc: <xen-devel@xxxxxxxxxxxxxxxxxxxxx>, <Ian.Pratt@xxxxxxxxxxxx>
Delivery-date: Sat, 12 Jun 2004 05:07:12 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
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
Thread-index: AcRP/T9WJI+Cj18+Qo2INlHPfjTg7QAM6jjk
Thread-topic: [Xen-devel] booting on a Compaq Proliant 1600
I am starting Xen with the following GRUB configuration:

title Xen
kernel /xen.gz dom0_mem=131072 ser_baud=115200 ignorebiostables ifname=dummy
module /xenolinux.gz root=/dev/discs/disc0/part6 ro console=tty0

If there is a crash message then it's too quick for me to see, I will try and 
attempt a serial capture of the boot process tonight.

Here's the dmesg output of a UP kernel. I will also load a SMP kernel tonight 
and send you that.

thanks for the speedy response.

James

Linux version 2.4.26-1-686 (herbert@gondolin) (gcc version 3.3.3 (Debian 
20040401)) #1 Sat May 1 18:04:05 EST 2004
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
 BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001c000000 (usable)
 BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
448MB LOWMEM available.
On node 0 totalpages: 114688
zone(0): 4096 pages.
zone(1): 110592 pages.
zone(2): 0 pages.
DMI not present.
ACPI: Unable to locate RSDP
Kernel command line: root=/dev/discs/disc0/part6 ro devfs=mount 
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Initializing CPU#0
Detected 349.188 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 696.32 BogoMIPS
Memory: 446504k/458752k available (1220k kernel code, 11860k reserved, 459k 
data, 112k init, 0k highmem)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU:     After generic, caps: 0183fbff 00000000 00000000 00000000
CPU:             Common caps: 0183fbff 00000000 00000000 00000000
CPU: Intel Pentium II (Deschutes) stepping 02
Enabling fast FPU save and restore... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 349.1846 MHz.
..... host bus clock speed is 99.7667 MHz.
cpu: 0, clocks: 997667, slice: 498833
CPU0<T0:997664,T1:498816,D:15,S:498833,C:997667>
mtrr: v1.40 (20010327) Richard Gooch (rgooch@xxxxxxxxxxxxx)
mtrr: detected mtrr type: Intel
ACPI: Subsystem revision 20040326
ACPI: Interpreter disabled.
PCI: PCI BIOS revision 2.10 entry at 0xf0080, last bus=2
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: ACPI tables contain no PCI IRQ routing entries
PCI: Probing PCI hardware (bus 00)
PCI: Device 00:00 not found by BIOS
PCI: Device 00:a0 not found by BIOS
PCI: Device 00:a1 not found by BIOS
PCI: Device 00:a2 not found by BIOS
PCI: Device 00:a3 not found by BIOS
Limiting direct PCI/PCI transfers.
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Disk quotas vdquot_6.5.1
devfs: v1.12c (20020818) Richard Gooch (rgooch@xxxxxxxxxxxxx)
devfs: boot_options: 0x1
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT 
SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
COMX: driver version 0.85 (C) 1995-1999 ITConsult-Pro Co. <info@xxxxxx>
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 4368 blocks [1 disk] into ram disk... done.
Freeing initrd memory: 4368k freed
VFS: Mounted root (cramfs filesystem).
Mounted devfs on /dev
Mounted devfs on /dev
Freeing unused kernel memory: 112k freed
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Compaq SMART2 Driver (v 2.4.28)
cpqarray: Device 0xae10 has been found at bus 2 dev 0 func 0
cpqarray: Finding drives on ida0 (SMART-2SL)
cpqarray ida/c0d0: blksz=512 nr_blks=53309280
blk: queue c02edac0, I/O limit 4095Mb (mask 0xffffffff)
Partition check:
 ida/c0d0: p1 p2 p3 < p5 p6 >
Journalled Block Device driver loaded
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Adding Swap: 501816k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on ida0(72,6), internal journal
Real Time Clock Driver v1.10f
natsemi dp8381x driver, version 1.07+LK1.0.17, Sep 27, 2002
  originally by Donald Becker <becker@xxxxxxxxx>
  http://www.scyld.com/network/natsemi.html
  2.4.x kernel port by Jeff Garzik, Tjeerd Mulder
eth0: NatSemi DP8381[56] at 0xdc88b000, 00:40:f4:5f:cf:f2, IRQ 15.
eth1: NatSemi DP8381[56] at 0xdc88d000, 00:40:f4:5f:cf:95, IRQ 15.
eth2: NatSemi DP8381[56] at 0xdc88f000, 00:40:f4:5f:cf:05, IRQ 5.
Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky
GRE over IPv4 tunneling driver
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ida0(72,2), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
NET4: Ethernet Bridge 008 for NET4.0



-----Original Message-----
From: Ian Pratt [mailto:Ian.Pratt@xxxxxxxxxxxx]
Sent: Sat 12/06/2004 7:43 AM
To: James Harper
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx; Ian.Pratt@xxxxxxxxxxxx
Subject: Re: [Xen-devel] booting on a Compaq Proliant 1600
 

> I'm trying to test Xen on a Compaq Proliant 1600 (P2@350Mhz) but it just
> reboots on startup.
> 
> It appears to start Xen up okay, then I see Domain0 start to boot and
> the last thing I see before the screen goes blank is 'Calibrating Delay
> Loop...'. The fact that I see that means that it probably prints 'xxx.xx
> bogomips' and then next bit before it actually crashes.
> 
> I think the next thing it gets to is the report on available memory and
> then a report on the cpu. 

Interesting -- I haven't heard of anything like this.

How much memory does the machine have? How much memory are you
starting dom0 with (on the xen command line)? Have you tried
varying this?

Please can you post the dmesg output of an SMP linux kernel
booting on the same machine.

Do you get a crash message out or does it just reboot? Could you
hook up a serial line to the machine (and configure xen with a
serial console) to capture the xen and domain0 boot messages?

> Anything obvious anyone can suggest? Is there a list of supported
> hardware somewhere?

It doesn't sound like a driver issue, and Xen should work on
anything newer than a PPro.

Ian