xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Joanna Rutkowska <joanna@invisiblethingslab.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Subject: Re: Re: DomU lockups after resume from S3 on Core	 i5 processors
Date: Tue, 06 Jul 2010 10:59:36 +0200	[thread overview]
Message-ID: <4C32F078.2080009@invisiblethingslab.com> (raw)
In-Reply-To: <4C33085E0200007800009AE1@vpn.id2.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 1728 bytes --]

On 07/06/10 10:41, Jan Beulich wrote:
>>>> On 06.07.10 at 01:17, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>> On 07/05/2010 03:52 PM, Joanna Rutkowska wrote:
>>> On 07/06/10 00:43, Jeremy Fitzhardinge wrote:
>>>> Do you know what's going on it in that it might be waiting
>>>> for?
>>>>     
>>> No idea. I might be guessing that it would be different kernel
>>> subsystems each time -- e.g. when I'm lucky and when the apps got only
>>> "partially" locked up, I can e.g. open new tabs in Google Chrome, I can
>>> see some thumbnails of my popular websites, but without their contents.
>>> This would suggest the networking subsystem is dead, but at the same
>>> time Chrome is apparently communicating fine with the X server in the
>>> DomU (and which in turn talks fine with Dom0 over Xen shared
>>> memory/evtchanl).
>>>
>>> I experienced the above behavior also when had only one VCPU er DomU.
>>>   
>>
>> I've seen similar things with just normal domain save/restore, where the
>> timer interrupt seems to be failing.  Can you ssh into the domain?  I
>> found that I couldn't do an interactive ssh (hung at the prompt), but a
>> non-interactive command would work, so I could cat /proc/interrupts.
> 
> Did either of you try disabling the setting of sched_clock_stable in
> arch/x86/kernel/cpu/intel.c:early_init_intel()? I found this to be a
> requirement in our pv kernels (though in connection with the use of
> C-states, not with S3).
> 
Before I try it -- can you explain what would be the theory behind it,
specifically how this would be related to HT? Clearly it is a HT
problem, and intuitively, I would expect this to be a Xen-side problem,
rather than DomU-side?

joanna.


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 226 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

  reply	other threads:[~2010-07-06  8:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-05 10:38 DomU lockups after resume from S3 on Core i5 processors Joanna Rutkowska
2010-07-05 21:28 ` Joanna Rutkowska
2010-07-05 22:07   ` Joanna Rutkowska
2010-07-05 22:43     ` Jeremy Fitzhardinge
2010-07-05 22:52       ` Joanna Rutkowska
2010-07-05 23:17         ` Jeremy Fitzhardinge
2010-07-06  8:41           ` Jan Beulich
2010-07-06  8:59             ` Joanna Rutkowska [this message]
2010-07-06  9:57               ` Jan Beulich
2010-07-08 14:04     ` Joanna Rutkowska

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=4C32F078.2080009@invisiblethingslab.com \
    --to=joanna@invisiblethingslab.com \
    --cc=JBeulich@novell.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    /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).