From owner-freebsd-hackers Thu Dec 11 17:31:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA01992 for hackers-outgoing; Thu, 11 Dec 1997 17:31:18 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA01975 for ; Thu, 11 Dec 1997 17:31:02 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.7/8.8.7) id RAA25144; Thu, 11 Dec 1997 17:30:46 -0800 (PST) Message-ID: <19971211173046.63648@hydrogen.nike.efn.org> Date: Thu, 11 Dec 1997 17:30:46 -0800 From: John-Mark Gurney To: Mike Smith Cc: ETX-B-SL Martti Kuparinen , freebsd-hackers@FreeBSD.ORG Subject: Re: panic: npxintr from nowhere References: <199712111644.RAA00495@kk662.kk.etx.ericsson.se> <199712112247.JAA01956@word.smith.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199712112247.JAA01956@word.smith.net.au>; from Mike Smith on Fri, Dec 12, 1997 at 09:17:07AM +1030 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mike Smith scribbled this message on Dec 12: > > What does this message mean, i.e. what's this npxintr thing? > > It's the interrupt handler for interrupts from the FPU. > > > Position 1 > > npxintr: npxproc = 0x0, curproc = 0x0, npx_exists = 1 > > panic: npxintr from nowhere > > > > Why does it crash when/before executing the function? Memory leak > > somewhere? ``netstat -m'' does not show any leak during execution. > > > > Corrupted instruction pointer? Why does it "find" the first > > printf line? > > npxintr() is being called without a valid NPX interrupt status. Are > you calling any functions indirectly? actually, now that someone else brought it up, any good way to call floating point routins from the kernel? if you do, and don't have any processes that have used floating point, will will get the above mentioned panic... quite easy to reproduce... boot kernel, run floating point code in kernel, see it panic... now boot same kernel, run systat, run floating point code in kernel, see it run normally.. :) this was from a current kernel as of a few weeks ago... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD