DomU lockups after resume from S3 on Core i5 processors

[Joanna Rutkowska <joanna@invisiblethingslab.com>]

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

I'm experiencing very reproducible DomU lockups that occur after I
resume the system from an S3 sleep. Strangely this seem to happen only
on my Core i5 systems (tested on two different machines), but not on
older Core 2 Duo systems.

Usually this causes the apps (e.g. Firefox) running in DomUs to become
unresponsive, but sometimes I see that some very limited functionality
of the app is still available (e.g. I can open/close Tabs in Firefox,
but cannot do much anything more). Also, when I log in to the DomU via
xm console, I usually can see the login prompt, can enter the username,
but then the console hangs.

I tried to attach to such a hanged DomU using gdbserver-xen, but when I
subsequently try to attach to the server from gdb (via the target
127.0.0.1:9999 command), my gdb segfaults (how funny!).

I'm running Xen 3.4.3, and fairly recent pvops0 kernel in DomU. In Dom0
I run 2.6.34-xenlinux kernel (opensuse patches), but I doubt it is
relevant in any way.

This seems like a scheduling problem, and, because it seems to affect
Core i5 processors, but not Core 2 Duos, it might have something to do
with Hyperthreading perhaps?

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