From owner-freebsd-alpha Mon Dec 3 11:14:20 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 0E23F37B416 for ; Mon, 3 Dec 2001 11:14:12 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA07273; Mon, 3 Dec 2001 14:14:07 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id fB3JDfj32190; Mon, 3 Dec 2001 14:13:41 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15371.52965.269328.817708@grasshopper.cs.duke.edu> Date: Mon, 3 Dec 2001 14:13:41 -0500 (EST) To: "Koster, K.J." Cc: "'freebsd-alpha@freebsd.org'" Subject: RE: as2100 saga continues: memory trouble? *sigh* In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FDA180@l04.research.kpn.com> References: <59063B5B4D98D311BC0D0001FA7E452205FDA180@l04.research.kpn.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Koster, K.J. writes: > Dear Wilko, > > > > > > When I type "show memory" on the monitor prompt I see that > > > I have one memory > > > board with 128MB (which is good) but it also says "bad > > > pages 4096" (which I > > > suspect is bad). I cannot remove the one board, for obvious > > > reasons. > > > > You are in deep sh* ... > > > Yeah, I was just in denial. Thanks for slapping me out of it. I see boards on Ebay now & then.. > > Suppose that I know the bad memory range, any way of telling FreeBSD not to > use it? Perhaps abuse the option ROM device to claim that memory range for > itself? Perhaps we should be using the pg_test field for memory clusters on some platforms. I'd be interested in seeing what it said for a machine w/bad ram. If you can build a kernel, can you #define DEBUG_CLUSTER and print out the memc->mddt_pg_test field in the MEMC printf(). Sample, mailer mangled patch below. Drew Index: machdep.c =================================================================== RCS file: /home/ncvs/src/sys/alpha/alpha/machdep.c,v retrieving revision 1.68.2.14 diff -u -c -r1.68.2.14 machdep.c *** machdep.c 2001/10/04 13:09:36 1.68.2.14 --- machdep.c 2001/12/03 19:07:04 *************** *** 836,843 **** for (i = 0; i < mddtp->mddt_cluster_cnt; i++) { memc = &mddtp->mddt_clusters[i]; #ifdef DEBUG_CLUSTER ! printf("MEMC %d: pfn 0x%lx cnt 0x%lx usage 0x%lx\n", i, ! memc->mddt_pfn, memc->mddt_pg_cnt, memc->mddt_usage); #endif totalphysmem += memc->mddt_pg_cnt; --- 836,844 ---- for (i = 0; i < mddtp->mddt_cluster_cnt; i++) { memc = &mddtp->mddt_clusters[i]; #ifdef DEBUG_CLUSTER ! printf("MEMC %d: pfn 0x%lx cnt 0x%lx tested 0x$lx usage 0x%lx\n", i, ! memc->mddt_pfn, memc->mddt_pg_cnt, memc->mddt_pg_test, ! memc->mddt_usage); #endif totalphysmem += memc->mddt_pg_cnt; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message