[Xen-bugs] [Bug 26] Dom0 fails to boot on x86_64

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=26





------- Additional Comments From dbarrera@xxxxxxxxxx  2005-05-10 13:49 -------
Note from "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>:

This is a side-effect of having full ACPI/PCI support in dom0 (enabled
on x86 first), and Arun and I are working on 2). 

Jun
-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of David F
Barrera
Sent: Friday, May 06, 2005 2:58 PM
To: xen-devel
Subject: Re: [Xen-devel] x86-64 xen broken with May4th xen-unstable
build

Jerone,

I am seeing the same thing you reported on an HS20 (EMT64).

David

On Wed, 2005-05-04 at 17:29 -0500, Jerone Young wrote:
> There are two things that happened in the May 4th build.
> 
> 1) x86-64 xen Linux is looking for arch/xen/x86_64/pci/direct.c (a
> symlink to arc/xen/pci/i386/pci/direct.c) and can't find it.
>       This can easily be resolved by commenting out "c-xen-obj-
> $(CONFIG_PCI_DIRECT)+= direct.o" in arch/xen/pci/Makefile. This was
> removed from i386 and no one told x86-64 about it ...that's why he
> always misses the party :-)
> 
> 
> 2) When booting dom0, I can nolonger bootup and the domain crashes not
> far in the bootup:
> (XEN) *** LOADING DOMAIN 0 ***
> (XEN) Xen-ELF header found:
> 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xf'(XEN) PHYSICAL
> MEMORY ARRANGEMENT:
> (XEN)  Dom0 alloc.:   0000000010000000->0000000020000000 (62464 pages
to
> be allocat)(XEN) VIRTUAL MEMORY ARRANGEMENT:
> (XEN)  Loaded kernel: ffffffff80100000->ffffffff80519086
> (XEN)  Init. ramdisk: ffffffff8051a000->ffffffff8051a000
> (XEN)  Phys-Mach map: ffffffff8051a000->ffffffff80597000
> (XEN)  Page tables:   ffffffff80597000->ffffffff8059e000
> (XEN)  Start info:    ffffffff8059e000->ffffffff8059f000
> (XEN)  Boot stack:    ffffffff8059f000->ffffffff805a0000
> (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).
>  Xen: 0000000000000000 - 000000001f400000 (usable)
> kernel direct mapping tables upto ffff88001f400000 @ 59e000-69a000
> Linux version 2.6.11-xen0 (root@xen64) (gcc version 3.4.3 20050227
(Red
> Hat 3.4.3-25Registering memory for bootmem: from  800000, size =
> 1ec00000
> Built 1 zonelists
> Kernel command line: ro root=/dev/sda1
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 65536 bytes)
> Xen reported: 2193.760 MHz processor.
> Using tsc for high-res timesource
> Console: colour VGA+ 80x25
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Memory: 495616k/512000k available (2474k kernel code, 7872k reserved,
> 880k data, 40)(XEN) BUG at domain.c:136
> (XEN) CPU:    0
> (XEN) EIP:    0810:[<ffff830000107369>]
> (XEN) EFLAGS: 0000000000010282
> (XEN) rax: 0000000000000000   rbx: ffff830000ffbb00   rcx:
> 00000000000003f8   rdx: 6(XEN) rsi: 000000000000000a   rdi:
> ffff830000158474   rbp: ffff830000ff4080   rsp: 0(XEN) r8:
> 0000000000000036   r9:  0000000000001687   r10: 0000000000000001
r11:
> 5(XEN) r12: ffff830000155ea0   r13: ffff830000155e80   r14:
> 0000000000000000   r15: 0(XEN) Stack trace from RSP=ffff830000105f00:
> (XEN)     0000000000000810 ffff830000ff4080 ffff830000ff4080
> [ffff830000107459] [ff
> (XEN)     ffffffff80100038 ffffffff803d1c80 00000000ffff8b19
> 0000000000000000 ffff8
> (XEN)     000000007fb67903 0000000000000002 0000000000000355
> 0000000000010000 00000
> (XEN)     ffffffff804b3f80 000000000000082b 000000000000082b
> 0000000000000000 00000
> (XEN) Call Trace from RSP=ffff830000105f00:
> (XEN)    [<ffff830000107459>] [<ffff830000133f86>]
[<ffff830000133ea3>]
> 
> ****************************************
> CPU0 FATAL TRAP: vector = 6 (invalid operand)
> [error_code=0000]
> Aieee! CPU0 is toast...
> ****************************************
> 
> Reboot in five seconds...
>       



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs