From: Marek Marczykowski <marmarek@invisiblethingslab.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Ben Guthro <ben@guthro.net>,
xen-devel@lists.xen.org
Subject: Re: Only CPU0 active after ACPI S3, xen 4.1.3
Date: Fri, 21 Dec 2012 16:30:24 +0100 [thread overview]
Message-ID: <50D48090.6060603@invisiblethingslab.com> (raw)
In-Reply-To: <50D46B47.8000003@invisiblethingslab.com>
[-- Attachment #1.1: Type: text/plain, Size: 1769 bytes --]
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@invisiblethingslab.com>
>> wrote:
>>> On 21.12.2012 09:55, Jan Beulich wrote:
>>>>>>> On 21.12.12 at 05:52, Marek Marczykowski <marmarek@invisiblethingslab.com>
>>> 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 #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 551 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-12-21 15:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 18:55 Only CPU0 active after ACPI S3, xen 4.1.3 Marek Marczykowski
2012-11-30 9:33 ` Jan Beulich
2012-11-30 16:07 ` Marek Marczykowski
2012-11-30 16:12 ` Jan Beulich
2012-11-30 16:18 ` Marek Marczykowski
2012-12-03 7:39 ` Jan Beulich
2012-12-04 13:27 ` Marek Marczykowski
2012-12-20 15:59 ` Marek Marczykowski
2012-12-20 16:37 ` Jan Beulich
2012-12-20 19:41 ` Ben Guthro
2012-12-20 23:17 ` Marek Marczykowski
2012-12-21 4:52 ` Marek Marczykowski
2012-12-21 8:55 ` Jan Beulich
2012-12-21 13:33 ` Marek Marczykowski
2012-12-21 13:34 ` Marek Marczykowski
2012-12-21 13:42 ` Jan Beulich
2012-12-21 13:59 ` Marek Marczykowski
2012-12-21 14:03 ` Ben Guthro
2012-12-21 14:05 ` Jan Beulich
2012-12-21 15:30 ` Marek Marczykowski [this message]
2012-12-21 15:54 ` Ben Guthro
2012-12-21 16:03 ` Jan Beulich
2012-12-21 16:18 ` Ben Guthro
2012-12-23 2:49 ` Marek Marczykowski
2012-12-23 13:45 ` Ben Guthro
2012-12-31 12:51 ` Ben Guthro
2013-01-03 8:52 ` Jan Beulich
2013-01-16 11:22 ` George Dunlap
2013-01-16 11:58 ` George Dunlap
2013-01-16 13:08 ` Jan Beulich
2013-01-16 13:58 ` George Dunlap
2013-01-16 14:31 ` Jan Beulich
2013-01-03 8:52 ` Jan Beulich
2013-01-12 7:05 ` Marek Marczykowski
2013-01-14 3:28 ` Marek Marczykowski
2012-11-30 21:33 ` Konrad Rzeszutek Wilk
2012-11-30 22:12 ` Ben Guthro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50D48090.6060603@invisiblethingslab.com \
--to=marmarek@invisiblethingslab.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=ben@guthro.net \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).