* vcpu migration Xen crash in 4.1
@ 2011-03-18 16:48 Ian Jackson
2011-03-18 17:09 ` Tim Deegan
2011-03-18 17:12 ` Jan Beulich
0 siblings, 2 replies; 4+ messages in thread
From: Ian Jackson @ 2011-03-18 16:48 UTC (permalink / raw)
To: xen-devel
I'm having numerous watchdog-induced crashes with Xen 4.1. Here is an
example. This happens on either of my two Dell R310s but not
(apparently) on other machines. Here is an example:
Mar 18 16:22:52.141183 (XEN) Watchdog timer detects that CPU3 is stuck!
Mar 18 16:23:58.689745 (XEN) ----[ Xen-4.1.0-rc7 x86_32p debug=n Not tainted ]----
Mar 18 16:23:58.689846 (XEN) CPU: 3
Mar 18 16:23:58.704363 (XEN) EIP: e008:[<ff116120>] _csched_cpu_pick+0xc0/0x3e0
Mar 18 16:23:58.704434 (XEN) EFLAGS: 00000046 CONTEXT: hypervisor
Mar 18 16:23:58.709625 (XEN) eax: 00000000 ebx: 00000002 ecx: 00000004 edx: 00000004
Mar 18 16:23:58.709690 (XEN) esi: ff2e7e6c edi: ff2e7e7c ebp: 00000006 esp: ff2e7e40
Mar 18 16:23:58.721258 (XEN) cr0: 8005003b cr4: 000026f0 cr3: 00286c80 cr2: dd8f64b4
Mar 18 16:23:58.721325 (XEN) ds: e010 es: e010 fs: 0000 gs: 0033 ss: e010 cs: e008
Mar 18 16:23:58.729310 (XEN) Xen stack trace from esp=ff2e7e40:
Mar 18 16:23:58.729368 (XEN) ff2e7e9c ff2e7e9c ff2e7e6c 00000080 00000080 0000e010 00000000 ff2723b0
Mar 18 16:23:58.741268 (XEN) 01000000 00000005 00000001 000000c0 00000000 00000000 00000000 00000030
Mar 18 16:23:58.749754 (XEN) 00000000 00000000 00000000 000000fb 00000000 00000000 00000000 00000003
Mar 18 16:23:58.749825 (XEN) 00000000 00000000 00000000 ff2e1024 ff2ec024 00000003 00000000 ff11f6e6
Mar 18 16:23:58.761276 (XEN) ff20b9a0 ff286000 ff271820 ff271820 ff286000 00000206 ff2e1024 ff2ea000
Mar 18 16:23:58.769645 (XEN) ff2e7efc 00000003 ff286000 ff14ab79 ff286000 00000080 00000000 00000000
Mar 18 16:23:58.781243 (XEN) 00000000 00000000 00000000 ff2ea000 ff286000 00000003 00000000 ff11edda
Mar 18 16:23:58.781313 (XEN) ff286000 ff2ea000 6a1a3faa 00000018 00000000 ff2ec030 00000002 00000018
Mar 18 16:23:58.789653 (XEN) ff2ec030 6a1e908d 6a1a3faa 00000018 ff2ec080 ff2ec020 ff286150 c9c1c070
Mar 18 16:23:58.801316 (XEN) ff271900 6a1a36c7 ff2ea000 ffffffff ffffffff ff271900 ffbeec08 00000003
Mar 18 16:23:58.801400 (XEN) ffffffff ff2e7fb0 bf819718 ff120244 00000003 ff1db38b ff145bf4 00000000
Mar 18 16:23:58.809665 (XEN) ff286000 0000007b 0000007b ff1db406 00000000 00000011 00005949 00000001
Mar 18 16:23:58.821253 (XEN) 00000000 bf819718 00000000 00f90000 08052958 00000073 00000283 bf819718
Mar 18 16:23:58.829247 (XEN) 0000007b 0000007b 0000007b 00000000 00000033 00000003 ff2ea000 0007a800
Mar 18 16:23:58.829318 (XEN) Xen call trace:
Mar 18 16:23:58.837508 (XEN) [<ff116120>] _csched_cpu_pick+0xc0/0x3e0
Mar 18 16:23:58.837566 (XEN) [<ff11f6e6>] vcpu_migrate+0xd6/0x200
Mar 18 16:23:58.837623 (XEN) [<ff14ab79>] context_switch+0xd9/0x1d0
Mar 18 16:23:58.849259 (XEN) [<ff11edda>] schedule+0x28a/0x610
Mar 18 16:23:58.849314 (XEN) [<ff120244>] __do_softirq+0x54/0x90
Mar 18 16:23:58.857446 (XEN) [<ff1db38b>] hypercall+0x8b/0x92
Mar 18 16:23:58.857499 (XEN) [<ff145bf4>] smp_apic_timer_interrupt+0x44/0x70
Mar 18 16:23:58.857558 (XEN) [<ff1db406>] process_softirqs+0x6/0x10
Mar 18 16:23:58.869265 (XEN)
Mar 18 16:23:58.869303 (XEN)
Mar 18 16:23:58.869337 (XEN) ****************************************
Mar 18 16:23:58.869389 (XEN) Panic on CPU 3:
Mar 18 16:23:58.877386 (XEN) FATAL TRAP: vector = 2 (nmi)
Mar 18 16:23:58.877436 (XEN) [error_code=0000] , IN INTERRUPT CONTEXT
Mar 18 16:23:58.877490 (XEN) ****************************************
Mar 18 16:23:58.885257 (XEN)
Mar 18 16:23:58.885293 (XEN) Reboot in five seconds...
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: vcpu migration Xen crash in 4.1
2011-03-18 16:48 vcpu migration Xen crash in 4.1 Ian Jackson
@ 2011-03-18 17:09 ` Tim Deegan
2011-03-18 17:22 ` Keir Fraser
2011-03-18 17:12 ` Jan Beulich
1 sibling, 1 reply; 4+ messages in thread
From: Tim Deegan @ 2011-03-18 17:09 UTC (permalink / raw)
To: Ian Jackson; +Cc: xen-devel@lists.xensource.com, keir
At 16:48 +0000 on 18 Mar (1300466889), Ian Jackson wrote:
> Mar 18 16:23:58.829318 (XEN) Xen call trace:
> Mar 18 16:23:58.837508 (XEN) [<ff116120>] _csched_cpu_pick+0xc0/0x3e0
> Mar 18 16:23:58.837566 (XEN) [<ff11f6e6>] vcpu_migrate+0xd6/0x200
> Mar 18 16:23:58.837623 (XEN) [<ff14ab79>] context_switch+0xd9/0x1d0
Looks like http://xenbits.xen.org/hg/staging/xen-unstable.hg/rev/3caed2112c65
is needed on the 4.1-testing tree as well. Keir?
Cheers,
Tim.
--
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: vcpu migration Xen crash in 4.1
2011-03-18 16:48 vcpu migration Xen crash in 4.1 Ian Jackson
2011-03-18 17:09 ` Tim Deegan
@ 2011-03-18 17:12 ` Jan Beulich
1 sibling, 0 replies; 4+ messages in thread
From: Jan Beulich @ 2011-03-18 17:12 UTC (permalink / raw)
To: Ian Jackson; +Cc: xen-devel
>>> On 18.03.11 at 17:48, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
> I'm having numerous watchdog-induced crashes with Xen 4.1. Here is an
> example. This happens on either of my two Dell R310s but not
> (apparently) on other machines. Here is an example:
Looks like 4.1 is missing -unstable 23043:3caed2112c65.
Jan
> Mar 18 16:22:52.141183 (XEN) Watchdog timer detects that CPU3 is stuck!
> Mar 18 16:23:58.689745 (XEN) ----[ Xen-4.1.0-rc7 x86_32p debug=n Not tainted ]----
> Mar 18 16:23:58.689846 (XEN) CPU: 3
> Mar 18 16:23:58.704363 (XEN) EIP: e008:[<ff116120>]
> _csched_cpu_pick+0xc0/0x3e0
> Mar 18 16:23:58.704434 (XEN) EFLAGS: 00000046 CONTEXT: hypervisor
> Mar 18 16:23:58.709625 (XEN) eax: 00000000 ebx: 00000002 ecx: 00000004
> edx: 00000004
> Mar 18 16:23:58.709690 (XEN) esi: ff2e7e6c edi: ff2e7e7c ebp: 00000006
> esp: ff2e7e40
> Mar 18 16:23:58.721258 (XEN) cr0: 8005003b cr4: 000026f0 cr3: 00286c80
> cr2: dd8f64b4
> Mar 18 16:23:58.721325 (XEN) ds: e010 es: e010 fs: 0000 gs: 0033 ss:
> e010 cs: e008
> Mar 18 16:23:58.729310 (XEN) Xen stack trace from esp=ff2e7e40:
> Mar 18 16:23:58.729368 (XEN) ff2e7e9c ff2e7e9c ff2e7e6c 00000080 00000080
> 0000e010 00000000 ff2723b0
> Mar 18 16:23:58.741268 (XEN) 01000000 00000005 00000001 000000c0 00000000
> 00000000 00000000 00000030
> Mar 18 16:23:58.749754 (XEN) 00000000 00000000 00000000 000000fb 00000000
> 00000000 00000000 00000003
> Mar 18 16:23:58.749825 (XEN) 00000000 00000000 00000000 ff2e1024 ff2ec024
> 00000003 00000000 ff11f6e6
> Mar 18 16:23:58.761276 (XEN) ff20b9a0 ff286000 ff271820 ff271820 ff286000
> 00000206 ff2e1024 ff2ea000
> Mar 18 16:23:58.769645 (XEN) ff2e7efc 00000003 ff286000 ff14ab79 ff286000
> 00000080 00000000 00000000
> Mar 18 16:23:58.781243 (XEN) 00000000 00000000 00000000 ff2ea000 ff286000
> 00000003 00000000 ff11edda
> Mar 18 16:23:58.781313 (XEN) ff286000 ff2ea000 6a1a3faa 00000018 00000000
> ff2ec030 00000002 00000018
> Mar 18 16:23:58.789653 (XEN) ff2ec030 6a1e908d 6a1a3faa 00000018 ff2ec080
> ff2ec020 ff286150 c9c1c070
> Mar 18 16:23:58.801316 (XEN) ff271900 6a1a36c7 ff2ea000 ffffffff ffffffff
> ff271900 ffbeec08 00000003
> Mar 18 16:23:58.801400 (XEN) ffffffff ff2e7fb0 bf819718 ff120244 00000003
> ff1db38b ff145bf4 00000000
> Mar 18 16:23:58.809665 (XEN) ff286000 0000007b 0000007b ff1db406 00000000
> 00000011 00005949 00000001
> Mar 18 16:23:58.821253 (XEN) 00000000 bf819718 00000000 00f90000 08052958
> 00000073 00000283 bf819718
> Mar 18 16:23:58.829247 (XEN) 0000007b 0000007b 0000007b 00000000 00000033
> 00000003 ff2ea000 0007a800
> Mar 18 16:23:58.829318 (XEN) Xen call trace:
> Mar 18 16:23:58.837508 (XEN) [<ff116120>] _csched_cpu_pick+0xc0/0x3e0
> Mar 18 16:23:58.837566 (XEN) [<ff11f6e6>] vcpu_migrate+0xd6/0x200
> Mar 18 16:23:58.837623 (XEN) [<ff14ab79>] context_switch+0xd9/0x1d0
> Mar 18 16:23:58.849259 (XEN) [<ff11edda>] schedule+0x28a/0x610
> Mar 18 16:23:58.849314 (XEN) [<ff120244>] __do_softirq+0x54/0x90
> Mar 18 16:23:58.857446 (XEN) [<ff1db38b>] hypercall+0x8b/0x92
> Mar 18 16:23:58.857499 (XEN) [<ff145bf4>]
> smp_apic_timer_interrupt+0x44/0x70
> Mar 18 16:23:58.857558 (XEN) [<ff1db406>] process_softirqs+0x6/0x10
> Mar 18 16:23:58.869265 (XEN)
> Mar 18 16:23:58.869303 (XEN)
> Mar 18 16:23:58.869337 (XEN) ****************************************
> Mar 18 16:23:58.869389 (XEN) Panic on CPU 3:
> Mar 18 16:23:58.877386 (XEN) FATAL TRAP: vector = 2 (nmi)
> Mar 18 16:23:58.877436 (XEN) [error_code=0000] , IN INTERRUPT CONTEXT
> Mar 18 16:23:58.877490 (XEN) ****************************************
> Mar 18 16:23:58.885257 (XEN)
> Mar 18 16:23:58.885293 (XEN) Reboot in five seconds...
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: vcpu migration Xen crash in 4.1
2011-03-18 17:09 ` Tim Deegan
@ 2011-03-18 17:22 ` Keir Fraser
0 siblings, 0 replies; 4+ messages in thread
From: Keir Fraser @ 2011-03-18 17:22 UTC (permalink / raw)
To: Tim Deegan, Ian Jackson; +Cc: xen-devel@lists.xensource.com
On 18/03/2011 17:09, "Tim Deegan" <Tim.Deegan@citrix.com> wrote:
> At 16:48 +0000 on 18 Mar (1300466889), Ian Jackson wrote:
>> Mar 18 16:23:58.829318 (XEN) Xen call trace:
>> Mar 18 16:23:58.837508 (XEN) [<ff116120>] _csched_cpu_pick+0xc0/0x3e0
>> Mar 18 16:23:58.837566 (XEN) [<ff11f6e6>] vcpu_migrate+0xd6/0x200
>> Mar 18 16:23:58.837623 (XEN) [<ff14ab79>] context_switch+0xd9/0x1d0
>
> Looks like http://xenbits.xen.org/hg/staging/xen-unstable.hg/rev/3caed2112c65
> is needed on the 4.1-testing tree as well. Keir?
Yes, I've backported a couple of other fixes as well. Let's leave it to be
tested over the weekend, then do an -rc8 on Monday. We can maybe release end
of next week, or week on Monday.
-- Keir
> Cheers,
>
> Tim.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-03-18 17:22 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-18 16:48 vcpu migration Xen crash in 4.1 Ian Jackson
2011-03-18 17:09 ` Tim Deegan
2011-03-18 17:22 ` Keir Fraser
2011-03-18 17:12 ` Jan Beulich
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).