From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tomasz Wroblewski <tomasz.wroblewski@citrix.com>
Subject: Re: [PATCH] Fix scheduler crash after s3 resume
Date: Wed, 23 Jan 2013 18:01:19 +0100
Message-ID: <5100175F.4030304@citrix.com>
References: <5100070F.7010808@citrix.com>
	<510019B302000078000B8C7E@nat28.tlf.novell.com>
	<5100165D.7020109@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <5100165D.7020109@citrix.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: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>, Juergen Gross <juergen.gross@ts.fujitsu.com>, "Keir (Xen.org)" <keir@xen.org>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

Aha, also don't be offended by the stacktraces attached having a serial 
port activity in the trace, I had to get them by hooking the most of xen 
suspend logic (without actual do_lowlevel_suspend) onto a debug key 
instead of using real s3 - since I can't otherwise get resume serial 
trace on this laptop, which uses pci serial card. But I did test the 
resulting patch against real s3 cycle.