From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.xen@gmail.com>
Subject: Re: Re: [xen-unstable test] 6413: regressions - FAIL
Date: Tue, 29 Mar 2011 16:30:18 +0100
Message-ID: <C9B7B99A.158FC%keir.xen@gmail.com>
References: <AANLkTim4vYE-sv6NSrGAouZkOy6B=OZmQjBgFf8r=d=D@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <AANLkTim4vYE-sv6NSrGAouZkOy6B=OZmQjBgFf8r=d=D@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: George Dunlap <dunlapg@umich.edu>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, Jan Beulich <JBeulich@novell.com>
List-Id: xen-devel@lists.xenproject.org

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@umich.edu> wrote:

> Has there been a fix for this one?
>=20
> I just did a pull of 4.1-release, and I'm getting this every couple of
> boots...
>  -George
>=20
> On Tue, Mar 15, 2011 at 10:00 AM, Keir Fraser <keir.xen@gmail.com> wrote:
>> On 15/03/2011 09:56, "Jan Beulich" <JBeulich@novell.com> wrote:
>>=20
>>>>>> 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:
>>>>>> =A0test-amd64-amd64-xl-win =A0 =A0 =A0 5 xen-boot =A0 =A0 =A0 =A0 =A0 =A0 =A0 fail REGR. v=
s.
>>>>>> 6396
>>>>>=20
>>>>> Xen boot crash. =A0Lots of these ...
>>>>=20
>>>> Yes, I can see my thinko is c/s 23033:84bacd800bf8 =A0(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.
>>>>=20
>>>> Jan
>>>>=20
>>>>> 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.
>>>=20
>>> But I hope these aren't related, as I can't see how any recent
>>> change could have broken the watchdog NMI setup logic.
>>=20
>> I think our NMI watchdog support is not working properly on all new CPUs=
,
>> and it's been that way for some time.
>>=20
>> =A0-- Keir
>>=20
>>> Jan
>>>=20
>>>=20
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>=20
>>=20
>>=20
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>>=20