From owner-freebsd-stable Wed Mar 29 7:47:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from TK147108.tuwien.teleweb.at (TK147108.tuwien.teleweb.at [195.34.147.108]) by hub.freebsd.org (Postfix) with ESMTP id 61E7A37B6D0 for ; Wed, 29 Mar 2000 07:47:46 -0800 (PST) (envelope-from satyr@TK147108.tuwien.teleweb.at) Received: from satyr by TK147108.tuwien.teleweb.at with local (Exim 2.12 #1) id 12aKjb-0002FN-00 for freebsd-stable@freebsd.org; Wed, 29 Mar 2000 17:50:19 +0200 Date: Wed, 29 Mar 2000 17:50:18 +0200 From: "Marinos J . Yannikos" To: freebsd-stable@freebsd.org Subject: 3.4-RELEASE; panic while paging Message-ID: <20000329175018.V15889@TK147108.telekabel.at> Reply-To: nino@inode.at Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am using 3.4-RELEASE (no patches) on an Athlon 600 / FIC SD11 system. So far I have experienced: - 1 spontaneous reboot - several sig 10/sig 11 errors while compiling the kernel - 2 kernel panics while paging, the message was "supervisor read - page not present, IIRC". Apparently the kernel ran out of swap, but I doubt that this was the only reason. 3.4-RELEASE seems rock-stable on my K6-3/400 system. Does anyone use the above configuration without problems? I am using very conservative SDRAM timings and brand 6ns PC100 SDRAM. Could this be a sign of a bad power supply, or do these things happen with 3.4-RELEASE because of a bug? Thanks, -mjy -- ***==> Marinos J. Yannikos ***==> http://pobox.com/~mjy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message