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

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

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