xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Julien Grall <julien.grall@arm.com>
Cc: xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>,
	Steve Capper <Steve.Capper@arm.com>,
	Andre Przywara <andre.przywara@arm.com>,
	osstest service owner <osstest-admin@xenproject.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Wei Chen <Wei.Chen@linaro.org>
Subject: Re: [xen-unstable test] 97737: regressions - FAIL
Date: Tue, 26 Jul 2016 11:05:08 +0100	[thread overview]
Message-ID: <20160726100508.GE27082@citrix.com> (raw)
In-Reply-To: <66b3169b-535a-2542-8e72-511515eef7cf@arm.com>

On Tue, Jul 26, 2016 at 10:52:13AM +0100, Julien Grall wrote:
> 
> 
> On 25/07/16 12:53, Wei Liu wrote:
> >On Mon, Jul 25, 2016 at 12:34:53PM +0100, Julien Grall wrote:
> >>
> >>
> >>On 25/07/16 12:11, Wei Liu wrote:
> >>>Thanks for investigating.
> >>>
> >>>There are only two arm related changes in the range being tested:
> >>>
> >>>* a43cc8f - (origin/smoke) arm/traps: fix bug in dump_guest_s1_walk handling of level 2 page tables (5 days ago) <Jonathan Daugherty>
> >>>* 60e06f2 - arm/traps: fix bug in dump_guest_s1_walk L1 page table offset computation (5 days ago) <Jonathan Daugherty>
> >>>
> >>>They don't look very suspicious.
> >>
> >>The modified function is not called in the hypervisor at all. It's only here
> >>for manual debugging.
> >>
> >>Although, this may change the offset of some function (assuming we have an
> >>hidden bug).
> >>
> >>>If you need help navigating osstest test report, please let me know.
> >>
> >>I have noticed that there is 2 kernel BUG in the logs (with one host reboot
> >>in the middle). Can you detail what the exact the test?
> >
> >What I normally do is to look at the summary page of the failed test to
> >identify the failed step and the time.
> >
> >In this case:
> >
> >http://logs.test-lab.xenproject.org/osstest/logs/97737/test-armhf-armhf-xl/info.html
> >
> >The time stamp said the failed step started at 2016-07-21 19:30:10 Z,
> >and then I look at the output of failed step log to look for time stamp
> >that the test failed.  Then I would look for output between these two
> >time stamps in various log.
> >
> >I now realise the log I pasted in was not from the failed test. I wanted
> >to paste in the second kernel oops, which should be the culprit that
> >the test failed. The two oops was the same one, though.
> >
> >To identify  which test step was running when the first oops happened,
> >the same technique applies.
> >
> >It seems that the oops happened during ts-debian-install according to
> >time stamps.
> 
> I looked at the new xen-unstable report [1], test-armhf-armhf-xl is passing
> (though it is on arndale and not a cubietruck).
> 
> Is there any way to re-run the previous test on the cubietruck? Just to
> confirm the bug is reproducable.
> 

This

http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/xen-unstable

The history of that test case on xen-unstable branch.

> Regards,
> 
> [1] http://logs.test-lab.xenproject.org/osstest/logs/99605/
> 
> -- 
> Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2016-07-26 10:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22  3:27 [xen-unstable test] 97737: regressions - FAIL osstest service owner
2016-07-22 10:49 ` Wei Liu
2016-07-22 12:10   ` Dario Faggioli
2016-07-25  8:53 ` Wei Liu
2016-07-25 11:05   ` Julien Grall
2016-07-25 11:11     ` Wei Liu
2016-07-25 11:34       ` Julien Grall
2016-07-25 11:53         ` Wei Liu
2016-07-26  9:52           ` Julien Grall
2016-07-26 10:05             ` Wei Liu [this message]

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=20160726100508.GE27082@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=Steve.Capper@arm.com \
    --cc=Wei.Chen@linaro.org \
    --cc=andre.przywara@arm.com \
    --cc=julien.grall@arm.com \
    --cc=osstest-admin@xenproject.org \
    --cc=sstabellini@kernel.org \
    --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).