From owner-freebsd-current Sun Dec 17 16:53:27 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA12692 for current-outgoing; Sun, 17 Dec 1995 16:53:27 -0800 (PST) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA12636 Sun, 17 Dec 1995 16:53:16 -0800 (PST) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id QAA11101; Sun, 17 Dec 1995 16:53:03 -0800 From: "Rodney W. Grimes" Message-Id: <199512180053.QAA11101@GndRsh.aac.dev.com> Subject: Re: FreeBSD-current-stable ??? To: phk@freefall.freebsd.org (Poul-Henning Kamp) Date: Sun, 17 Dec 1995 16:53:03 -0800 (PST) Cc: current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <19611.819233434@freefall.freebsd.org> from "Poul-Henning Kamp" at Dec 17, 95 12:50:34 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk ... > > I have had only one serious problem (2 core dumps apparently caused by > > some vm change in the last month). > > I have some bogons, but they are quite likely HW actually. (Don't worry > Rod, I just have not got around to flash the boot-patition correctly :-). When you do go to flash it, get the 112 version of the BIOS for the PCI/I-P55TP4XE board as I have qualified that here. Be sure to update both the BIOS and the bios boot-partition (requires you to move the MB jumper to enable write to the bios boot-code) and then clear the ESCD. One thing you might try without going to the newest BIOS is drop the PCI latency timer to 32 clocks, seems ASUS has found that this works best as the 80 clocks was just to long for some boards and causes some problems. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD