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


RE: [Xen-devel] ACPI suspend/resume on Dell Inspirons 1464/1564/1764

To: <roger.cruz@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] ACPI suspend/resume on Dell Inspirons 1464/1564/1764
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Wed, 19 May 2010 08:10:32 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 19 May 2010 00:12:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> "Roger Cruz"  05/19/10 12:39 AM >>>
>A little more info.  I am now able to wake up the Dell Inspiron 1764 after I 
>put it to sleep.  I found that the code commented out below would cause the 
>problems in my system.  I have yet to understand why these variables don't end 
>up with the expected values.  If anyone has any thoughts that they would like 
>to share on how this code works and why it is comparing to stored variables, I 
>would very much like to hear them.

The checks are done because code elsewhere expects that the capabilities found 
on individual CPUs are consistent across the whole system. If you found that 
one of these BUG_ON()s triggers, you can certainly also find out which one it 
is, and what the specific discrepancy is.


Xen-devel mailing list