From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Re: [xen-unstable test] 6413: regressions - FAIL Date: Tue, 15 Mar 2011 10:00:29 +0000 Message-ID: References: <4D7F45E40200007800036882@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4D7F45E40200007800036882@vpn.id2.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , Ian Jackson Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 15/03/2011 09:56, "Jan Beulich" wrote: >>>> On 15.03.11 at 10:47, "Jan Beulich" wrote: >>>>> On 14.03.11 at 18:22, Ian Jackson 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