Date: Thu, 12 Sep 1996 22:18:54 -0700 (PDT) From: Jaye Mathisen <mrcpu@cdsnet.net> To: "Julian H. Stacey" <jhs@FreeBSD.org> Cc: Stephen Hocking <sysseh@devetir.qld.gov.au>, current@FreeBSD.org Subject: Re: VM/kernel problems? Message-ID: <Pine.NEB.3.95.960912221646.9658r-100000@mail.cdsnet.net> In-Reply-To: <199609112156.XAA03514@vector.jhs.no_domain>
next in thread | previous in thread | raw e-mail | index | archive | help
Hmmm, as of -current supped on the 11th and 12th, my box is working just yippee skippee after a make world. Although I'm not using John's cache color mumbo-jumbo voodoo evilness. On Wed, 11 Sep 1996, Julian H. Stacey wrote: > Date: Wed, 11 Sep 1996 23:56:16 +0200 > From: "Julian H. Stacey" <jhs@FreeBSD.org> > To: Stephen Hocking <sysseh@devetir.qld.gov.au> > Cc: current@FreeBSD.org > Subject: Re: VM/kernel problems? > > Hi, Reference: > > > Is this just me? I started getting these on three different machines with > > > a > > > vanilla -current kernel from within the last 24 hours. > > > > > > pid 659 (FvwmPager), uid 433: exited on signal 11 (core dumped) > > 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 ! > > Julian > -- > Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.960912221646.9658r-100000>