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 1726] New: Dom0 crashes on Core2 when dom0_mem is no mor

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1726] New: Dom0 crashes on Core2 when dom0_mem is no more than 1972MB
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 21 Jan 2011 03:20:01 -0800
Delivery-date: Fri, 21 Jan 2011 03:20:07 -0800
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/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1726

           Summary: Dom0 crashes on Core2 when dom0_mem is no more than
                    1972MB
           Product: Xen
           Version: unstable
          Platform: Other
        OS/Version: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: shaohui.zheng@xxxxxxxxx


Environment:
------------
Service Arch (ia32/ia32e/IA64): 
Guest Arch (ia32/ia32e/IA64): 
Guest OS Type (Linux/Windows):
Change Set: 
Hardware: 
Other:


Bug detailed description:
--------------------------
Dom0 kernel bug and crash on Core2 E6750 platform when dom0_mem is set no more
than 1972MB. The platform that shows the bug is HP 7800p minitower with one
E6750 processor, 4GB memory and one 250GB SATA disk.


Reproduce steps:
----------------
1. Use Core2 processor, use xen-unstable revision 22653.
2. Boot Xen with dom0_mem less or equal to 1972MB.

Current result:
----------------
Xen failed to get l1e in ptwr_emulate. Dom0 crash.

Expected result:
----------------
Dom0 boots successfully.

Basic root-causing log:
----------------------

[    0.235838] Linux agpgart interface v0.103
[    0.235877] agpgart-intel 0000:00:00.0: Intel Q35 Chipset
[    0.237152] agpgart-intel 0000:00:00.0: detected 6140K stolen memory
(XEN) mm.c:889:d0 Error getting mfn 40900 (pfn 5555555555555555) from L1 entry
8000000040900473 for                           l1e_owner=0, pg_owner=0
(XEN) mm.c:889:d0 Error getting mfn 40900 (pfn 5555555555555555) from L1 entry
8000000040900473 for                           l1e_owner=0, pg_owner=0
(XEN) mm.c:4958:d0 ptwr_emulate: could not get_page_from_l1e()
[    0.280076] BUG: unable to handle kernel paging request at ffff88003fc56360
[    0.280092] IP: [<ffffffff810370e5>] xen_set_pte+0x3e/0x4b
[    0.280107] PGD 1002067 PUD 1006067 PMD 2e8067 PTE 801000003fc56065
[    0.280127] Oops: 0003 [#1] SMP
[    0.280138] last sysfs file:
[    0.280145] CPU 1
[    0.280153] Modules linked in:
[    0.280163] Pid: 1, comm: swapper Not tainted 2.6.32.26 #1 HP Compaq dc7800p
Convertible Minitow                          er
[    0.280171] RIP: e030:[<ffffffff810370e5>]  [<ffffffff810370e5>]
xen_set_pte+0x3e/0x4b
[    0.280183] RSP: e02b:ffff88003fc89ab0  EFLAGS: 00010246
[    0.280189] RAX: 0000000000000000 RBX: 0000000000000000 RCX:
8000000040900473
[    0.280197] RDX: 0000000000000000 RSI: 8000000040900473 RDI:
ffff88003fc56360
[    0.280204] RBP: ffff88003fc89ad0 R08: 0000000000000000 R09:
ffffffff818720d0
[    0.280211] R10: 8000000000000573 R11: 800000000000056b R12:
8000000040900473
[    0.280218] R13: ffff88003fc56360 R14: ffffc9000006c000 R15:
ffff88003fc56360
[    0.280228] FS:  0000000000000000(0000) GS:ffff88002806c000(0000)
knlGS:0000000000000000
[    0.280236] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[    0.280243] CR2: ffff88003fc56360 CR3: 0000000001001000 CR4:
0000000000002660
[    0.280250] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[    0.280258] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[    0.280265] Process swapper (pid: 1, threadinfo ffff88003fc88000, task
ffff88003fc80000)
[    0.280272] Stack:
[    0.280277]  ffffffff811e4e11 ffff88003fc80000 ffffffff817c2c80
8000000040900473
[    0.280293] <0> ffff88003fc89b30 ffffffff81038a09 ffff88003fc89b30
ffffffff8103620f
[    0.280303] <0> 800000000000056b 8000000000000573 ffffffff818720d0
ffff88003fc56360
[    0.280303] Call Trace:
[    0.280303]  [<ffffffff811e4e11>] ? rb_insert_color+0xb9/0xe3
[    0.280303]  [<ffffffff81038a09>] xen_set_pte_at+0xdb/0xea
[    0.280303]  [<ffffffff8103620f>] ? __raw_callee_save_xen


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- 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