From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Latest Pv_ops dom0 fails to boot Date: Wed, 28 Oct 2009 10:34:37 -0700 Message-ID: <4AE880AD.50304@goop.org> References: <0463F45F3606F4428ED35AC8C709F92E089B924AF0@pdsmsx502.ccr.corp.intel.com> <4AE748A0.90706@goop.org> <706158FABBBA044BAD4FE898A02E4BC201C9C3194C@pdsmsx503.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC201C9C3194C@pdsmsx503.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Zhang, Xiantao" Cc: "Xu, Jiajun" , "'xen-devel@lists.xensource.com'" , "space.time.universe@gmail.com" List-Id: xen-devel@lists.xenproject.org On 10/27/09 20:03, Zhang, Xiantao wrote: > Seems it is caused by newly-introduced hypercall(VCPUOP_register_vcpu_time_memory_area) for setting memory area for vcpu time. Try the following patch(Just disable Xen_TIM_VSYSCALL) to have a try. > Are you saying that if that hypercall hasn't been implemented it crashes? Hm, will double-check. It's certainly supposed to just fall back. J > Xiantao > diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig > index 1e306c8..20b0133 100644 > --- a/arch/x86/xen/Kconfig > +++ b/arch/x86/xen/Kconfig > @@ -15,7 +15,7 @@ config XEN > Xen hypervisor. > > config XEN_TIME_VSYSCALL > - def_bool y > + def_bool n > depends on X86_VSYSCALL && PARAVIRT_CLOCK > select PARAVIRT_CLOCK_VSYSCALL > > > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Jeremy Fitzhardinge > Sent: Wednesday, October 28, 2009 3:23 AM > To: Xu, Jiajun > Cc: 'xen-devel@lists.xensource.com' > Subject: Re: [Xen-devel] Latest Pv_ops dom0 fails to boot > > On 10/26/09 06:55, Xu, Jiajun wrote: > >> Hi, >> I found latest pv_ops dom0, commit 3dd81018a392941fcc722ee521de344527481eb8, fails to boot with call trace. And commit 34ffcd2bde0018cf78d5b4f1f5427c38a3e9b502 has no such issue. Could anyone help on this issue? >> >> > Could you post a full log? > > Thanks, > J > > >> Call trace messages: >> ####### >> 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] [] panic+0xa0/0x15f >> [ 0.862730] [] ? atomic_add_unless+0x29/0x42 >> [ 0.862739] [] ? raw_local_irq_disable+0x19/0x1b >> [ 0.862748] [] ? _write_lock_irq+0xd/0x21 >> [ 0.862756] [] ? raw_local_irq_enable+0x19/0x1b >> [ 0.862763] [] ? exit_ptrace+0xa0/0x110 >> [ 0.862770] [] ? raw_local_irq_disable+0x19/0x1b >> [ 0.862777] [] do_exit+0x79/0x629 >> [ 0.862784] [] sys_exit_group+0x0/0x16 >> [ 0.862791] [] get_signal_to_deliver+0x312/0x335 >> [ 0.862800] [] do_notify_resume+0x8b/0x717 >> [ 0.862807] [] ? print_vma_addr+0xf8/0x101 >> [ 0.862815] [] ? scale_delta+0x0/0x26 >> [ 0.862823] [] ? __up_read+0x84/0x8c >> [ 0.862830] [] ? scale_delta+0x0/0x26 >> [ 0.862837] [] ? bad_area_nosemaphore+0xe/0x10 >> [ 0.862844] [] ? do_page_fault+0x14c/0x271 >> [ 0.862852] [] retint_signal+0x48/0x8c >> [ 0.862858] [] ? scale_delta+0x0/0x26 >> ####### >> >> >> Best Regards >> Jiajun >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel >> >> >> > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >