From owner-freebsd-ports@FreeBSD.ORG Wed Apr 11 15:23:00 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 454F716A402; Wed, 11 Apr 2007 15:23:00 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from gateway.cybervisiontech.com.ua (gateway.cybervisiontech.com.ua [88.81.251.18]) by mx1.freebsd.org (Postfix) with ESMTP id 078B413C455; Wed, 11 Apr 2007 15:22:59 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (hq.cybervisiontech.com [127.0.0.1]) by gateway.cybervisiontech.com.ua (Postfix) with ESMTP id 96133ED4823; Wed, 11 Apr 2007 18:22:53 +0300 (EEST) X-Virus-Scanned: amavisd-new at cybervisiontech.com Received: from gateway.cybervisiontech.com.ua ([127.0.0.1]) by localhost (hq.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xHPomhG3Et6j; Wed, 11 Apr 2007 18:22:46 +0300 (EEST) Received: from [10.2.1.87] (rein.cybervisiontech.com.ua [10.2.1.87]) by gateway.cybervisiontech.com.ua (Postfix) with ESMTP id D2C73ED4812; Wed, 11 Apr 2007 18:22:46 +0300 (EEST) Message-ID: <461CFD4B.4020801@icyb.net.ua> Date: Wed, 11 Apr 2007 18:22:51 +0300 From: Andriy Gapon User-Agent: Thunderbird 1.5.0.10 (X11/20070329) MIME-Version: 1.0 To: freebsd-emulation@freebsd.org, Juergen Lock Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: kqemu+amd64: fpudna in kernel mode X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2007 15:23:00 -0000 I get swarms of messages "fpudna in kernel mode" in system log when I run qemu with kqemu on FreeBSD 6.2 amd64 host with Windows XP 32-bit guest. I noticed that someone reported this problem a while ago: http://lists.freebsd.org/pipermail/freebsd-emulation/2006-February/001800.html There is no harm done, but the messages are annoying and they might be indicative of some bigger issue. Note that I am running qemu like follows: $ qemu-system-x86_64 ... -m 512 -net tap -net nic -localtime there is no -kernel-kqemu option and "info kqemu" in qemu monitor says that it is enabled for user code. As I understand "fpudna" means "FPU device not available" and the message comes from here: http://fxr.watson.org/fxr/source/amd64/amd64/trap.c on T_DNA ("device not avaialble") _kernel_ fault. BTW, not complaining about the following, but I think I should report it. When I use -kernel-kqemu option I get random crashes of the guest XP (BSOD) with diagnostics like the following (they vary): IRQL_NOT_GREATER_OR_EQUAL PFN_LIST_CORRUPT PAGE_FAULT_IN_NONPAGED_AREA Looks like all three are caused by some sort of memory corruption or driver misbehavior according to the following: http://aumha.org/a/stop.htm -- Andriy Gapon