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? 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] [<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 ####### Best Regards Jiajun _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Mr. Teo En Ming (Zhang Enming)
2009-Oct-26 14:03 UTC
Re: [Xen-devel] Latest Pv_ops dom0 fails to boot
What is the kernel version? -- Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering) Alma Maters: (1) Singapore Polytechnic (2) National University of Singapore Blog URL: http://teo-en-ming-aka-zhang-enming.blogspot.com Email: space.time.universe@gmail.com MSN: teoenming@hotmail.com Mobile Phone: +65-9648-9798 Street: Bedok Reservoir Road Republic of Singapore On Mon, Oct 26, 2009 at 9:55 PM, Xu, Jiajun <jiajun.xu@intel.com> 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? > > 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] [<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 > ####### > > > 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
It''s 2.6.31.4 On Monday, October 26, 2009 10:03 PM Mr. Teo En Ming (Zhang Enming) wrote:> What is the kernel version? > > -- > Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) > BEng(Hons)(Mechanical Engineering) Alma Maters: > (1) Singapore Polytechnic > (2) National University of Singapore > Blog URL: http://teo-en-ming-aka-zhang-enming.blogspot.com > Email: space.time.universe@gmail.com > MSN: teoenming@hotmail.com > Mobile Phone: +65-9648-9798 > Street: Bedok Reservoir Road > Republic of Singapore > > > > On Mon, Oct 26, 2009 at 9:55 PM, Xu, Jiajun > <jiajun.xu@intel.com> 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? >> >> 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] [<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 ####### >> >> >> Best Regards >> Jiajun >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-develBest Regards Jiajun _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Mr. Teo En Ming (Zhang Enming)
2009-Oct-26 14:41 UTC
Re: [Xen-devel] Latest Pv_ops dom0 fails to boot
Try my kernel configuration? See if it helps. Attached kernel config. -- Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering) Alma Maters: (1) Singapore Polytechnic (2) National University of Singapore Blog URL: http://teo-en-ming-aka-zhang-enming.blogspot.com Email: space.time.universe@gmail.com MSN: teoenming@hotmail.com Mobile Phone: +65-9648-9798 Street: Bedok Reservoir Road Republic of Singapore On Mon, Oct 26, 2009 at 10:16 PM, Xu, Jiajun <jiajun.xu@intel.com> wrote:> > It''s 2.6.31.4 > > On Monday, October 26, 2009 10:03 PM Mr. Teo En Ming (Zhang Enming) wrote: > >> What is the kernel version? >> >> -- >> Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) >> BEng(Hons)(Mechanical Engineering) Alma Maters: >> (1) Singapore Polytechnic >> (2) National University of Singapore >> Blog URL: http://teo-en-ming-aka-zhang-enming.blogspot.com >> Email: space.time.universe@gmail.com >> MSN: teoenming@hotmail.com >> Mobile Phone: +65-9648-9798 >> Street: Bedok Reservoir Road >> Republic of Singapore >> >> >> >> On Mon, Oct 26, 2009 at 9:55 PM, Xu, Jiajun >> <jiajun.xu@intel.com> 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? >>> >>> 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] [<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 ####### >>> >>> >>> Best Regards >>> Jiajun >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel > > > > Best Regards > Jiajun_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2009-Oct-27 19:23 UTC
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] [<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 > ####### > > > 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
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.
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] [<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
> #######
>
>
> 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
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2009-Oct-28 17:34 UTC
Re: [Xen-devel] Latest Pv_ops dom0 fails to boot
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] [<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 >> ####### >> >> >> 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 > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge wrote:> 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.No. If hypervisor doesn''t support the hypercall, it just return -ENOSYS, and dom0 can work well. But after implementing the hypercall in the hypervisor(Cset#20339), both dom0 and hypervisor all performs correpsonding actions in this case, so issues happen. That is to say, if disable this hypercall either in hypervisor or in dom0, it should work, but if enable both, the issue occurs. So it should be caused by incorrect hypercall implementation Xiantao _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2009-Oct-29 20:39 UTC
Re: [Xen-devel] Latest Pv_ops dom0 fails to boot
On 10/28/09 18:14, Zhang, Xiantao wrote:> Jeremy Fitzhardinge wrote: > >> 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. >> > No. If hypervisor doesn''t support the hypercall, it just return -ENOSYS, and dom0 can work well. But after implementing the hypercall in the hypervisor(Cset#20339), both dom0 and hypervisor all performs correpsonding actions in this case, so issues happen. That is to say, if disable this hypercall either in hypervisor or in dom0, it should work, but if enable both, the issue occurs. So it should be caused by incorrect hypercall implementation >It''s hard to see how any bug in either the Xen or kernel code relating to that could cause the symptoms you''re reporting, at least directly. Could you post the full output of the kernel boot? What is the host hardware? Thanks, J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Friday, October 30, 2009 4:39 AM Jeremy Fitzhardinge wrote:> On 10/28/09 18:14, Zhang, Xiantao wrote: >> Jeremy Fitzhardinge wrote: >> >>> 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. >>> >> No. If hypervisor doesn''t support the hypercall, it just > return -ENOSYS, and dom0 can work well. But after implementing > the hypercall in the hypervisor(Cset#20339), both dom0 and > hypervisor all performs correpsonding actions in this case, so > issues happen. That is to say, if disable this hypercall > either in hypervisor or in dom0, it should work, but if enable > both, the issue occurs. So it should be caused by incorrect > hypercall implementation >> > > It''s hard to see how any bug in either the Xen or kernel code relating > to that could cause the symptoms you''re reporting, at least directly. > Could you post the full output of the kernel boot? > > What is the host hardware?The bug is found only on 64-bit system, because on 32-bit system, option PARAVIRT_CLOCK_VSYSCALL is not selected. We meet the dom0 crash on both Core 2 Duo and Xeon X5300 Serial platorm. Best Regards Jiajun _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Maybe Matching Threads
- How to enable 64bit solaris guest on top of solaris dom0
- How to configure default NIC when creating Guest
- [PATCH] ioemu-remote: ACPI S3 state wake up
- rmeta package: metaplot or forestplot of meta-analysis under DSL (ramdon) model
- Testing Report for Xen 3.0.3 rc1