From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: e008:[] check_lock+0x1b/0x45 Date: Wed, 19 Jun 2013 13:01:39 -0400 Message-ID: <20130619170139.GA13046@phenom.dumpdata.com> References: <20130619160622.GA11787@phenom.dumpdata.com> <51C1DE2D.2010409@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <51C1DE2D.2010409@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper Cc: "aravindp@cisco.com" , "xen-devel@lists.xensource.com" , "jbeulich@suse.com" , Roger Pau Monne List-Id: xen-devel@lists.xenproject.org On Wed, Jun 19, 2013 at 05:37:01PM +0100, Andrew Cooper wrote: > On 19/06/13 17:06, Konrad Rzeszutek Wilk wrote: > > Hey, > > > > It looks like one of the patches that went in Xen 4.1 blows up. > > > > This used to work over the weekend, so I can only surmise > > it is one the three patches. This is with a debug=y build > > (which has been working nicely for the last month or more). > > > > It looks like one of the patches that went in Xen 4.1 blows up. > > > > This used to work a day ago - that is c/s 23551 worked nicely. And just to confirm, yes the same kernel but with cs 23551 boots (just built it). Let me narrow down which of the c/s is at fault.