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

[Xen-bugs] [Bug 146] New: PAE getting (XEN) BUG at domain_build.c:327

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 146] New: PAE getting (XEN) BUG at domain_build.c:327
From: pl@xxxxxxxxxx
Date: Fri, 05 Aug 2005 22:05:38 +0000
Delivery-date: Fri, 05 Aug 2005 22:05:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=146

           Summary: PAE getting (XEN) BUG at domain_build.c:327
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: pl@xxxxxxxxxx


System is a 4-way PIII, 4GB ram.
Here is a diff from the default xen0-32bit config:

-CONFIG_HIGHMEM4G=y
-# CONFIG_HIGHMEM64G is not set
+# CONFIG_HIGHMEM4G is not set
+CONFIG_HIGHMEM64G=y
+CONFIG_X86_PAE=y

# hg tip
changeset:   6027:69b7c9c3a9fd
tag:         tip
user:        kaf24@xxxxxxxxxxxxxxxxxxxx
date:        Fri Aug  5 10:11:46 2005
summary:     Fix mach2phys table allocation for 32-bit PAE Xen.

On boot I'm getting this:
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: c0100000->c06025e4
(XEN)  Init. ramdisk: c0603000->c0603000
(XEN)  Phys-Mach map: c0603000->c0643000
(XEN)  Page tables:   c0643000->c064c000
(XEN)  Start info:    c064c000->c064d000
(XEN)  Boot stack:    c064d000->c064e000
(XEN)  TOTAL:         c0000000->c0800000
(XEN)  ENTRY ADDRESS: c0100000
(XEN) BUG at domain_build.c:327
(XEN) CPU:    0
(XEN) EIP:    e008:[<ff11d8e9>] construct_dom0+0x5e9/0xec0
(XEN) EFLAGS: 00010292   CONTEXT: hypervisor
(XEN) eax: 00000000   ebx: 00000000   ecx: 00000ef3   edx: 00000001
(XEN) esi: 80000001   edi: ff1537ad   ebp: ff1b6900   esp: ff103b34
(XEN) cr0: 8005003b   cr3: 00104000
(XEN) ds: e010   es: e010   fs: e010   gs: e010   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ff103b34:
(XEN)    ff1519a0 ff1537ad 00000147 c0603000 c0603000 c0603000 c0643000 c0643000
(XEN)    c064c000 c064c000 c064d000 c064d000 c064e000 c0000000 c0800000 00000286
(XEN)    0000005f 0000000f 0000000e 00648000 00000000 00649000 c0800000 c064c000
(XEN)    c0643000 c064e000 c0603000 c0603000 00648008 00644000 00647008 00000643
(XEN)    00643000 ff1b4080 00000000 10000000 00000000 00000009 00010000 00000000
(XEN)    00c00000 004c4abc c0000000 c06025e4 c0100000 c06025e4 c0100000 00000000
(XEN)    00000000 00000000 010c4442 ff10b1d7 ff1b4080 009c6339 00000000 00000000
(XEN)    00c00000 ff0223a0 ff187a40 ff14a7e8 ff1b6900 00c00000 004c4abc 00000000
(XEN)    00000000 ff187a40 00000000 00000000 000000b4 00054184 000000d8 00054244
(XEN)    00000009 00000000 00000000 010c4abc 00c00000 000010b7 ff0223a0 00000009
(XEN)    00000000 00000008 0000006e 00000001 00000003 000002f8 00000000 00000000
(XEN)    00000000 00000000 0009dc00 00000000 00000001 0009dc00 00000000 00002400
(XEN)    00000000 00000002 000e0000 00000000 00020000 00000000 00000002 00100000
(XEN)    00000000 eb6f9380 00000000 00000001 eb7f9380 00000000 00006c80 00000000
(XEN)    00000003 fec00000 00000000 00001000 00000000 00000002 fee00000 00000000
(XEN)    00001000 00000000 00000002 fff80000 00000000 00080000 00000000 00000002
(XEN)    00000000 00000001 20000000 00000000 00000001 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
(XEN) Xen call trace from esp=ff103b34:
(XEN)    [<ff10b1d7>] do_createdomain+0xb7/0x150
(XEN) [<ff14a7e8>] __start_xen+0x4c8/0x760
(XEN)

****************************************
Panic on CPU0:
CPU0 FATAL TRAP: vector = 6 (invalid operand)
[error_code=0000]
****************************************

The "BUG at domain_build.c:327" references this section of code in 
construct_dom0():
    325         page = &frame_table[mfn];
    326         if ( !get_page_and_type(page, d, PGT_writable_page) )
    327             BUG();
    328
    329         mfn++;



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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 146] New: PAE getting (XEN) BUG at domain_build.c:327, pl <=