From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@novell.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [xen-unstable test] 6413: regressions - FAIL
Date: Tue, 15 Mar 2011 10:00:29 +0000 [thread overview]
Message-ID: <C9A4E93D.14CE4%keir.xen@gmail.com> (raw)
In-Reply-To: <4D7F45E40200007800036882@vpn.id2.novell.com>
On 15/03/2011 09:56, "Jan Beulich" <JBeulich@novell.com> wrote:
>>>> On 15.03.11 at 10:47, "Jan Beulich" <JBeulich@novell.com> wrote:
>>>>> On 14.03.11 at 18:22, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
>>> Ian Jackson writes ("[xen-unstable test] 6413: regressions - FAIL"):
>>>> Tests which did not succeed and are blocking:
>>>> test-amd64-amd64-xl-win 5 xen-boot fail REGR. vs. 6396
>>>
>>> Xen boot crash. Lots of these ...
>>
>> Yes, I can see my thinko is c/s 23033:84bacd800bf8 (too bad all
>> my test systems either have ARAT or no MSI support in their HPETs).
>> I'm sorry for that and will send a fix soon.
>>
>> Jan
>>
>>> Mar 13 23:29:31.091587 (XEN) Brought up 8 CPUs
>>> Mar 13 23:29:31.205401 (XEN) Testing NMI watchdog --- CPU#0 okay. CPU#1
>>> stuck.
>>> CPU#2 stuck. CPU#3 stuck. CPU#4 stuck. CPU#5 stuck. CPU#6 s
>>> tuck. CPU#7 stuck.
>
> But I hope these aren't related, as I can't see how any recent
> change could have broken the watchdog NMI setup logic.
I think our NMI watchdog support is not working properly on all new CPUs,
and it's been that way for some time.
-- Keir
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-03-15 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 1:59 [xen-unstable test] 6413: regressions - FAIL xen.org
2011-03-14 17:22 ` Ian Jackson
2011-03-14 17:34 ` Keir Fraser
2011-03-15 9:47 ` Jan Beulich
2011-03-15 9:56 ` Jan Beulich
2011-03-15 10:00 ` Keir Fraser [this message]
2011-03-29 15:15 ` George Dunlap
2011-03-29 15:30 ` Keir Fraser
2011-03-29 16:11 ` Jan Beulich
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=C9A4E93D.14CE4%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@novell.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 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).