From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Xen4.2 S3 regression?
Date: Thu, 6 Sep 2012 09:05:59 -0400
Message-ID: <20120906130559.GC22927@phenom.dumpdata.com>
References: <502BB8FD02000078000951E0@nat28.tlf.novell.com>
	<CAOvdn6VD6bp13F-tvYdkBsj4hkhE7PTGZrapndtdHrDKeZqccg@mail.gmail.com>
	<502CCC0002000078000955C4@nat28.tlf.novell.com>
	<CAOvdn6VEuX7R2_wz74ZvCxMjC-=YUir9kP5sdxEVaKVspRUd_w@mail.gmail.com>
	<502CF0A8020000780009574E@nat28.tlf.novell.com>
	<CAOvdn6VsZvn_1TCWYeuyY5YuTcP8=miK2KwE4583nsj6Qjb_vg@mail.gmail.com>
	<504494FB0200007800098398@nat28.tlf.novell.com>
	<CAOvdn6UT13qvWbMyfZkWND03RoVKVSgb6wW4yqTUpuBYEX01Dg@mail.gmail.com>
	<5048958D02000078000993EB@nat28.tlf.novell.com>
	<CAOvdn6WrNK1Jn_Y_P7C3AwX6ApVcgzacLA_x-u=xBQtebnuPxA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <CAOvdn6WrNK1Jn_Y_P7C3AwX6ApVcgzacLA_x-u=xBQtebnuPxA@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ben Guthro <ben@guthro.net>
Cc: Thomas Goetz <thomas.goetz@citrix.com>, john.baboval@citrix.com, Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

On Thu, Sep 06, 2012 at 07:48:26AM -0400, Ben Guthro wrote:
> Fantastic!
> 
> Initial tests are very good, with this dma_msi_ack modification.
> 
> I've been able to get past the ahci stall, and run through ~10 suspend
> / resume cycles with this fix.
> Additional tests are warranted, and I'll run through an automated
> sleep / wake script I have to make sure this fix holds over time.

How are you automating this? (/me imagines some robotic arm pressing
the power button every couple of minutes).