From owner-freebsd-hackers Mon May 7 16:34:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id F0BB937B422 for ; Mon, 7 May 2001 16:34:39 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id BAA54025; Tue, 8 May 2001 01:34:28 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Valentin Nechayev Cc: Rohit Rakshe , freebsd-hackers@FreeBSD.ORG Subject: Re: FPU exception, kernel panic References: <20010507083206.A511@iv.nn.kiev.ua> From: Dag-Erling Smorgrav Date: 08 May 2001 01:34:27 +0200 In-Reply-To: <20010507083206.A511@iv.nn.kiev.ua> Message-ID: Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Valentin Nechayev writes: > (I cannot even guarantree 50% this is the same problem, but...) > There were some reports in current@ about incorrect usage of i586_bzero() > which uses FPU for zero-filling. It generated random kernel panics mainly > on K6-2, also on P5-MMX and similars. You can try to disable such bzero, > but IMHO it is reasonable to upgrade to 4.3-RELEASE (RELENG_4_3) first. 1) this bug only occurs on -CURRENT systems that have interrupt preemption enabled (i.e. anything newer than february) 2) the symptoms are nowhere near what's described here anyway - you'd see the kernel stack getting smashed, not an FPU exception. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message