WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] vmx status report against changeset 13826

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] vmx status report against changeset 13826
From: "Yu, Ping Y" <ping.y.yu@xxxxxxxxx>
Date: Fri, 9 Feb 2007 11:24:08 +0800
Delivery-date: Thu, 08 Feb 2007 19:23:53 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1F17F3F.923A%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdLUbF5zhYXkUEHTbudbOsozzXcWQADsSyAAAx/NfsAFQMKIAAApPBBAAA1M/UAA+ulMA==
Thread-topic: [Xen-devel] vmx status report against changeset 13826
Keir,

After re-test this c/s, and we found that this bug is gone now. Cheers!

-- Ping

>-----Original Message-----
>From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
>Sent: 2007年2月9日 9:31
>To: Keir Fraser; Yu, Ping Y; xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] vmx status report against changeset 13826
>
>Actually, given that this bug was introduced only a couple of weeks ago when
>we upgraded to Linxu 2.6.18, I'm almost certain that this bug will turn out
>to be fixed by changeset 13816.
>
> -- Keir
>
>On 9/2/07 01:24, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx> wrote:
>
>>
>> I'd be interested to know if this is reproducible with current tip of
>> xen-unstable. I checked in a modified form of Kevin Tian's softlockup patch
>> which fixes some spurious softlockup warnings.
>>
>>  -- Keir
>>
>> On 9/2/07 01:09, "Yu, Ping Y" <ping.y.yu@xxxxxxxxx> wrote:
>>
>>> Keir,
>>>
>>> I have opened a bug
>>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=878
>>> to
>>> track this issue, and we have some detail information for this bug there.
>>> Thanks
>>>
>>> -- Ping
>>>
>>>> -----Original Message-----
>>>> From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx]
>>>> Sent: 2007年2月8日 23:05
>>>> To: Yu, Ping Y; xen-devel@xxxxxxxxxxxxxxxxxxx
>>>> Subject: Re: [Xen-devel] vmx status report against changeset 13826
>>>>
>>>>
>>>>
>>>>
>>>> On 8/2/07 09:07, "Yu, Ping Y" <ping.y.yu@xxxxxxxxx> wrote:
>>>>
>>>>> 2) Call trace are printed continually in serial port(p2)
>>>>> A lot of call trace are printed in serial port, it exists in
>>>>> both PAE and IA32e Xen0, and I am afraid it also exists on IA32.
>>>>
>>>> Do you have an example to show us? Are they softlockup warnings?
>>>>
>>>> -- Keir
>>
>>
>>
>> _______________________________________________
>> 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