All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	xen-devel@lists.xensource.com, ian.jackson@eu.citrix.com
Subject: Re: [xen-unstable test] 59040: regressions - FAIL
Date: Mon, 6 Jul 2015 16:05:38 +0200	[thread overview]
Message-ID: <1436191538.14347.110.camel@citrix.com> (raw)
In-Reply-To: <1436186029.25646.65.camel@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1946 bytes --]

On Mon, 2015-07-06 at 13:33 +0100, Ian Campbell wrote:
> On Fri, 2015-07-03 at 21:59 +0000, osstest service owner wrote:

> >  test-armhf-armhf-xl-credit2  15 guest-start/debian.repeat fail REGR. vs. 58965
> 
> From
> http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl-credit2/xen-unstable.html it appears this one is sporadically unreliable on cubietruck, but works just fine on arndale.
> 
> Comparing to
> http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/xen-unstable.html 
> it looks to be credit2 specific.
> 
Yes, noted... I shall have a look.

From what I recall, failures varies a bit, in terms of what the state of
the system (vcpus active/idle, etc.) when the fail itself happens.

If I'm not confusing this with something else, I've seen instances where
everything was completely idle and instances, like this one, where there
is something going on... As I said, I'll have a look.

> d8v0 has a PC at 0xffff000c, which will be the entry point for the
> prefetch abort handler. ABT_LR shows it came from 0xffff0010 which is
> the data abt handler, which uses the same banked LR as prefetch abt so
> we don't know where it came from.
> 
> SVR_LR shows that the last function call done in kernel mode was a call
> to fdt_check_header from early_init_dt_verify, but that might have been
> ages ago.
> 
Thanks for this. My nonexistent knowledge of ARM internals limits by
quite a bit the amount of information that I can extract from this
trace... but this is already something.

I'll ask if there is anything that is ARM specific that I need but can't
figure out.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

      parent reply	other threads:[~2015-07-06 14:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 21:59 [xen-unstable test] 59040: regressions - FAIL osstest service owner
2015-07-06 12:33 ` Ian Campbell
2015-07-06 12:47   ` Ian Jackson
2015-07-06 12:57     ` Ian Campbell
2015-07-06 13:23       ` Wei Liu
2015-07-06 13:37         ` Ian Campbell
2015-07-06 13:52           ` Wei Liu
2015-07-06 14:05   ` Dario Faggioli [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=1436191538.14347.110.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=wei.liu2@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.