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

[Xen-devel] minor copy&paste error in vmx.c ?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] minor copy&paste error in vmx.c ?
From: Stefan Kaltenbrunner <stefan@xxxxxxxxxxxxxxxx>
Date: Sun, 06 Aug 2006 14:33:59 +0200
Delivery-date: Sun, 06 Aug 2006 05:34:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
User-agent: Thunderbird 1.5.0.4 (X11/20060713)
While trying to find out why OpenBSD/AMD64 still does not want to boot
on -unstable I got a rather strange (immpossible) error telling me that
CR is 0 in vmx.c:1822 which made no sense since there is a case 0 in the
switch statement.
Is it possible that there is a small c&p error and the printk() there
should actually look like:

--- a/xen/arch/x86/hvm/vmx/vmx.c        Fri Aug 04 20:34:44 2006 +0100
+++ b/xen/arch/x86/hvm/vmx/vmx.c        Sun Aug 06 11:17:04 2006 +0200
@@ -1818,7 +1818,7 @@ static int mov_to_cr(int gp, int cr, str
         break;
     }
     default:
-        printk("invalid cr: %d\n", gp);
+        printk("invalid cr: %d\n", cr);
         __hvm_bug(regs);
     }

?

with that change in place i get the following when trying to boot a
OpenBSD/AMD64 kernel:

(XEN) (GUEST: 1) Booting from CD-Rom...
(XEN) invalid cr: 8
(XEN) __hvm_bug at vmx.c:1822
(XEN) ----[ Xen-3.0-unstable    Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    0008:[<ffffffff8024b222>]
(XEN) RFLAGS: 0000000000000246   CONTEXT: hvm
(XEN) rax: 0000000000000000   rbx: ffffffff8055ada0   rcx: 0000000000000007
(XEN) rdx: 0000000000000007   rsi: 0000000000000002   rdi: ffff8000006c5f80
(XEN) rbp: ffffffff809d0ef0   rsp: ffffffff809d0ef0   r8:  0000000000000000
(XEN) r9:  ffffffff8099fbe0   r10: ffffffff8099fbe0   r11: ffffffff8099fd80
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000000
(XEN) r15: 0000000000000000   cr0: 000000008005003b   cr3: 000000009c439000
(XEN) ds: 0010   es: 0010   fs: 0000   gs: 0000   ss: 0010   cs: 0008
(XEN) domain_crash_sync called from vmx.c:1822
(XEN) Domain 1 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.0-unstable    Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    0008:[<ffffffff8024b222>]
(XEN) RFLAGS: 0000000000000246   CONTEXT: hvm
(XEN) rax: 0000000000000000   rbx: ffffffff8055ada0   rcx: 0000000000000007
(XEN) rdx: 0000000000000007   rsi: 0000000000000002   rdi: ffff8000006c5f80
(XEN) rbp: ffffffff809d0ef0   rsp: ffffffff809d0ef0   r8:  0000000000000000
(XEN) r9:  ffffffff8099fbe0   r10: ffffffff8099fbe0   r11: ffffffff8099fd80
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000000
(XEN) r15: 0000000000000000   cr0: 000000008005003b   cr3: 000000009c439000
(XEN) ds: 0010   es: 0010   fs: 0000   gs: 0000   ss: 0010   cs: 0008

any ideas ?


Stefan

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

<Prev in Thread] Current Thread [Next in Thread>