From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [linux-linus test] 17376: regressions - FAIL
Date: Fri, 22 Mar 2013 20:31:17 +0000 [thread overview]
Message-ID: <514CBF95.3030406@citrix.com> (raw)
In-Reply-To: <20130322201725.GC6189@phenom.dumpdata.com>
On 22/03/13 20:17, Konrad Rzeszutek Wilk wrote:
> On Fri, Mar 22, 2013 at 07:23:48PM +0000, xen.org wrote:
>> flight 17376 linux-linus real [real]
>> http://www.chiark.greenend.org.uk/~xensrcts/logs/17376/
>>
>> Regressions :-(
> So.. looking at it:
>
>
> [ 260.914218] CE: Reprogramming failure. Giving up
> [ 260.914218] CE: Reprogramming failure. Giving up
> [ 260.914218] PM: noirq restore of devices complete after 0.025 msecs
> [ 260.914218] PM: early restore of devices complete after 0.009 msecs
> [ 261.033132] PM: restore of devices complete after 98.510 msecs
> [ 261.033187] CE: Reprogramming failure. Giving up
> [ 261.056750] Setting capacity to 8388608
> [ 261.069104] Setting capacity to 2048000
>
> INIT: Switching to runlevel: 0
>
> INIT: Sending processes the TERM signal
>
> [ 523.220878]
> vcpu 0
> 0: masked=0 pending=0 event_sel 00000000
>
> pending:
>
> ...
> and
> http://www.chiark.greenend.org.uk/~xensrcts/logs/17376/test-amd64-i386-xl/bush-cricket-output-%23usr%23lib%23xen%23bin%23xenctx_15_0
> tells us that it is stuck at
> <c10023a7>] <--
> [<c1051002>]
> [<c18e5fd0>]
> [<c7013000>]
> [<c1050ff0>]
> [<c1883f04>]
> [<c1061c44>]
> [<c18e5fd0>]
> [<c7013000>]
> [<c189a158>]
> [<c1883f10>]
> [<c1061506>]
> [<c19353c0>]
> [<c1883f18>]
> [<c167a258>]
> [<c1883f38>]
> [<c18edbc9>]
> [<ffffffff>]
> [<ffffffff>]
> [<c18ed6e3>]
> [<c19353c0>]
> [<c1883f44>]
> [<c18ed369>]
> [<c189a158>]
> [<c1883ffc>]
> [<c18f0e88>]
> [<c1883fe8>]
> [<c7013000>]
>
> Any chance of making xenctx use the System.map of the guest?
>From the log:
cs:eip: 0061:c10023a7
flags: 00001246 i z p
ss:esp: 0069:c1883ee0
eax: 00000000 ebx: deadbeef ecx: deadbeef edx: 00000000
esi: c7013000 edi: c1050ff0 ebp: c1883ef0
ds: 007b es: 007b fs: 00d8 gs: 0000
Code (instr addr c10023a7)
cc cc cc cc cc cc cc cc cc cc cc cc cc cc b8 1d 00 00 00 cd 82 <c3> cc cc cc cc cc cc cc cc cc cc
Stack:
c1051002 c18e5fd0 c7013000 c1050ff0 c1883f04 c1061c44 c18e5fd0 c7013000
c189a158 c1883f10 c1061506 c19353c0 c1883f18 c167a258 c1883f38 c18edbc9
00000163 ffffffff ffffffff c18ed6e3 c19353c0 01c8f000 c1883f44 c18ed369
c189a158 c1883ffc c18f0e88 c1883fe8 00000000 00000000 00000000 00000000
Call Trace:
[<c10023a7>] <--
With my work on the xen-crashdump-analyser, I have come across a few
instances like this.
Call trace is in a SCHEDOP_yield hypercall
~Andrew
next prev parent reply other threads:[~2013-03-22 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 19:23 [linux-linus test] 17376: regressions - FAIL xen.org
2013-03-22 20:17 ` Konrad Rzeszutek Wilk
2013-03-22 20:31 ` Andrew Cooper [this message]
2013-03-27 15:02 ` Ian Jackson
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=514CBF95.3030406@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=konrad.wilk@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).