From owner-freebsd-current@FreeBSD.ORG Sat Jun 19 11:26:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF88416A4CE for ; Sat, 19 Jun 2004 11:26:18 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A83243D2D for ; Sat, 19 Jun 2004 11:26:18 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.12.11/8.12.11) with ESMTP id i5JBQE26095955 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 19 Jun 2004 13:26:14 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.12.11/8.12.5/Submit) id i5JBQEtR095954 for current@freebsd.org; Sat, 19 Jun 2004 13:26:14 +0200 (CEST) Date: Sat, 19 Jun 2004 13:26:14 +0200 From: Divacky Roman To: current@freebsd.org Message-ID: <20040619112614.GB94870@stud.fit.vutbr.cz> References: <20040618104954.GA63085@stud.fit.vutbr.cz> <20040618101433.H36931@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040618101433.H36931@carver.gumbysoft.com> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Subject: Re: strange message appearing in a fresh current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jun 2004 11:26:18 -0000 On Fri, Jun 18, 2004 at 10:16:07AM -0700, Doug White wrote: > On Fri, 18 Jun 2004, Divacky Roman wrote: > > > > > kernel trap 22 with interrupts disabled > > npxdna: fpcurthread == curthread 1 times > > > > I am getting this quite often (uptime is about 2 minutes and I've got it > > at least 3 times) > > Are you compiling with CPU_ENABLE_SSE? I dont set anything from CPU_* > Also try backing out rev 1.151 of src/sys/i386/isa/npx.c. Its possible > its just noticing another bug somewhere... will try on monday (its my workstation in my job). btw: this occured exactly on fridays current, thursday was ok