From: Roderick Colenbrander <thunderbird2k@gmail.com>
To: Konrad Rzeszutek Wilk <konrad@darnok.org>
Cc: xen-devel@lists.xensource.com, Andreas Kinzler <ml-xen-devel@hfp.de>
Subject: Re: Questions about GPLPV stability tests
Date: Fri, 16 Dec 2011 02:25:25 +0000 [thread overview]
Message-ID: <CAEc3jaA8q1fLaH60MgtCtqMyUbE97cmtiERUFSOJsAY1HiK-ig@mail.gmail.com> (raw)
In-Reply-To: <20111213212031.GA8410@konrad-lan>
Thanks. On Tuesday I set up your monitoring tool on the already
running tests. Some of the systems were on the verge of showing
results, but we just had a power outage and I have to restart the
tests. It will probably take until the Holidays before there any
results :(
Roderick
On Tue, Dec 13, 2011 at 9:20 PM, Konrad Rzeszutek Wilk
<konrad@darnok.org> wrote:
>> > Does this feel like blktap issues? Or is it more likely that something
>> > else happened which causes blktap and the other things to fail?
>>
>> It looks like the interrupts stopped. Perhaps you can run the C code
>> (attached) on the serial console and see _what_ (or perhaps _when_)
>> the interrupts stops (and also verify that the timeouts and 'frozen'
>> happen due to no interrupts being received).
>
> The C code is http://darnok.org/xen/read_interrupts.c
>
>>
>> There are a couple of bugs that were discovered in the interrupt code
>> (that had been there since 2.6.27!) that went to the stable tree - so
>> they should been backported to 2.6.32.x tree - but I honestly don't
>> recall the names. I can look them up tomorrow.
>
> xen: x86_32: do not enable iterrupts when returning from exception in
> interrupt context (git commit d198d499148a0c64a41b3aba9e7dd43772832b91)
>
next prev parent reply other threads:[~2011-12-16 2:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEc3jaBds7xmiKH8RMfmEHQumkEeZ3PopVfbZPs_B-Kz8-DsWw@mail.gmail.com>
2011-11-29 17:12 ` Questions about GPLPV stability tests Andreas Kinzler
2011-11-29 18:04 ` Roderick Colenbrander
2011-11-29 18:15 ` Andreas Kinzler
2011-11-29 18:21 ` Roderick Colenbrander
2011-11-30 13:11 ` Andreas Kinzler
2011-11-29 23:02 ` Konrad Rzeszutek Wilk
2011-11-30 0:01 ` Roderick Colenbrander
2011-12-06 19:12 ` Roderick Colenbrander
2011-12-07 20:38 ` Konrad Rzeszutek Wilk
2011-12-07 20:44 ` Roderick Colenbrander
2011-12-08 23:46 ` Konrad Rzeszutek Wilk
2011-12-09 1:33 ` Roderick Colenbrander
2011-12-09 22:02 ` Roderick Colenbrander
2011-12-11 12:52 ` Pasi Kärkkäinen
2011-12-11 18:58 ` Roderick Colenbrander
2011-12-12 22:30 ` Roderick Colenbrander
2011-12-13 1:50 ` James Harper
2011-12-13 1:58 ` Roderick Colenbrander
2011-12-13 2:02 ` Konrad Rzeszutek Wilk
2011-12-13 21:20 ` Konrad Rzeszutek Wilk
2011-12-16 2:25 ` Roderick Colenbrander [this message]
2011-12-26 18:45 ` Roderick Colenbrander
2012-01-03 16:55 ` Konrad Rzeszutek Wilk
2012-01-04 23:37 ` Roderick Colenbrander
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=CAEc3jaA8q1fLaH60MgtCtqMyUbE97cmtiERUFSOJsAY1HiK-ig@mail.gmail.com \
--to=thunderbird2k@gmail.com \
--cc=konrad@darnok.org \
--cc=ml-xen-devel@hfp.de \
--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).