From owner-freebsd-stable Thu Dec 21 1:51:57 2000 From owner-freebsd-stable@FreeBSD.ORG Thu Dec 21 01:51:53 2000 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from oxmail.ox.ac.uk (oxmail4.ox.ac.uk [163.1.2.33]) by hub.freebsd.org (Postfix) with ESMTP id 2E38537B400 for ; Thu, 21 Dec 2000 01:51:53 -0800 (PST) Received: from ratbert.oucs.ox.ac.uk ([163.1.14.71]) by oxmail.ox.ac.uk with esmtp (Exim 3.12 #1) id 1492Nr-0001t4-00; Thu, 21 Dec 2000 09:51:35 +0000 Received: from neil by ratbert.oucs.ox.ac.uk with local (Exim 3.14 #1) id 1492Nr-0006AU-00; Thu, 21 Dec 2000 09:51:35 +0000 From: "Neil Long" Message-Id: <1001221095135.ZM23712@ratbert.oucs.ox.ac.uk> Date: Thu, 21 Dec 2000 09:51:35 +0000 In-Reply-To: Reddy Crashalott "Re: RELENG_3 buildworld problems" (Dec 21, 7:15am) References: <200012210615.eBL6FJw62370@crotchety.newsbastards.org> X-Mailer: Z-Mail (5.0.0 30July97) To: freebsd-user@netscum.dk Subject: Re: RELENG_3 buildworld problems Cc: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Dec 21, 7:15am, Reddy Crashalott wrote: > Subject: Re: RELENG_3 buildworld problems > [disclaimer: this is an invalid sender address; replies should be > posted to the list or perhaps better not posted at all] > > :: I have cvsup'd since then (and double checked) but now it is dieing in > :: buildworld but it never seems to be the same place - e.g. > > You've got some dodgy memory flipping bits around: > > :: /usr/src/usr.bin/vi/../../contrib/nvi/include/vi_extern.h:104: > :: parse error before `VIcMD' > > VICMD -> VIcMD > ^ ^ > :: /var/tmp/ccV66454.s:114: Error: invalid character (0x8) in opcode > > bit gone awry > > :: another time it failed to find 'chare' rather than 'share' > > chare -> share > ^ ^ > > :: Anyone else seeing such weirdness? > > I've seen it with flaky memory. Try swapping bits of it out, or > doing a memory test, until you isolate the defective part(s) > > > Hello Kind of spooky (and it may be bad memory so I will run some more tests) but I risked it and built a new kernel (the cvsup changes were the recent contrib/bind, procfs_status.c, dev/isp and related, krb4 fixes and pmap.c and procfs_ctl.c After rebooting on the new kernel (single user) a buildworld ran as smoothly as ever. This was on a Thinkpad 600E with 128M (so I could down it to 64M again). I had done all the usual dead chicken stuff and zapped /usr/obj but with luck I will never see the problem again. Anyone know of a good memory tester (I will try the built-in diagnostics on the TP - they take almost forever but that doesn't always mean they are good. regards Neil -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr Neil J Long, Computing Services, University of Oxford 13 Banbury Road, Oxford, OX2 6NN, UK Tel:+44 1865 273232 Fax:+44 1865 273275 EMail: Neil.Long@computing-services.oxford.ac.uk PGP: ID 0xE88EF71F OxCERT: oxcert@ox.ac.uk PGP: ID 0x4B11561D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message