From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: dump with xen-unstable & linux 3.2.17
Date: Tue, 22 May 2012 14:00:22 -0400
Message-ID: <20120522180022.GA22488@phenom.dumpdata.com>
References: <CAOvdn6V1xSRjWEMPG8Mo1qZUco2NQC-eLWOJ7paM4329tjkFfg@mail.gmail.com>
	<4FBA739A0200007800084DEE@nat28.tlf.novell.com>
	<CAOvdn6XGkvqcxfVH+eQ_o8WpDYAd3E+0Er9QHW1rCKL+Qibi0g@mail.gmail.com>
	<CAOvdn6XQq_MPhMTRRh0BSKuxEDWLSE22TqWO_bkSCNbrR9Vr9A@mail.gmail.com>
	<CAOvdn6Xz2Jh8uKKYxz_MZ_VxhuVJiSepkBz2KcVf3K3UBCPtXQ@mail.gmail.com>
	<4FBBD629020000780008538C@nat28.tlf.novell.com>
	<CAOvdn6UrJcmrKMJTUcuvwjKW_VqZnvWCJWsUfiSTR1eUWT4kiw@mail.gmail.com>
	<20120522173403.GD19601@phenom.dumpdata.com>
	<CAOvdn6XbSf70-9NQft6nyT7Mgt-azs1wfAeyCn=d1tabFkWSYQ@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: <CAOvdn6XbSf70-9NQft6nyT7Mgt-azs1wfAeyCn=d1tabFkWSYQ@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: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

On Tue, May 22, 2012 at 01:55:25PM -0400, Ben Guthro wrote:
> Are you referring to kernel, or Xen patches?

Xen.
> 
> I'm currently seeing the issue in question with the xen-unstable tip
> none of our patches pushed...

I pushed the serial ones.

> ...or are you suggesting that the patch, as committed is incorrect?

I just tried to suspend and resume Xen 4.1 with and without serial console
and it only works when there is no serial console.

I think something is buggy. Not sure what (this was with a normal
built-in motherboard serial port).