From owner-freebsd-hackers Thu Dec 11 18:03:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA04536 for hackers-outgoing; Thu, 11 Dec 1997 18:03:39 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA04509 for ; Thu, 11 Dec 1997 18:03:17 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id MAA00288; Fri, 12 Dec 1997 12:13:18 +1030 (CST) Message-Id: <199712120143.MAA00288@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: John-Mark Gurney cc: Mike Smith , ETX-B-SL Martti Kuparinen , freebsd-hackers@FreeBSD.ORG Subject: Re: panic: npxintr from nowhere In-reply-to: Your message of "Thu, 11 Dec 1997 17:30:46 -0800." <19971211173046.63648@hydrogen.nike.efn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Dec 1997 12:13:18 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 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... Hmm, interesting. I would guess that this means that you shouldn't run floating point code in the kernel. Think about it for a moment; to whom would you deliver a floating-point exception? It probably fails because the FPU initialisation is lazy, and if you haven't initialised it before you use it, you'll die screaming. mike