From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "aravindp@cisco.com" <aravindp@cisco.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"jbeulich@suse.com" <jbeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: e008:[<ffff82c480122353>] check_lock+0x1b/0x45
Date: Wed, 19 Jun 2013 13:01:39 -0400 [thread overview]
Message-ID: <20130619170139.GA13046@phenom.dumpdata.com> (raw)
In-Reply-To: <51C1DE2D.2010409@citrix.com>
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.
next prev parent reply other threads:[~2013-06-19 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 16:06 e008:[<ffff82c480122353>] check_lock+0x1b/0x45 [konrad.wilk@oracle.com: FAILURE 3.10.0-rc6upstream-00061-g752bf7d(x86_64) 3.10.0-rc6upstream-00061-g752bf7d(i386): 2013-06-19 (tst007)] Konrad Rzeszutek Wilk
2013-06-19 16:37 ` e008:[<ffff82c480122353>] check_lock+0x1b/0x45 Andrew Cooper
2013-06-19 17:01 ` Konrad Rzeszutek Wilk [this message]
2013-06-19 17:22 ` Andrew Cooper
2013-06-19 20:30 ` Konrad Rzeszutek Wilk
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=20130619170139.GA13046@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=aravindp@cisco.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.