From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: devel/for-linus-3.14 branch: dom0 BUG: soft lockup - CPU#1 stuck for 22s! RIP: e030:[] [] generic_exec_single+0x88/0xc0 xen_destroy_contiguous_region+0x160/0x160 Date: Tue, 7 Jan 2014 09:43:55 -0500 Message-ID: <20140107144355.GH3588@phenom.dumpdata.com> References: <1536712177.20140107125352@eikelenboom.it> <52CC08C2.5090004@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: <52CC08C2.5090004@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: David Vrabel Cc: Sander Eikelenboom , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Tue, Jan 07, 2014 at 02:01:38PM +0000, David Vrabel wrote: > On 07/01/14 11:53, Sander Eikelenboom wrote: > > Hi Konrad, > > > > A new year and a new linux merge window looming, so i thought i would try out the "devel/for-linus-3.14" branch. > > But dom0 seems to blow up for me .. (without this branch pulled it works ok) Hot damm! Thank you for testing so quickly! > > > > Xen: latest xen-unstable > > The FIFO-based event channel ABI is broken in current xen-unstable. > > You need the two patches from: > > http://lists.xen.org/archives/html/xen-devel/2013-12/msg01458.html > > You can also disable the use the FIFO ABI by the guest using the > xen.fifo_events = 0 kernel command line option. > > David