WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] cpuidle causing Dom0 soft lockups

To: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] cpuidle causing Dom0 soft lockups
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Thu, 4 Feb 2010 09:40:37 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Wed, 03 Feb 2010 17:41:58 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B6969AB.60605@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4B58402E020000780002B3FE@xxxxxxxxxxxxxxxxxx> <C77DE51B.6F89%keir.fraser@xxxxxxxxxxxxx> <4B67E85E020000780002D1A0@xxxxxxxxxxxxxxxxxx> <8B81FACE836F9248894A7844CC0BA814250B6A12F0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B695ADB020000780002D70F@xxxxxxxxxxxxxxxxxx> <73BDC2BA3DA0BD47BAAEE12383D407EF35C2F436@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B6969AB.60605@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acqkyw6nssgMf9dfSIqdUuaapvh6YAAb584g
Thread-topic: [Xen-devel] cpuidle causing Dom0 soft lockups
>From: Juergen Gross [mailto:juergen.gross@xxxxxxxxxxxxxx] 
>Sent: 2010年2月3日 20:19
>
>Tian, Kevin wrote:
>>> From: Jan Beulich
>>> Sent: 2010年2月3日 18:16
>>>
>>>>>> "Yu, Ke" <ke.yu@xxxxxxxxx> 02.02.10 18:07 >>>
>>>>> Just fyi, we now also have seen an issue on a 24-CPU 
>system that went
>>>>> away with cpuidle=0 (and static analysis of the hang 
>hinted in that
>>>>> direction). All I can judge so far is that this likely has 
>>> something to do
>>>>> with our kernel's intensive use of the poll hypercall (i.e. 
>>> we see vCPU-s
>>>>> not waking up from the call despite there being pending 
>unmasked or
>>>>> polled for events).
>>>> We just identified the cause of this issue, and is trying to 
>>> find appropriate way to fix it.
>>>
>>> Hmm, while I agree that the scenario you describe can be a 
>problem, I
>>> don't think it can explain the behavior on the 24-CPU system pointed
>>> out above, nor the one Juergen Gross pointed out yesterday.
>> 
>> Is 24-CPU system observed with same likelihood as 64-CPU system to
>> hang at boot time, or less frequent? Ke just did some 
>theoretical analysis
>> by assuming some values. There could be other factors added 
>to latency
>> and each system may have different characteristics too. We can't
>> draw conclusion whether smaller system will face same issue, 
>by simply
>> changing CPU number in Ke's formula. :-) Possibly you can 
>provide cpuidle
>> information on your 24-core system for further comparison.
>
>My 4-core system hangs _always_. For minutes. If I press any key on the
>console it will resume booting with soft lockup messages (all cpus were
>in xen_safe_halt).
>Sometimes another hang occurs, sometimes the system will come 
>up without
>further hangs.
>
>Juergen
>

interesting. Then did you also observe hang disappeared by disabling
cpuidle? Your case really looks like some missed event scenario, in
which key press just kicks cpu alive...

Thanks,
Kevin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel