All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [xen-unstable test] 17595: tolerable FAIL
Date: Wed, 10 Apr 2013 10:26:02 +0100	[thread overview]
Message-ID: <5165302A.6000402@eu.citrix.com> (raw)
In-Reply-To: <51641B9002000078000CBBB6@nat28.tlf.novell.com>

On 09/04/13 12:45, Jan Beulich wrote:
>>>> On 09.04.13 at 11:58, xen.org <ian.jackson@eu.citrix.com> wrote:
>> flight 17595 xen-unstable real [real]
>> http://www.chiark.greenend.org.uk/~xensrcts/logs/17595/
>>
>> Failures :-/ but no regressions.
>>
>> Tests which are failing intermittently (not blocking):
>>   test-amd64-amd64-xl-sedf-pin  7 debian-install              fail pass in 17594
> Ian,
>
> with Keir's agreement I put in a debugging patch that I hope will
> help spotting why the mites once in a while experience a platform
> timer wrap followed by a hang.
>
> In order for the added code to be fully utilized, you would need
> to add "log_time=<big number>" to *-mite's hypervisor options,
> with <big number> being large enough to cover the longest time
> tests would run (including an eventual timeout). To be on the
> safe side, 0x7fffffff could be used (as the maximum sensible
> value).
>
> Of course, this is going to mildly spam the logs on those systems
> (output resulting from platform timer overflow handling and timer
> calibration code).
>
> Without any option added, some debugging code would
> nevertheless be active, and there is a chance that even in this
> mode the problem could be caught earlier and in a more explicit
> way. But with it happening relatively rarely, I'd prefer the full
> functionality to be enabled from the beginning.
>
> George,
>
> could you put on your 4.3 release requirements list the need to
> revert this debugging patch (commit bd9be94), so that in the
> event that I forget about it we have a way of being reminded
> collectively?

Good idea.

  -George

      reply	other threads:[~2013-04-10  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09  9:58 [xen-unstable test] 17595: tolerable FAIL xen.org
2013-04-09 11:45 ` Jan Beulich
2013-04-10  9:26   ` George Dunlap [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=5165302A.6000402@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.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.