From: Shannon Zhao <zhaoshenglong@huawei.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, osstest-admin@xenproject.org
Subject: Re: [xen-unstable-smoke test] 85178: regressions - FAIL
Date: Thu, 3 Mar 2016 21:58:19 +0800 [thread overview]
Message-ID: <56D842FB.3090105@huawei.com> (raw)
In-Reply-To: <56D8422E.6070809@citrix.com>
On 2016/3/3 21:54, Andrew Cooper wrote:
> On 03/03/16 13:38, Shannon Zhao wrote:
>> >
>> > On 2016/3/3 20:53, Jan Beulich wrote:
>>>>>> >>>>> On 03.03.16 at 12:18, <osstest-admin@xenproject.org> wrote:
>>>>> >>>> flight 85178 xen-unstable-smoke real [real]
>>>>> >>>> http://logs.test-lab.xenproject.org/osstest/logs/85178/
>>>>> >>>>
>>>>> >>>> Regressions :-(
>>>>> >>>>
>>>>> >>>> Tests which did not succeed and are blocking,
>>>>> >>>> including tests which could not be run:
>>>>> >>>> test-armhf-armhf-xl 6 xen-boot fail REGR. vs. 85080
>>> >> Unless this is a spurious failure, would one of you please look into
>>> >> this? The complete lack of Xen messages in the log after the most
>>> >> recent host install may suggest that a boot attempt failed very
>>> >> early.
>> > Ah, sorry for this. I'm looking at this and have reproduced this.
>> >
>> > It fails with below log:
>> >
>> > (XEN) Xen call trace:
>> > (XEN) [<0000000000204f08>] dt_irq_translate+0x14/0x58 (PC)
>> > (XEN) [<0000000000205244>] dt_device_get_irq+0x2c/0x38 (LR)
>> > (XEN) [<0000000000205244>] dt_device_get_irq+0x2c/0x38
>> > (XEN) [<000000000024ab54>] platform_get_irq+0x14/0x44
>> > (XEN) [<000000000028f088>] preinit_xen_time+0x8c/0x120
>> > (XEN) [<000000000028ddc0>] start_xen+0x554/0xc8c
>> > (XEN) [<000000000020061c>] arm64/head.o#paging+0x84/0xbc
>> > (XEN)
>> > (XEN)
>> > (XEN) ****************************************
>> > (XEN) Panic on CPU 0:
>> > (XEN) Assertion 'dt_irq_xlate != NULL' failed at device_tree.c:1452
>> >
>> > I'm fixing this.
>> >
>> > BTW, if I fix this problem, do I need to update the original patch or
>> > send a new one?
> Smoke tests are run on top of what is already committed into staging.
> Please submit a new patch.
Ok, thanks a lot.
--
Shannon
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-03 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 11:18 [xen-unstable-smoke test] 85178: regressions - FAIL osstest service owner
2016-03-03 12:53 ` Jan Beulich
2016-03-03 13:38 ` Shannon Zhao
2016-03-03 13:54 ` Andrew Cooper
2016-03-03 13:58 ` Shannon Zhao [this message]
2016-03-03 13:56 ` Shannon Zhao
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=56D842FB.3090105@huawei.com \
--to=zhaoshenglong@huawei.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=osstest-admin@xenproject.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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.