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] Re: 2.6.29 git, resume from ram broken on thinkpad

To: "Rafael J. Wysocki" <rjw@xxxxxxx>
Subject: [Xen-devel] Re: 2.6.29 git, resume from ram broken on thinkpad
From: Ingo Molnar <mingo@xxxxxxx>
Date: Thu, 2 Apr 2009 23:04:51 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Arkadiusz Miskiewicz <a.miskiewicz@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Mike Travis <travis@xxxxxxx>, Chris Wright <chrisw@xxxxxxxxxxxx>, virtualization@xxxxxxxxxxxxxx, Yinghai Lu <yhlu.kernel@xxxxxxxxx>, KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx>, Venkatesh Pallipadi <venkatesh.pallipadi@xxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxxxxxxx>
Delivery-date: Thu, 02 Apr 2009 14:06:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200904022300.01707.rjw@xxxxxxx>
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>
References: <200904011155.20751.a.miskiewicz@xxxxxxxxx> <200904020023.58363.rjw@xxxxxxx> <20090401230637.GW18394@xxxxxxxxxxxxxxxxxxxx> <200904022300.01707.rjw@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
* Rafael J. Wysocki <rjw@xxxxxxx> wrote:

> On Thursday 02 April 2009, Chris Wright wrote:
> > * Rafael J. Wysocki (rjw@xxxxxxx) wrote:
> > > Sorry for the misunderstanding, I thought the breakage might be introduced
> > > between 15f7176eb1cccec0a332541285ee752b935c1c85 and
> > > 0a0c5168df270a50e3518e4f12bddb31f8f5f38f, so I thought it would be a good
> > > idea to verify if 0a0c5168df270a50e3518e4f12bddb31f8f5f38f fails too.
> > 
> > Ah, sure.  It fails too (both test_suspend=mem and regular suspend/resume).
> Having looked at the commit the Arek's bisect turned up I don't 
> think it's likely to have caused this problem to appear.
> It seems that the regression had been introduced before the PM and 
> PCI updates went it, so I bet it's one of the x86 changes.  Ingo, 
> are there any commits obviously worth testing?

i lost context - a list/range of commits to check would be nice.


Xen-devel mailing list

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