[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Crash with paravirt-ops 2.6.31.6 kernel
On 11/18/09 03:04, William Pitcock wrote: > Begin: Running /scripts/init-bottom ... done. > [ 1.254927] init[1] general protection ip:f779042f sp:ff9b0340 error:0 > [ 1.255189] Kernel panic - not syncing: Attempted to kill init! > [ 1.255202] Pid: 1, comm: init Tainted: G W 2.6.31.6 #2 > [ 1.255210] Call Trace: > [ 1.255226] [<ffffffff8128526b>] ? panic+0x86/0x133 > [ 1.255237] [<ffffffff810cc7bf>] ? mntput_no_expire+0x23/0xed > [ 1.255247] [<ffffffff81117a83>] ? cap_file_free_security+0x0/0x1 > [ 1.255258] [<ffffffff8100d155>] ? xen_force_evtchn_callback+0x9/0xa > [ 1.255267] [<ffffffff8100d7c2>] ? check_events+0x12/0x20 > [ 1.255275] [<ffffffff81117a83>] ? cap_file_free_security+0x0/0x1 > [ 1.255285] [<ffffffff81287365>] ? _write_lock_irq+0x7/0x16 > [ 1.255295] [<ffffffff81040e59>] ? exit_ptrace+0xa7/0x126 > [ 1.255304] [<ffffffff8103af48>] ? do_exit+0x72/0x66b > [ 1.255312] [<ffffffff8103b5ad>] ? do_group_exit+0x6c/0x99 > [ 1.255321] [<ffffffff8104513c>] ? get_signal_to_deliver+0x303/0x327 > [ 1.255332] [<ffffffff8116a0e0>] ? dummycon_dummy+0x0/0x3 > [ 1.255341] [<ffffffff812873b3>] ? _spin_unlock_irqrestore+0xc/0xd > [ 1.255351] [<ffffffff8100ee2a>] ? do_notify_resume+0x79/0x6d1 > [ 1.255360] [<ffffffff812873b3>] ? _spin_unlock_irqrestore+0xc/0xd > [ 1.255369] [<ffffffff8100d7c2>] ? check_events+0x12/0x20 > [ 1.255378] [<ffffffff8100d155>] ? xen_force_evtchn_callback+0x9/0xa > [ 1.255387] [<ffffffff8100d7c2>] ? check_events+0x12/0x20 > [ 1.255396] [<ffffffff8116a0e0>] ? dummycon_dummy+0x0/0x3 > [ 1.255404] [<ffffffff812873b3>] ? _spin_unlock_irqrestore+0xc/0xd > [ 1.255414] [<ffffffff8100d7af>] ? xen_restore_fl_direct_end+0x0/0x1 > [ 1.255423] [<ffffffff812873b3>] ? _spin_unlock_irqrestore+0xc/0xd > [ 1.255432] [<ffffffff81044a57>] ? force_sig_info+0xd3/0xe1 > [ 1.255441] [<ffffffff810103dc>] ? retint_signal+0x48/0x8c > > I don't know why this is happening. It does not happen on XenSource 2.6.18 > kernel, or the Debian 2.6.26 kernel. > Unfortunately this is a known bug that hasn't been properly investigated yet. There's a bug in AMD syscall return on 32-on-64 domains; the workaround is to boot with "vdso32=0" on the kenrel command line. J _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |