Xen project Mailing List

Re: [Xen-devel] cpu.c BUG, Xen or hardware failure?

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>

From: Thiago Camargo Martins Cordeiro <thiagocmartinsc@xxxxxxxxx>

Date: Sun, 30 Aug 2009 22:58:14 -0300

Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>

Delivery-date: Sun, 30 Aug 2009 18:58:44 -0700

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ix0gdAv3B6m3EWy130rdVqCJpAvS1IPPYgkLpAt2mhKaQdgaD/Au3hoR5Eub838zr9 HGmYRMtYO5nh0/7dQJ7xbIx6GjJv+bJnfLVbG80B6b/ilzLz2jn8hxZNt/R2M66Vmuiz e+OPcRAm/BkoKz5OE0YPn96ZLqbPOpmvshnSU=

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

2009/8/30 Keir Fraser <keir.fraser@xxxxxxxxxxxxx>

This may be fixed by linux-2.6.18-xen.hg:931. Give it a go.

-- Keir

On 29/08/2009 23:45, "Thiago Camargo Martins Cordeiro"

<thiagocmartinsc@xxxxxxxxx> wrote:

> Hi!
>
> Today one of my domU is showing the following message at the xvc0 console:
>
> BUG: warning at
> /home/administrativo/xen-3.3.2/linux-2.6.18-xen.hg/kernel/cpu.c:53/unlock_cpu_
> hotplug()
>
> Call Trace:
> [<ffffffff80248c7a>] unlock_cpu_hotplug+0x3f/0x6c
> [<ffffffff802295b2>] sched_getaffinity+0x7e/0x90
> [<ffffffff8024f281>] compat_sys_sched_getaffinity+0x1d/0x4a
> [<ffffffff8021ebda>] sysenter_do_call+0x1b/0x25
>
> BUG: warning at
> /home/administrativo/xen-3.3.2/linux-2.6.18-xen.hg/kernel/cpu.c:53/unlock_cpu_
> hotplug()
>
> Call Trace:
> [<ffffffff80248c7a>] unlock_cpu_hotplug+0x3f/0x6c
> [<ffffffff802295b2>] sched_getaffinity+0x7e/0x90
> [<ffffffff8024f281>] compat_sys_sched_getaffinity+0x1d/0x4a
> [<ffffffff8021ebda>] sysenter_do_call+0x1b/0x25
>
> This can be the root of some weird problems with the domU...
>
> This is a hardware failure or Xen BUG?!
>
> Thanks,
> Thiago
>

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