From owner-freebsd-emulation@FreeBSD.ORG Tue May 6 20:02:54 2008 Return-Path: Delivered-To: freebsd-emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A2389106566B for ; Tue, 6 May 2008 20:02:54 +0000 (UTC) (envelope-from bsd@kuehlbox.de) Received: from samael.qmail-ldap.de (mail.kuehlbox.de [62.159.47.22]) by mx1.freebsd.org (Postfix) with ESMTP id 2DF658FC2C for ; Tue, 6 May 2008 20:02:53 +0000 (UTC) (envelope-from bsd@kuehlbox.de) Received: (qmail 25977 invoked from network); 6 May 2008 20:02:41 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlbox.de; b=ei5XaJmF6vo2exWEb6OYRVvg6dR/nSeQJNX40A5G/zMD3SLJHEsW2tSw8XEU7LxDdMQi57f+bnjAD3sz3RPuQBG9yewnAa9BBIeW3mAhtrUQ0XgRKSkItXAtu3pDeeIC ; Received: from unknown (HELO [192.168.200.128]) (bsd@kuehlbox.de@[10.0.48.22]) (envelope-sender ) by samael.qmail-ldap.de (qmail-ldap-1.03) with SMTP for ; 6 May 2008 20:02:41 -0000 Received: from: ppp-88-217-15-6.dynamic.mnet-online.de RECURED ([88.217.15.6]) by HSF smtp proxy with AES256-SHA encrypted SMTP Message-ID: <4820B954.7040603@kuehlbox.de> Date: Tue, 06 May 2008 22:02:28 +0200 From: Teufel User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Bakul Shah , freebsd-emulation@FreeBSD.org References: <20080506194800.876695B4C@mail.bitblocks.com> In-Reply-To: <20080506194800.876695B4C@mail.bitblocks.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: seems I finally found what upset kqemu on amd64 SMP... shared gdt! (please test patch :) X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2008 20:02:54 -0000 Bakul Shah wrote: >> at needs to be done to fix that? >> > > Comment it out in amd64/amd64/trap.c! > getting rid of the message, yes.. but without further issues?