[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Xen 4.6 DomU crashes: domain_crash_sync called from entry.S: fault at ffff82d08022a01e create_bounce_frame+0x66/0x13a



On Fri, 2015-12-04 at 11:49 +0100, Maarten Coenaerts wrote:
> Just had another reboot of the domU and now I have a kernel panic inÂÂ
> the console log.
> Is this a problem with unstable clocksource?

Whatever this issue is it certainly looks like a bug. I'd suggest posting
to xen-devel. SeeÂhttp://wiki.xen.org/wiki/Reporting_Bugs_against_XenÂfor
more info.

Ian.

> 
> [79376.951876] general protection fault: febc [#1] SMP
> [79376.951885] Modules linked in: rpcsec_gss_krb5 xt_tcpudp xt_limit 
> xt_state xt_multiport iptable_filter iptable_nat nf_conntrack_ipv4 
> nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle ip_tables 
> x_tables x86_pkg_temp_thermal thermal_sys coretemp evdev snd_pcm 
> snd_timer crct10dif_pclmul crc32_pclmul snd soundcore pcspkr r8168(O) 
> crc32c_intel
> [79376.951910] CPU: 4 PID: 898 Comm: ntpd Tainted: GÂÂÂÂÂÂÂÂÂÂÂO 4.1.13
> #1
> [79376.951914] task: ffff8802e88dee80 ti: ffff8802eebf8000 task.ti: 
> ffff8802eebf8000
> [79376.951919] RIP: e030:[<ffffffff810471df>] [<ffffffff810471df>] 
> setup_sigcontext+0xde/0x13f
> [79376.951927] RSP: e02b:ffff8802eebfbe30ÂÂEFLAGS: 00010246
> [79376.951930] RAX: 0000000000000246 RBX: 00007ffddc51a878 RCX: 
> 0000000000000000
> [79376.951933] RDX: ffff8802eebfbf58 RSI: 00007ffddc51aa40 RDI: 
> 00007ffddc51a8a8
> [79376.951937] RBP: ffff8802e88df4b0 R08: 0000000000000000 R09: 
> ffff88000389df00
> [79376.951940] R10: ffff88000389df00 R11: 0000000000000005 R12: 
> 0000000000000000
> [79376.951943] R13: 000000000000000e R14: 00007ffddc51aa40 R15: 
> ffff8802eebfbf58
> [79376.951949] FS:ÂÂ00007f064a398700(0000) GS:ffff8802f0d00000(0000) 
> knlGS:ffff8802f0d00000
> [79376.951953] CS:ÂÂe033 DS: 0000 ES: 0000 CR0: 0000000080050033
> [79376.951957] CR2: ffffffffff600400 CR3: 00000002ec1aa000 CR4: 
> 0000000000042660
> [79376.951960] Stack:
> [79376.951962]ÂÂffffffff81047572 00000003950ffebe 0000000000000000 
> 0000000000000000
> [79376.951967]ÂÂ0000000000000340 0000000000000000 000000000042c640 
> 0000000004000000
> [79376.951973]ÂÂ00007f0649009230 0000000000000000 000000000000000e 
> 000000000001fffe
> [79376.951979] Call Trace:
> [79376.951982]ÂÂ[<ffffffff81047572>] ? do_signal+0x332/0x53e
> [79376.951987]ÂÂ[<ffffffff81040f75>] ? xen_clocksource_read+0x12/0x14
> [79376.951990]ÂÂ[<ffffffff8104778b>] ? do_notify_resume+0xd/0x48
> [79376.951995]ÂÂ[<ffffffff8157687c>] ? int_signal+0x12/0x17
> [79376.951998] Code: 00 48 8b 80 d8 05 00 00 48 89 87 98 00 00 00 48 8b 
> 82 80 00 00 00 48 89 87 80 00 00 00 48 8b 82 90 00 00 00 48 89 87 88 00 
> 00 00 <48> cb 82 88 00 00 00 66 89 87 90 00 00 00 66 c7 87 92 00 00 00
> [79376.952027] RIPÂÂ[<ffffffff810471df>] setup_sigcontext+0xde/0x13f
> [79376.952031]ÂÂRSP <ffff8802eebfbe30>
> [79376.952043] ---[ end trace 7994404a264eb3f4 ]---
> [79376.952492] general protection fault: 0000 [#2] SMP
> [79376.952498] Modules linked in: rpcsec_gss_krb5 xt_tcpudp xt_limit 
> xt_state xt_multiport iptable_filter iptable_nat nf_conntrack_ipv4 
> nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle ip_tables 
> x_tables x86_pkg_temp_thermal thermal_sys coretemp evdev snd_pcm 
> snd_timer crct10dif_pclmul crc32_pclmul snd soundcore pcspkr r8168(O) 
> crc32c_intel
> [79376.952521] CPU: 5 PID: 1 Comm: init Tainted: GÂÂÂÂÂÂDÂÂÂÂO 4.1.13 #1
> [79376.952525] task: ffff8802eed60000 ti: ffff8802eed68000 task.ti: 
> ffff8802eed68000
> [79376.952530] RIP: e030:[<ffffffff810471df>] [<ffffffff810471df>] 
> setup_sigcontext+0xde/0x13f
> [79376.952537] RSP: e02b:ffff8802eed6be30ÂÂEFLAGS: 00010246
> [79376.952540] RAX: 0000000000000246 RBX: 00007ffc1375c278 RCX: 
> 0000000000000000
> [79376.952543] RDX: ffff8802eed6bf58 RSI: 00007ffc1375c440 RDI: 
> 00007ffc1375c2a8
> [79376.952546] RBP: ffff8802eed60630 R08: 0000000000000000 R09: 
> ffff8802f0d59ea0
> [79376.952550] R10: ffff8802edf47a00 R11: 0000000000000005 R12: 
> 0000000000000000
> [79376.952553] R13: 0000000000000011 R14: 00007ffc1375c440 R15: 
> ffff8802eed6bf58
> [79376.952558] FS:ÂÂ00007fce2a6267a0(0000) GS:ffff8802f0d40000(0000) 
> knlGS:ffff8802f0d40000
> [79376.952563] CS:ÂÂe033 DS: 0000 ES: 0000 CR0: 0000000080050033
> [79376.952566] CR2: ffffffffff600400 CR3: 00000002ea106000 CR4: 
> 0000000000042660
> [79376.952570] Stack:
> [79376.952572]ÂÂffffffff81047572 0000000000000001 0000000000000000 
> 0000000000000000
> [79376.952577]ÂÂ0000000000000000 00000000fffffdfe 0000000000402a80 
> 0000000014000000
> [79376.952583]ÂÂ00007fce29f04230 0000000000000000 0000000000000011 
> ffffffff00040002
> [79376.952589] Call Trace:
> [79376.952592]ÂÂ[<ffffffff81047572>] ? do_signal+0x332/0x53e
> [79376.952597]ÂÂ[<ffffffff8118d8be>] ?
> poll_select_copy_remaining+0xe3/0xf9
> [79376.952601]ÂÂ[<ffffffff8104778b>] ? do_notify_resume+0xd/0x48
> [79376.952605]ÂÂ[<ffffffff8157687c>] ? int_signal+0x12/0x17
> [79376.952608] Code: 00 48 8b 80 d8 05 00 00 48 89 87 98 00 00 00 48 8b 
> 82 80 00 00 00 48 89 87 80 00 00 00 48 8b 82 90 00 00 00 48 89 87 88 00 
> 00 00 <48> cb 82 88 00 00 00 66 89 87 90 00 00 00 66 c7 87 92 00 00 00
> [79376.952638] RIPÂÂ[<ffffffff810471df>] setup_sigcontext+0xde/0x13f
> [79376.952642]ÂÂRSP <ffff8802eed6be30>
> [79376.952646] ---[ end trace 7994404a264eb3f5 ]---
> [79376.952784] Kernel panic - not syncing: Attempted to kill init! 
> exitcode=0x0000000b
> [79376.952784]
> [79376.952798] Kernel Offset: disabled
> 
> KR,
> Maarten
> 
> On 3/12/2015 17:44, Maarten Coenaerts wrote:
> > Hi,
> > 
> > I'm having a problem with an Xen 4.6.0 install on debian jessie 8.2
> > with
> > kernel 4.1.13.
> > 1 domU has been unexpectedly rebooted 2 times in the past 8 days, no
> > logs in the domU itself.
> > Enabled guest console logging but no luck yet on getting any logs on
> > why
> > the reboot occurs.
> > 
> > Then today a domU crashed with following trace in xl dmesg:
> > 
> > (XEN) domain_crash_sync called from entry.S: fault at ffff82d08022a01e
> > create_bounce_frame+0x66/0x13a
> > (XEN) Domain 12 (vcpu#7) crashed on cpu#6:
> > (XEN) ----[ Xen-4.6.0ÂÂx86_64ÂÂdebug=nÂÂNot tainted ]----
> > (XEN) CPU:ÂÂÂÂ6
> > (XEN) RIP:ÂÂÂÂe033:[<ffffffff81041530>]
> > (XEN) RFLAGS: 0000000000010206ÂÂÂEM: 0ÂÂÂCONTEXT: pv guest (d12v7)
> > (XEN) rax: 00000000000000caÂÂÂrbx: 000000000000006eÂÂÂrcx:
> > ffffffff81041530
> > (XEN) rdx: 0000000000000001ÂÂÂrsi: 0000000000000081ÂÂÂrdi:
> > 00007fc1749baa28
> > (XEN) rbp: 00007fc1734f36b0ÂÂÂrsp: 00007fc17fe2ddf5ÂÂÂr8:
> > 00007fc1749baa28
> > (XEN) r9:ÂÂ0000000000000646ÂÂÂr10: 00007fc1734f3670ÂÂÂr11:
> > 0000000000000206
> > (XEN) r12: 00000000000001f4ÂÂÂr13: 00007fc1749baa00ÂÂÂr14:
> > 00007fc1749baa28
> > (XEN) r15: 00007fc1749baa50ÂÂÂcr0: 0000000080050033ÂÂÂcr4:
> > 00000000001526e0
> > (XEN) cr3: 0000000066760000ÂÂÂcr2: 00007fc17fe2dded
> > (XEN) ds: 0000ÂÂÂes: 0000ÂÂÂfs: 0000ÂÂÂgs: 0000ÂÂÂss: e02bÂÂÂcs: e033
> > (XEN) Guest stack trace from rsp=00007fc17fe2ddf5:
> > (XEN)ÂÂÂÂ0000841f0fc35e5a 4955415441000000 ec8348f58949fc89
> > c748f631e7894810
> > (XEN)ÂÂÂÂ48d0ffff600000c0 0003e8bf0824448b 007d8b49e7f74800
> > 243c2b4808758b49
> > (XEN)ÂÂÂÂc681480a79c62948 48cfff483b9aca00 243c89483678ff85
> > 148b410824748948
> > (XEN)ÂÂÂÂe289491474d28524 00cab8e7894cf631 75003f83050f0000
> > 4110c48348c0310b
> > (XEN)ÂÂÂÂ92f88348c35c415d eb0000006eb88f75 90909090909090ea
> > 314d525241909090
> > (XEN)ÂÂÂÂ6400000080f681d2 8900000048253423 a980000000ca81c2
> > d0392b7540000000
> > (XEN)ÂÂÂÂ097517b10ff00674 8b050f000000cab8 148b64da75c08507
> > 00ca81000002d025
> > (XEN)ÂÂÂÂ7517b10ff0800000 666666c35a415ac6 0000841f0f2e6666
> > 20d4213d83000000
> > (XEN)ÂÂÂÂ8949514175740000 81ffffffffb941d2 34236400000080f6
> > 09ce810000004825
> > (XEN)ÂÂÂÂ40000000a9000001 0000ca81c2893c75 0ff00d74c2398000
> > 000000c1c74817b1
> > (XEN)ÂÂÂÂ000000cab80b7500 c085078bc189050f 02d025148b641775
> > 80000000ca810000
> > (XEN)ÂÂÂÂ5941037517b10ff0 f983057492f983c3 ebd8f7c889b075ea
> > 9aca00087a8148ed
> > (XEN)ÂÂÂÂ41000000d4830f3b 5655415441514150 49fc894920ec8348
> > 481024448948d589
> > (XEN)ÂÂÂÂ00c0c748f631e789 448b48d0ffff6000 48000003e8bf0824
> > 8b49007d8b49e7f7
> > (XEN)ÂÂÂÂ2948243c2b480875 ca00c681480a79c6 ff8548cfff483b9a
> > 89480000008c880f
> > (XEN)ÂÂÂÂ480824748948243c ca81d0891024548b 000000a980000000
> > f00f74c239537540
> > (XEN)ÂÂÂÂc1c7482414b10f41 8949267500000000 80f6812024748be2
> > 4825342364000000
> > (XEN)ÂÂÂÂcab8e7894c000000 c18948050f000000 2975c08524048b41
> > 000002d025148b64
> > (XEN)ÂÂÂÂ41f080000000ca81 834813752414b10f 59415c415d4128c4
> > 00000016b8c35841
> > (XEN)ÂÂÂÂff30850f92f983c3 eb0000006eb8ffff 90909090909090dd
> > 25348b645f909090
> > 
> > 
> > Any idea what I can do to get more info about the error?
> > 
> > KR,
> > Maarten
> > 
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxx
> > http://lists.xen.org/xen-users
> > 
> > 
> 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.