From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Florath <xen@flonatel.org>
Subject: Re: Strange error in domU after dom0 update
Date: Tue, 27 Oct 2009 15:44:16 +0100
Message-ID: <20091027154416.n6j0pou4sg4kwg8g@webmail.flonatel.org>
References: <20091022094717.fk8pkqy6o80kgg0w@webmail.flonatel.org>
	<20091022110131.GO1434@reaktio.net>
	<20091022135508.4pwk6lslroc8oosc@webmail.flonatel.org>
	<4AE0C9E9.4010405@goop.org>
	<20091023132840.yd6yyujmck448sc8@webmail.flonatel.org>
	<20091023180154.j3n1ik6w0k8gkcco@webmail.flonatel.org>
Mime-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	DelSp="Yes";
	format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20091023180154.j3n1ik6w0k8gkcco@webmail.flonatel.org>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Andreas Florath <xen@flonatel.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, Xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Hello!

It seams that the root cause for this is a bug in the kernel 2.6.31.4  
pv_ops.  Tried a bisection and ended at version  
d2af313fcf20275d4008725f32f1974bde06ec9e, which is good, i.e. works  
without the described problems and  
9cf89da8cb207818c029975f261ea672addbb801 which is bad.

There are some other problems in version  
0148adde28789aa72f6210add9ac34625309535b which does even not boot, so  
it's somewhat tricky to do a bisection when there is more than one  
problem :-(

If it helps to find the bug, I can just try some other versions in  
between by random.

Note that the merge after the version which works for me  
(3dd81018a392941fcc722ee521de344527481eb8) changed things in the  
network layer.

Kind regards - Andreas