[Xen-bugs] [Bug 1529] New: Latest 64-bit Pv_ops dom0 fails to boot up with call-trace

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1529

           Summary: Latest 64-bit Pv_ops dom0 fails to boot up with call-
                    trace
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: P1
         Component: Linux-pv_ops dom0
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: jiajun.xu@xxxxxxxxx


Environment:
------------
Service Arch (ia32/ia32e/IA64): ia32e
Guest Arch (ia32/ia32e/IA64): 
Guest OS Type (Linux/Windows):
Change Set: 
Hardware: 
Other:
pv-ops dom0 commit: 3dd81018a392941fcc722ee521de344527481eb8

Bug detailed description:
--------------------------
With latest pv-ops dom0, 3dd81018a392941fcc722ee521de344527481eb8, dom0 will
call trace when booting up. 
Serial output:

#######
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
[    0.860962] init[1]: segfault at ffffffff8104f1e8 ip ffffffff8104f1e8 sp
00007fff5b08a578 error 14
[    0.862448] init[1]: segfault at ffffffff8104f1e8 ip 00000000005b7828 sp
00007fff5b089cb0 error 4 in nash[400000+239000]
[    0.862695] Kernel panic - not syncing: Attempted to kill init!
[    0.862702] Pid: 1, comm: init Not tainted 2.6.31.4 #1
[    0.862708] Call Trace:
[    0.862721]  [<ffffffff8106a6b9>] panic+0xa0/0x15f
[    0.862730]  [<ffffffff8109d3f1>] ? atomic_add_unless+0x29/0x42
[    0.862739]  [<ffffffff810901bd>] ? raw_local_irq_disable+0x19/0x1b
[    0.862748]  [<ffffffff8152d02e>] ? _write_lock_irq+0xd/0x21
[    0.862756]  [<ffffffff8107327b>] ? raw_local_irq_enable+0x19/0x1b
[    0.862763]  [<ffffffff81073b65>] ? exit_ptrace+0xa0/0x110
[    0.862770]  [<ffffffff810901bd>] ? raw_local_irq_disable+0x19/0x1b
[    0.862777]  [<ffffffff8106d4d1>] do_exit+0x79/0x629
[    0.862784]  [<ffffffff8106db22>] sys_exit_group+0x0/0x16
[    0.862791]  [<ffffffff81077a74>] get_signal_to_deliver+0x312/0x335
[    0.862800]  [<ffffffff8103215f>] do_notify_resume+0x8b/0x717
[    0.862807]  [<ffffffff810e2d64>] ? print_vma_addr+0xf8/0x101
[    0.862815]  [<ffffffff8104f1e8>] ? scale_delta+0x0/0x26
[    0.862823]  [<ffffffff811fa288>] ? __up_read+0x84/0x8c
[    0.862830]  [<ffffffff8104f1e8>] ? scale_delta+0x0/0x26
[    0.862837]  [<ffffffff81052c44>] ? bad_area_nosemaphore+0xe/0x10
[    0.862844]  [<ffffffff8152f258>] ? do_page_fault+0x14c/0x271
[    0.862852]  [<ffffffff8103375c>] retint_signal+0x48/0x8c
[    0.862858]  [<ffffffff8104f1e8>] ? scale_delta+0x0/0x26
#######

There is no such issue with commit 34ffcd2bde0018cf78d5b4f1f5427c38a3e9b502.

The culprit xen changeset and pvops commit is as following:

changeset:   20339:ad2fd7b94bd3
user:        Keir Fraser <keir.fraser@xxxxxxxxxx>
date:        Mon Oct 19 11:58:36 2009 +0100
files:       xen/arch/x86/domain.c xen/arch/x86/time.c
xen/include/asm-x86/domain.h xen/include/asm-x86/time.h xen/include/pu
blic/vcpu.h
description:
Allow guests to register secondary vcpu_time_info

Allow a guest to register a second location for the VCPU time info
structure for each vcpu.  This is intended to allow the guest kernel
to map this information into a usermode accessible page, so that
usermode can efficiently calculate system time from the TSC without
having to make a syscall.

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>
Signed-off-by: Keir Fraser <keir.fraser@xxxxxxxxxx>


commit c6b4fcace9a2bd98a761f7e8e67c7719bcbc6718
Author: Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>
Date:   Mon Oct 5 12:22:59 2009 -0700

    xen/time: add pvclock_clocksource_vread support

    Add support to register pvclock_vcpu_time_info structures in the userspace
    mapped page and set the xen clocksource .vread method if that works.
    The common pvclock code does everything else.

    Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>


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