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-devel

[Xen-devel] FPU exception

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] FPU exception
From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Date: Tue, 4 Mar 2008 12:10:50 +0000
Delivery-date: Tue, 04 Mar 2008 04:12:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.12-2006-07-14
Hello,

I was trying to boot w98 when I got a BUG:

(XEN) Xen BUG at traps.c:2640                                                   
(XEN) ----[ Xen-3.3-unstable  x86_64  debug=n  Not tainted ]----                
(XEN) CPU:    0                                                                 
(XEN) RIP:    e008:[<ffff828c8017e343>] do_device_not_available+0x44/0xbc       
(XEN) RFLAGS: 0000000000010246   CONTEXT: hypervisor                            
(XEN) rax: 0000000000000000   rbx: ffff83007d40e080   rcx: 0000000000001be0     
(XEN) rdx: ffff828c8028ff28   rsi: 000000000000000a   rdi: ffff828c8028e348     
(XEN) rbp: ffff828c8028e338   rsp: ffff828c8028e318   r8:  ffff828c8028fe28     
(XEN) r9:  ffff828c801c52fe   r10: 000000000fff00b0   r11: ffff828c801c54e6     
(XEN) r12: 0000000000000000   r13: 0000000000000000   r14: 0000000000000000     
(XEN) r15: 0000000000000000   cr0: 000000008005003b   cr4: 00000000000026b0     
(XEN) cr3: 0000000079183000   cr2: 0000000000000000                             
(XEN) ds: 0000   es: 0000   fs: 0000   gs: 0000   ss: e010   cs: e008           
...
(XEN)    [<ffff828c8017e343>] do_device_not_available+0x44/0xbc                 
(XEN)    [<ffff828c801f95b5>] handle_exception_saved+0x2d/0x6b                  
(XEN)    [<ffff828c801c54e6>] realmode_emulate_cmpxchg+0x0/0x3b                 
(XEN)    [<ffff828c801c52fe>] realmode_emulate_insn_fetch+0x0/0xc3              
(XEN)    [<ffff828c8018ad77>] x86_emulate+0xa267/0x1348c                        

which is

    case 0x9b:  /* wait/fwait */
        __emulate_fpu_insn("fwait");
        break;

I guess we need to ensure that the FPU is setup before emulating FPU
instructions?

Samuel

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

<Prev in Thread] Current Thread [Next in Thread>