From owner-freebsd-net@FreeBSD.ORG Sun May 22 12:12:40 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CAA216A41C for ; Sun, 22 May 2005 12:12:40 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB41D43D54 for ; Sun, 22 May 2005 12:12:39 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87]) by mailout1.pacific.net.au (8.12.3/8.12.3/Debian-7.1) with ESMTP id j4MCCYrI007550; Sun, 22 May 2005 22:12:34 +1000 Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailproxy2.pacific.net.au (8.12.3/8.12.3/Debian-7.1) with ESMTP id j4MCCWMC006245; Sun, 22 May 2005 22:12:33 +1000 Date: Sun, 22 May 2005 22:12:33 +1000 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: Vaibhave Agarwal In-Reply-To: Message-ID: <20050522220248.D3215@epsplex.bde.org> References: <20050521031625.77340.qmail@web53907.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: npxintr from nowhere X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 May 2005 12:12:40 -0000 On Sun, 22 May 2005, Vaibhave Agarwal wrote: > I was writing some code at the ethernet layer, > mainly changing the if_ethersubr.c for my work. > > I am not using any FP instructions in my code. > But while running, my kernel crashes and gives the following panic msg: > npx is the Floating point unit (fpu). > > ---------------------------------- > npxintr: npxproc = 0 , currproc = 0, npx_exists = 1 > panic: npxintr from nowhere > --------------------------------- > ... > > Has anybody ever got such message or they know the fix for it. > I was not able to trace the error...even using kernel debug corefiles. If you have a system newer than a 486SX, then npx interrupts shouldn't be used for anything except to probe that not using them works. It is barely possible that a bug in turning off npx interrupts after the probe results in one being delivered much later (there have been bugs in this area). If it was a real npx interrupt, then the address of the FP instruction that caused it should be in the FPU state in the kernel dump. Bruce