[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Only CPU0 active after ACPI S3, xen 4.1.3
On 21.12.2012 14:59, Marek Marczykowski wrote: > On 21.12.2012 14:42, Jan Beulich wrote: >>>>> On 21.12.12 at 14:33, Marek Marczykowski <marmarek@xxxxxxxxxxxxxxxxxxxxxx> >> wrote: >>> On 21.12.2012 09:55, Jan Beulich wrote: >>>>>>> On 21.12.12 at 05:52, Marek Marczykowski >>>>>>> <marmarek@xxxxxxxxxxxxxxxxxxxxxx> >>> wrote: >>>>> On 21.12.2012 00:17, Marek Marczykowski wrote: >>>>>> With this patch applied (on 4.1.4 and 4.3-unstable), I've got original >>>>> symptom >>>>>> - only CPU0 active after ACPI S3. Didn't get reboot after few tries. >>>>>> "xl debug-key r" output attached. >>>>>> Anyway it looks like bug was introduced somehow between 4.1.2 and 4.1.3 >>>>>> - on >>>>>> 4.1.2 none of above problems happened. >>>>> >>>>> I've done bisect on xen 4.1 and found problematic commit: >>>>> http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/1f95b55ef427 >>>> >>>> In that case, using "sched_ratelimit_us=0" should make the >>>> problem go away again - did you try that? >>> >>> This option does not help when trying 4.1.4, but does when trying xen >>> compiled >>> from above c/s. >> >> Which basically calls for you doing another bisection round, this >> time with that option in place. > > Will try, but not sure if will have time for it before Christmas. Next bisection (this time with sched_ratelimit_us=0) gives this commit: http://xenbits.xen.org/hg/xen-4.1-testing.hg/rev/d67e4d12723f I've tried also xen-4.1 tip with Ben's patch and sched_ratelimit_us=0, but it didn't worked well - got all vCPUs on pCPU 0, instead on reboot (more common effect). Not sure if this is really different effect or just non-deterministic behavior of the same bug. -- Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab Attachment:
signature.asc _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |