WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Debian 6.0 + Xen4.0 + FreeBSD hvm amd64 -> fpudna: fpcurthre

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Debian 6.0 + Xen4.0 + FreeBSD hvm amd64 -> fpudna: fpcurthread == curthread XXXX times
From: Sergi Seira <s.seira@xxxxxxxxx>
Date: Thu, 02 Jun 2011 10:24:03 +0200
Delivery-date: Thu, 02 Jun 2011 01:26:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100515 Lightning/1.0b1 Icedove/3.0.4
Hello,

I'm working with full virtual FreeBSD 8.2-RELEASE-p1 amd64 domU under debian
squeeze and xen-hypervisor-4.0-amd64.

If I cfg this hvm with cpu >  4 :

 vcpus    = 5

the server is blocked by these messages :

 fpudna: fpcurthread == curthread XXXX times

The machine is pingable but I'm unable to ssh to it.

On single user, freebsd works fine, fsck an so on ok, but when switching to
multiuser these fpudna messages start flooding.

I've googled but haven't found anything; something from 2005 about
fpudna :

http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004413.html

and this link, but I don't have the options he mentions enabled on the
kernel :

 http://forums.freebsd.org/showthread.php?t=17979

The machine really seems to detect cpu's available and responds to
keyboard on VNC, but it's impossible to see whats written down because of the
messages flooding the screen.

I've also asked freebsd-xen@xxxxxxxxxxx; I applied a suggestion from Mr. K. 
Belousov :

diff --git a/sys/amd64/amd64/fpu.c b/sys/amd64/amd64/fpu.c
index 08e5e57..a5ee853 100644
--- a/sys/amd64/amd64/fpu.c
+++ b/sys/amd64/amd64/fpu.c
@@ -394,14 +394,8 @@ fpudna(void)
      struct pcb *pcb;

      critical_enter();
-    if (PCPU_GET(fpcurthread) == curthread) {
-        printf("fpudna: fpcurthread == curthread %d times\n",
-            ++err_count);
-        stop_emulating();
-        critical_exit();
-        return;
-    }
-    if (PCPU_GET(fpcurthread) != NULL) {
+    if (PCPU_GET(fpcurthread) != NULL&&
+        PCPU_GET(fpcurthread) != curthread) {
          printf("fpudna: fpcurthread = %p (%d), curthread = %p (%d)\n",
                 PCPU_GET(fpcurthread),
                 PCPU_GET(fpcurthread)->td_proc->p_pid,

recompiled the kernel and got a 'kernel trap 22' with > 4 vcpus.

Has anyone stepped on this behavior before?
Is it freebsd related or xen related?
Is there any workaround?

Thanks for your help,
regards,
Sergi

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Debian 6.0 + Xen4.0 + FreeBSD hvm amd64 -> fpudna: fpcurthread == curthread XXXX times, Sergi Seira <=