From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: devel/for-linus-3.14 branch: dom0 BUG: soft lockup - CPU#1 stuck for 22s! RIP: e030:[<ffffffff81109a58>] [<ffffffff81109a58>] generic_exec_single+0x88/0xc0 xen_destroy_contiguous_region+0x160/0x160
Date: Tue, 7 Jan 2014 09:43:55 -0500 [thread overview]
Message-ID: <20140107144355.GH3588@phenom.dumpdata.com> (raw)
In-Reply-To: <52CC08C2.5090004@citrix.com>
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
next prev parent reply other threads:[~2014-01-07 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 11:53 devel/for-linus-3.14 branch: dom0 BUG: soft lockup - CPU#1 stuck for 22s! RIP: e030:[<ffffffff81109a58>] [<ffffffff81109a58>] generic_exec_single+0x88/0xc0 xen_destroy_contiguous_region+0x160/0x160 Sander Eikelenboom
2014-01-07 14:01 ` David Vrabel
2014-01-07 14:43 ` Konrad Rzeszutek Wilk [this message]
2014-01-07 16:30 ` Sander Eikelenboom
2014-01-07 16:58 ` Konrad Rzeszutek Wilk
2014-01-07 17:24 ` Sander Eikelenboom
2014-01-07 18:21 ` Konrad Rzeszutek Wilk
2014-01-07 16:06 ` Sander Eikelenboom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140107144355.GH3588@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.