 Home |
Products |
Support |
Community |
News |
xen-users
Re: [Xen-devel] cpu.c BUG, Xen or hardware failure?
| To: | Thiago Camargo Martins Cordeiro <thiagocmartinsc@xxxxxxxxx>, Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] cpu.c BUG, Xen or hardware failure? |
| From: | Keir Fraser <keir.fraser@xxxxxxxxxxxxx> |
| Date: | Sun, 30 Aug 2009 08:55:24 +0100 |
| Cc: | |
| Delivery-date: | Sun, 30 Aug 2009 00:55:56 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <6b7f6eb0908291545q1952e4a9u4f2bd3e93da5ffc9@xxxxxxxxxxxxxx> |
| 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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
| Thread-index: | Acoo+nBdoF0+9DSWSL2xyGjaFxF+8wATMp5D |
| Thread-topic: | [Xen-devel] cpu.c BUG, Xen or hardware failure? |
| User-agent: | Microsoft-Entourage/12.20.0.090605 |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] cpu.c BUG, Xen or hardware failure?, Thiago Camargo Martins Cordeiro |
|---|---|
| Next by Date: | [Xen-users] I/O Virtualization failure on d5400xs with iommu=1, c4pt |
| Previous by Thread: | [Xen-devel] cpu.c BUG, Xen or hardware failure?, Thiago Camargo Martins Cordeiro |
| Next by Thread: | Re: [Xen-devel] cpu.c BUG, Xen or hardware failure?, Thiago Camargo Martins Cordeiro |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
