Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

RE: [Xen-devel] Latest bk can NOT compile on x86_64

To: "David F Barrera" <dfbp@xxxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Latest bk can NOT compile on x86_64
From: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Date: Tue, 31 May 2005 12:32:51 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 31 May 2005 19:32:14 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVmAmNljWn406OiSf+79U+JSA5RQwADR3Ug
Thread-topic: [Xen-devel] Latest bk can NOT compile on x86_64
David F Barrera wrote:
> OK. This is the first time that I've been able to build Xen on SLES 9
> x86_64. When attempting to boot, Dom0 crashes. Although there is
> already 
> a defect open (Bugzilla #26) for a failure to boot Dom0 on x86_64 on
> FC4, I am opening a new defect (Bugzilla #65) since the failures
> appear different.
> 
> (XEN) Scrubbing Free RAM: ...........done.
> (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen). (XEN) CPU:    0
> (XEN) EIP:    e030:[<0000000000000000>]
> (XEN) EFLAGS: 0000000000010282
> (XEN) rax: 00000000ffffffea   rbx: 00000000105f5000   rcx:
> 0000000000000000 
> rdx: 0000000000000000
> (XEN) rsi: 0000000000000001   rdi: ffffffff804ebf40   rbp:
> 0000000000000808 
> rsp: ffffffff804ebf08
> (XEN) r8:  0000000000000000   r9:  0000000000000000   r10:
> 0000000000007ff0 
> r11: 0000000000000282
> (XEN) r12: 0000000000000000   r13: ffffffff805f4000   r14:
> ffffffff80102000 
> r15: ffffffff804ebfb0
> (XEN) Xen stack trace from rsp=ffffffff804ebf08:
> (XEN)    ffffffff80118d9d 0000000000000202 ffffffff80118da1
> 000000000001e030 0000000000010282 ffffffff804ebf40 000000000000e02b
> 00000000105f5808 (XEN)    0000000010101065 0000000000000000
> ffffffff80115d08 0000000000000000 0000000000000000 ffffffff804d8080
> ffffffff80 on CPU0: 
> Domain 0 crashed!
> ****************************************
> 

This is different from the other ones, but we need more hints as I don't
see this problem on our machines. For example, can you show the
instructions around 0xffffffff80118d9d? Please do like
1. objdump -d vmlinux > out (in linux-2.6.11-xen0)
2. search ffffffff80118d9d in 'out'
3. cut and send the disassembled instructions around ffffffff80118d9d.

Jun
---
Intel Open Source Technology Center

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