Can't boot 2.0.5 binaries

Can't boot 2.0.5 binaries

[Scott Laird]

I'm setting up a new PC to run Xen, and I can't get the pre-built 2.0.5 
binaries to boot.  Xen loads fine, and the 2.6.10-xen0 kernel starts to 
load, but it locks up after 'Initializing Cryptographic API'.  I'll 
have to wire up a serial console to get a full boot log, but I won't be 
able to do that until tonight at the earliest.

The hardware is an Athlon 64 3000+ (S939) w/ 1 GB of RAM on a MSI 
RS480M2-IL motherboard.  I'm trying to load the stock 32-bit Xen and 
kernel.

Has anyone seen this before?  At the very least, could someone send me 
their dmesg output from booting the stock 2.0.5 dom0 kernel, so I can 
see which subsystems come after the crypto API?

Thanks.


Scott



-------------------------------------------------------
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

Re: Can't boot 2.0.5 binaries

[Yvette]

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

Scott,

Hopefully somebody who has dealt with this issue before will give you
some more useful info, but in the interim I put the stock 2.0.5 dom0
kernel on one of my test machines and booted it so I could get the
dmesg for you. Sorry the hardware isn't more similar.

-Yvette


On Thu, 17 Mar 2005 09:21:45 -0800, Scott Laird <scott@sigkill.org> wrote:
> I'm setting up a new PC to run Xen, and I can't get the pre-built 2.0.5
> binaries to boot.  Xen loads fine, and the 2.6.10-xen0 kernel starts to
> load, but it locks up after 'Initializing Cryptographic API'.  I'll
> have to wire up a serial console to get a full boot log, but I won't be
> able to do that until tonight at the earliest.
> 
> The hardware is an Athlon 64 3000+ (S939) w/ 1 GB of RAM on a MSI
> RS480M2-IL motherboard.  I'm trying to load the stock 32-bit Xen and
> kernel.
> 
> Has anyone seen this before?  At the very least, could someone send me
> their dmesg output from booting the stock 2.0.5 dom0 kernel, so I can
> see which subsystems come after the crypto API?
> 
> Thanks.
> 
> Scott
>

[-- Attachment #2: xen0_2.6.10_vanilla_on_ibm_t22.dmesg --]
[-- Type: application/octet-stream, Size: 6885 bytes --]

Linux version 2.6.10-xen0 (xenod@freefall.cl.cam.ac.uk) (gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 Thu Mar 10 19:33:45 GMT 2005
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000004000000 (usable)
64MB LOWMEM available.
On node 0 totalpages: 16384
  DMA zone: 16384 pages, LIFO batch:4
  Normal zone: 0 pages, LIFO batch:1
  HighMem zone: 0 pages, LIFO batch:1
DMI not present.
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line: root=/dev/hda5 ro console=tty0
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 896.115 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 60400k/65536k available (2809k kernel code, 5048k reserved, 905k data, 320k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 1789.13 BogoMIPS (lpj=8945664)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000
CPU: After vendor identify, caps:  0383f9ff 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
CPU: After all inits, caps:        0383d1f1 00000000 00000000 00000040
CPU: Intel Pentium III (Coppermine) stepping 0a
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: Probing PCI hardware (bus 01)
PCI: Probing PCI hardware
IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com>
Initializing Cryptographic API
Limiting direct PCI/PCI transfers.
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
elevator: using anticipatory as default io scheduler
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.2)
Intel(R) PRO/1000 Network Driver - version 5.5.4-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.2.3-k2-NAPI
e100: Copyright(c) 1999-2004 Intel Corporation
PCI: Obtained IRQ 11 for device 0000:00:03.0
e100: eth0: e100_probe: addr 0xe8120000, irq 11, MAC addr 00:03:47:B7:5C:4A
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
PIIX4: IDE controller at PCI slot 0000:00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x1850-0x1857, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0x1858-0x185f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: IBM-DJSA-220, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: HITACHI DVD-ROM GD-S200, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
Probing IDE interface ide2...
ide2: Wait for ready failed before probe !
Probing IDE interface ide3...
ide3: Wait for ready failed before probe !
Probing IDE interface ide4...
ide4: Wait for ready failed before probe !
Probing IDE interface ide5...
ide5: Wait for ready failed before probe !
hda: max request size: 128KiB
hda: 39070080 sectors (20003 MB) w/1874KiB Cache, CHS=41344/15/63, UDMA(33)
hda: cache flushes not supported
 hda: hda1 hda2 hda3 < hda5 hda6 hda7 > hda4
hdc: ATAPI 24X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
Red Hat/Adaptec aacraid driver (1.1.2-lk2 Mar 10 2005)
3ware Storage Controller device driver for Linux v1.26.02.000.
libata version 1.10 loaded.
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  :  1211.200 MB/sec
raid5: using function: pIII_sse (1211.200 MB/sec)
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
device-mapper: 4.3.0-ioctl (2004-09-30) initialised: dm-devel@redhat.com
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
Bridge firewalling registered
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 320k freed
Adding 559424k swap on /dev/hda2.  Priority:-1 extents:1
EXT2-fs warning: maximal mount count reached, running e2fsck is recommended
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
device eth0 entered promiscuous mode
xen-br0: port 1(eth0) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 1(eth0) entering forwarding state
device vif1.0 entered promiscuous mode
xen-br0: port 2(vif1.0) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 2(vif1.0) entering forwarding state
device vif2.0 entered promiscuous mode
xen-br0: port 3(vif2.0) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 3(vif2.0) entering forwarding state
device vif3.0 entered promiscuous mode
xen-br0: port 4(vif3.0) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 4(vif3.0) entering forwarding state
device vif4.0 entered promiscuous mode
xen-br0: port 5(vif4.0) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 5(vif4.0) entering forwarding state
device vif4.0 left promiscuous mode
xen-br0: port 5(vif4.0) entering disabled state
device vif3.0 left promiscuous mode
xen-br0: port 4(vif3.0) entering disabled state
xen-br0: port 4(vif3.0) entering disabled state
device vif4.0 entered promiscuous mode
xen-br0: port 4(vif4.0) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 4(vif4.0) entering forwarding state
device vif3.0 entered promiscuous mode
xen-br0: port 5(vif3.0) entering learning state
xen-br0: topology change detected, propagating
xen-br0: port 5(vif3.0) entering forwarding state

Re: Can't boot 2.0.5 binaries

[Scott Laird]

On Mar 17, 2005, at 11:56 AM, Yvette wrote:

> Scott,
>
> Hopefully somebody who has dealt with this issue before will give you
> some more useful info, but in the interim I put the stock 2.0.5 dom0
> kernel on one of my test machines and booted it so I could get the
> dmesg for you. Sorry the hardware isn't more similar.

Thanks, this helps.  It looks like the next few lines are "Limiting 
direct PCI/PCI transfers" and then keyboard setup.  That at least gives 
me someplace to start debugging.  Thanks.


Scott



-------------------------------------------------------
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

RE: Can't boot 2.0.5 binaries

[Ian Pratt]

 
> > Hopefully somebody who has dealt with this issue before 
> will give you
> > some more useful info, but in the interim I put the stock 2.0.5 dom0
> > kernel on one of my test machines and booted it so I could get the
> > dmesg for you. Sorry the hardware isn't more similar.
> 
> Thanks, this helps.  It looks like the next few lines are "Limiting 
> direct PCI/PCI transfers" and then keyboard setup.  That at 
> least gives 
> me someplace to start debugging.  Thanks.

One thing you might want to try is to see if there's a BIOS update for
your motherboard.

Within a couple of weeks we should have some new platform init code in
the unstable.bk tree, which I hope might fix some of the corner cases we
currently experience on some platforms.

Ian


-------------------------------------------------------
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_id\x14396&op=click

Re: Can't boot 2.0.5 binaries

[Scott Laird]

On Mar 17, 2005, at 1:17 PM, Ian Pratt wrote:
>
>>> Hopefully somebody who has dealt with this issue before
>> will give you
>>> some more useful info, but in the interim I put the stock 2.0.5 dom0
>>> kernel on one of my test machines and booted it so I could get the
>>> dmesg for you. Sorry the hardware isn't more similar.
>>
>> Thanks, this helps.  It looks like the next few lines are "Limiting
>> direct PCI/PCI transfers" and then keyboard setup.  That at
>> least gives
>> me someplace to start debugging.  Thanks.
>
> One thing you might want to try is to see if there's a BIOS update for
> your motherboard.
>
> Within a couple of weeks we should have some new platform init code in
> the unstable.bk tree, which I hope might fix some of the corner cases 
> we
> currently experience on some platforms.

Okay, I'll try looking for BIOS updates; I'm not in front of the 
machine right now, but dmidecode suggests that it's running the most 
recent release from the vendor's website.  There's some suggestion 
online that there's a newer beta release somewhere; I'll see if I can 
track that down.

Also, it appears that I'm seeing APIC problems with stand-alone Linux 
on this box--the clock is running at 2x real time.  When I get home, 
I'll try booting Xen with the APIC disabled and see if it makes any 
difference.


Scott



-------------------------------------------------------
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