RE: [Xen-devel] [Patch] continue_hypercall_on_cpu rework using tasklets

["Wei, Gang" <gang.wei@xxxxxxxxx>]

On Monday, 2010-4-19 6:51 PM, Keir Fraser wrote:
> On 16/04/2010 18:51, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx> wrote:
> 
>>> We have a stress S3 test upon the Xen 4.1 unstable. Unfortunately,
>>> cset 21181 cannot pass the stress. It hangs after 48 times S3
>>> suspend/resume.  Another round test even shows it hangs after 2
>>> times suspend/resume. But it is too early to say cset 21181/21180
>>> is the evil, because even cset 21172 (cset ahead of
>>> continue_hypercall_on_cpu improvement patch) cannot pass the S3
>>> test either, although it has bigger success suspend/resume times
>>> than cset 21181 . so generally, there must be something wrong with
>>> S3 logic since Xen 4.0 release. We are still trying to dig it
>>> out...  
>> 
>> 21172 was not a good changeset to pick. I suggest trying
>> xen-unstable tip with just 21181/21180 reverted.
> 
> Actually, try xen-unstable staging tip (c/s 21202). I've just
> reimplemented tasklets, so things are quite different at latest tip.

Just tried c/s 21202, hung up during the 285th S3 resume on system with only 
legacy HPET broadcast. And it is more easy to hung up on HPET MSI broadcast 
capable system - need only <100 times.

Nothing wrong in the serial log, and ctrl-a didn't respond. I will try to find 
a debuging system with ITP to figure out the hanging point. Meanwhile, I will 
try cpu online/offline stress test see whether it is a general problem in cpu 
online/offline or just S3 specific.

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