[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: [xen-unstable test] 6413: regressions - FAIL


  • To: George Dunlap <dunlapg@xxxxxxxxx>
  • From: Keir Fraser <keir.xen@xxxxxxxxx>
  • Date: Tue, 29 Mar 2011 16:30:18 +0100
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
  • Delivery-date: Tue, 29 Mar 2011 08:31:10 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=OzpIx+LaYolP9wB+F31EkV89psbsbNSjqJcpwYDOV6CfJwdcZ6sFIcyUTM5iq/cAby Gt3wmcGkkAmadLmQYf+PsER9yZ2XvBxym0mIw2doam5RILBhf+bXqewCS5Mrdl+VqhEn 72S3IIwYr/avrYLRWNcsJvbjU+IKRaRXvUNoM=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcvuJjVDl8wJMOLZ+k23upgnl91d9w==
  • Thread-topic: [Xen-devel] Re: [xen-unstable test] 6413: regressions - FAIL

Then it can't be due to 23033:84bacd as Jan thought, as 4.1 branch does not
have that changeset.

 -- Keir

On 29/03/2011 16:15, "George Dunlap" <dunlapg@xxxxxxxxx> wrote:

> Has there been a fix for this one?
> 
> I just did a pull of 4.1-release, and I'm getting this every couple of
> boots...
>  -George
> 
> On Tue, Mar 15, 2011 at 10:00 AM, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
>> On 15/03/2011 09:56, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
>> 
>>>>>> On 15.03.11 at 10:47, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
>>>>>>> On 14.03.11 at 18:22, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel
>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.