Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Dec 2000 09:51:35 +0000
From:      "Neil Long" <neil.long@computing-services.oxford.ac.uk>
To:        freebsd-user@netscum.dk
Cc:        freebsd-stable@freebsd.org
Subject:   Re: RELENG_3 buildworld problems
Message-ID:  <1001221095135.ZM23712@ratbert.oucs.ox.ac.uk>
In-Reply-To: Reddy Crashalott <autoretributionmeowbot@free-N0rp.netscum.dk> "Re: RELENG_3 buildworld problems" (Dec 21,  7:15am)
References:  <E148rPa-0005py-00@ratbert.oucs.ox.ac.uk>  <200012210615.eBL6FJw62370@crotchety.newsbastards.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1001221095135.ZM23712>