Xen project Mailing List

[Xen-devel] Re: BUG() in common/timer.c:cpu_callback()

From: Keir Fraser <keir@xxxxxxx>

Date: Sat, 08 Jan 2011 10:53:23 +0000

Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Yinghai Lu <yinghai@xxxxxxxxxx>

Delivery-date: Sat, 08 Jan 2011 02:54:25 -0800

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=ign56+zfGf/2kTg19ijpbLIZpW4c06D5gyExEDl680PuSaZ7i7bdeO3jYoXxCHRAUb VipUPqExuviR6bmVJZNkec5cgEm7hdhb4JQxVZ3z7/4eNPqrOj2FuEaB9BC0I2TPTxMw DuLY1Y/CEmJ+fAht8WgaLi/9Zv7JoIps0zYcQ=

List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Thread-index: AcuvIkToZAj7MEabF0G9+dSlIIOGUg==

Thread-topic: BUG() in common/timer.c:cpu_callback()

On 07/01/2011 12:57, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote: > Keir, > > shouldn't it only be the CPU_DEAD case where BUG() is called upon > migrate_timers_from_cpu() returning non-zero? That is, shouldn't > CPU_UP_CANCELED go together with CPU_DYING? From what I > can tell, that's the reason for a crash Yinghai is seeing on a large > system (there are other problems obviously, as CPU bringup > shouldn't fail in the first place - I hope we can hunt that down > soon). It was more complicated to fix than I remembered, but it's done now. -- Keir > Jan > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.