Date: Thu, 12 Sep 1996 19:19:30 -0500 (EST) From: "John S. Dyson" <toor@dyson.iquest.net> To: jhs@FreeBSD.org Cc: sysseh@devetir.qld.gov.au, current@FreeBSD.org Subject: Re: VM/kernel problems? Message-ID: <199609130019.TAA06054@dyson.iquest.net> In-Reply-To: <199609112156.XAA03514@vector.jhs.no_domain> from "Julian H. Stacey" at Sep 11, 96 11:56:16 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > I managed to zap my 2 machines here with current of a couple of days back, > I got lots of sig 11s & 6s, & some free/malloc complaints, > then I broke new things while fixing other things. > I'm rebuilding now with old current binaries, then doing a make with 2.1.5 src/ > then will crawl back to current of a week or so ago, or maybe back to > brand new current, once John D announces an OK. > > Synopsis: I'll confirm: don't use current of a few days ago folks, it bites ! > Maybe I have made a mistake. For a while, I had warned the -current mailing list before making my "commit." I will resume that procedure. For those who haven't already guessed, the pmap code is notoriously difficult to work on (at least for me), and as a warning -- PLEASE be wary of my pmap commits :-)... I know that it does not absolve my sin, but this stuff needs to be done, and needs to be tested (and I try my darnedest before commiting it, believe it or not, the code is even worse when I first write it :-)). Soon, I hope to have a dual p6, so watch out SMP guys :-)... It will also be a second machine to do more complete testing on. John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609130019.TAA06054>