From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Tomasz Wroblewski <tomasz.wroblewski@citrix.com>
Cc: Milan opath <milan.opath@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Ben Guthro <ben@guthro.net>, Jan Beulich <JBeulich@suse.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: resume from S3 sleep not working in Dom0 - Xen4.2.1
Date: Fri, 8 Feb 2013 16:22:58 -0500 [thread overview]
Message-ID: <CACJDEmo4CMhRdYaVPwz01DS37z+_BMo+NbS2cSCKa-YRUAfxUA@mail.gmail.com> (raw)
In-Reply-To: <5114CF55.5000303@citrix.com>
On Fri, Feb 8, 2013 at 5:11 AM, Tomasz Wroblewski
<tomasz.wroblewski@citrix.com> wrote:
>
>> Hm, that is suspect. There should not be any cpuidle_register? Perhaps
>> you are .. ah yes, you are hitting a bug that should be in the stable
>> tree fix.
>>
>> Here is the git commit b88a634a903d9670aa5f2f785aa890628ce0dece and
>> 6f8c2e7933679f54b6478945dc72e59ef9a3d5e0
>>
>>
>
> Thanks Konrad. I've tried your patches, and whilst I have not seen this
> crash in cpuidle_register anymore, the others are still present (in
> build_schedule_domains for example).
>
That looks familiar too. I think it got fixed in the upstream kernel
and it was a generic bug - but I can't recall which commit it was.
> I've stumbled on a bit of interesting info - using dom0_vcpus_pin on xen
> commandline stops both the xen scheduler and dom0 kernel crashing and all
> works fine - made dozens of succesfull s3 attempts. Was wondering if you
> guys had any thoughts on this? Is the dom0 kernel even supposed to cope
> during s3 in non dom0 vcpu pin case?
>
No that is something new. Is this only an issue on Intel boxes but not AMD?
next prev parent reply other threads:[~2013-02-08 21:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 11:39 resume from S3 sleep not working in Dom0 - Xen4.2.1 Milan opath
2013-02-04 0:57 ` Ben Guthro
2013-02-04 9:47 ` Jan Beulich
2013-02-04 10:07 ` Tomasz Wroblewski
2013-02-05 18:32 ` Konrad Rzeszutek Wilk
2013-02-08 7:47 ` Milan opath
2013-02-08 8:05 ` Jan Beulich
2013-02-08 8:07 ` Tomasz Wroblewski
2013-02-08 10:11 ` Tomasz Wroblewski
2013-02-08 21:22 ` Konrad Rzeszutek Wilk [this message]
2013-02-09 17:21 ` Milan opath
2013-02-12 20:02 ` Konrad Rzeszutek Wilk
2013-02-12 21:40 ` Milan opath
2013-02-12 21:56 ` Konrad Rzeszutek Wilk
2013-02-13 8:27 ` Jan Beulich
2013-02-13 11:48 ` Ben Guthro
2013-02-16 17:07 ` Milan opath
2013-02-11 8:42 ` Tomasz Wroblewski
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=CACJDEmo4CMhRdYaVPwz01DS37z+_BMo+NbS2cSCKa-YRUAfxUA@mail.gmail.com \
--to=konrad@kernel.org \
--cc=JBeulich@suse.com \
--cc=ben@guthro.net \
--cc=konrad.wilk@oracle.com \
--cc=milan.opath@gmail.com \
--cc=tomasz.wroblewski@citrix.com \
--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).