From owner-freebsd-current Mon Nov 6 11:04:11 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA09162 for current-outgoing; Mon, 6 Nov 1995 11:04:11 -0800 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA09154 for ; Mon, 6 Nov 1995 11:04:01 -0800 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id LAA13281; Mon, 6 Nov 1995 11:03:41 -0800 From: "Rodney W. Grimes" Message-Id: <199511061903.LAA13281@GndRsh.aac.dev.com> Subject: Re: vnode_pager_outpages error To: smace@metal.ops.neosoft.com (Scott Mace) Date: Mon, 6 Nov 1995 11:03:41 -0800 (PST) Cc: current@freebsd.org In-Reply-To: <199511060338.VAA10499@metal.ops.neosoft.com> from "Scott Mace" at Nov 5, 95 09:38:21 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1481 Sender: owner-current@freebsd.org Precedence: bulk > > > You can _not_ put a 66mhz CPU in that board, and before swapping CPU chips > > simply clock your 100Mhz chip down at 90 (change external clock from 66 to > > 60Mhz). > > I clocked my 100mhz cpu down to 90mhz as you suggested above, and I've gotten > through 4 rebuilds of gcc with no signal 11's. I did this with 60ns simms > with chip count < 24 these SIMMs were standard non-edo modules. I will try > later with the EDO modules I have. Does this point to a bad cache module? It points to a timing problem most often either the cache has a slow chip in it, or your memory is not really performing at the 60nS speed. It can also be caused by a wrong voltage setting for the CPU chip (there is a five digit code ``SXxxx'' stamped on the top and bottom of your CPU chip, get that to me and I will tell you the correct setting for the CPU voltage). > > Phk just flashed his machine up to that revision and is now seeing soft > > (C-A-D) reboot problems, any such things going on with yours? I checked > > here and can not duplicate it here. > > Yes, I see the c-a-d problems. I cannot, for example, c-a-d during some > points of the bootup, its somewhat intermitent. c-a-d before init runs is an unstable thing, does /sbin/reboot consistently work? Does c-a-d consistently work when booted from a DOS floppy? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD