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

Re: [Xen-devel] VMX status report 12033:b21246720fde

To: "Li, Xin B" <xin.b.li@xxxxxxxxx>, "Yu, Ping Y" <ping.y.yu@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 01 Nov 2006 07:40:30 +0000
Delivery-date: Thu, 02 Nov 2006 13:54:32 -0800
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: Acb8nlQkpaZ430hoSVmzmsU4spEvlAAIcJHwADDwYgAAAUpUjA==
Thread-topic: [Xen-devel] VMX status report 12033:b21246720fde



On 1/11/06 7:09 am, "Li, Xin B" <xin.b.li@xxxxxxxxx> wrote:

> Hi Keir, this bug is caused by a dead spin lock in printk: printk will
> call __printk_ratelimit, but this guy may call printk again ( when lost
>> 0 ).
> After removing the call to printk in __printk_ratelimit, this bug is
> gone.

Thanks, I'll investigate the right fix.

 -- Keir



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

References:
- RE: [Xen-devel] VMX status report 12033:b21246720fde
  - From: Li, Xin B

Prev by Date: Re: [Xen-devel] [PATCH] Correct copy-n-paste error
Next by Date: RE: [Xen-devel] pfn to mfn mapping for HVM domains?
Previous by thread: RE: [Xen-devel] VMX status report 12033:b21246720fde
Next by thread: [Xen-users] Re: Fw: domU network problem , 10/30 progress
Index(es):
- Date
- Thread

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