From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <8b46cc686faa291fa66ad80de397dd8d@vitanuova.com> To: 9fans@cse.psu.edu Subject: Re: [9fans] SuperMicro P6DGU From: C H Forsyth Date: Wed, 10 Nov 2004 13:48:17 +0000 In-Reply-To: <48fa91a91dec3951895c5ab89a975502@quintile.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-ootmfwiexpktohloiaqgwlcjfq" Topicbox-Message-UUID: 0103163c-eace-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-ootmfwiexpktohloiaqgwlcjfq Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit i'd have said that was an old bug fixed by adding fpclear to l.s and main.c and that kernel is somehow out of date, unless there's a new manifestation. --upas-ootmfwiexpktohloiaqgwlcjfq Content-Type: message/rfc822 Content-Disposition: inline Received: from mail.cse.psu.edu ([130.203.4.6]) by doppio; Wed Nov 10 13:05:13 GMT 2004 Received: from psuvax1.cse.psu.edu (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 1FCAA63E7B for ; Wed, 10 Nov 2004 08:03:00 -0500 (EST) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: from localhost (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 1F91D63ED for <9fans@cse.psu.edu>; Wed, 10 Nov 2004 08:02:29 -0500 (EST) Received: from mail.cse.psu.edu ([127.0.0.1]) by localhost (psuvax1 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 04383-01-60 for <9fans@cse.psu.edu>; Wed, 10 Nov 2004 08:02:27 -0500 (EST) Received: from felix.quintile.net (cpc1-sout4-6-0-cust141.sot3.cable.ntl.com [81.96.207.141]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 6817C63C0 for <9fans@cse.psu.edu>; Wed, 10 Nov 2004 08:02:27 -0500 (EST) Message-ID: <48fa91a91dec3951895c5ab89a975502@quintile.net> From: "Steve Simon" Date: Wed, 10 Nov 2004 13:02:26 0000 To: 9fans@cse.psu.edu Subject: Re: [9fans] SuperMicro P6DGU MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at cse.psu.edu X-Spam-Status: No, hits=3.1 tagged_above=3.0 required=5.0 tests=FORGED_RCVD_HELO, INVALID_DATE, J_CHICKENPOX_13, RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL X-Spam-Level: *** X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces+forsyth=vitanuova.com@cse.psu.edu Errors-To: 9fans-bounces+forsyth=vitanuova.com@cse.psu.edu Ok, I understand a bit better now, I now have had 3 panics and two of them where prevoked. Both these times I just rebooted without halting - very early, just as fossil was comming up. Both times I got an fp overflow and a panic, when I rebooted again afterwards the system came up cleanly. panic (fp overflow) fppc=0x22aab status=0x80c1 pc=0x00022aa9 The problem seems to occur after fossil has checked a dirty filesystem. 0x22aa9 in fossil relates to /sys/src/libc/386/vlrt.c:105 which is _v2d(). Suffice to say my box seems happy now, I have one unexplained crash but I would be happy to put that down to a mains dropout. The above info might help somone else if this bites more severely. -Steve --upas-ootmfwiexpktohloiaqgwlcjfq--