This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Xen suspend

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Xen suspend
From: Kurt Garloff <kurt@xxxxxxxxxx>
Date: Tue, 30 Nov 2004 10:46:44 +0100
Delivery-date: Tue, 30 Nov 2004 13:45:42 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Organization: SUSE/Novell
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i

I'm running Xen-2.0.1 and a self-compiled 2.6.9-xen0 on my IBM T40.

When I close the lid the following happens:
(a) running natively (a SL92 kernel, 2.6.9-rc2 with some improvements):
    The powersaved is configured to do a suspend-to-ram. The OS suspends
    the devices and goes to sleep. Waking up again, the devices get 
    reinitialized and everything Works like a charm.
    Only downside is the power consumption in suspended mode.
    It's still about 4W.
(b) Running Xen
    The laptop goes into suspend mode immediately.
    It also wakes up again.
    The OS does not seem involved in suspending at all. dmesg does not
    show any signs of this event not even xm dmesg does.
    After waking up, however, the touchpad (synaptics) in domain 0 is 
    unusable and the kernel spits
    TouchPad at isa0060/serio1/input0 lost sync at byte 1
    I'm unsure whether other devices are in a sane state.
    The next xm create killed the machine :-(

Is this supposed to work?
Shouldn't Xen ask the domain0 kernel to suspend the devices?

Kurt Garloff                   <kurt@xxxxxxxxxx>             [Koeln, DE]

Attachment: pgpfsrnZZu0aH.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>