Date: Fri, 19 Oct 2001 16:43:18 +0100 From: Rasputin <rasputin@submonkey.net> To: stable@freebsd.org Subject: Re: compiling 4.4-STABLE Message-ID: <20011019164318.A12619@shikima.mine.nu> In-Reply-To: <3BD045DE.79886153@ntlworld.com>; from ianjhart@ntlworld.com on Fri, Oct 19, 2001 at 04:25:18PM %2B0100 References: <3BD186A7.3020808@delaware.net> <3BD045DE.79886153@ntlworld.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* ian j hart <ianjhart@ntlworld.com> [011019 16:30]: > "j. rivera" wrote: > > > > Hello, > > > > I've been fighting with my machine now for about three days, but I'm > > not sure what to make of my situation, and any advice would be > > appreciated. > > Here's the situation-- > > > > The machine: > > 133 mhz Pentium > > 64 MB memory > > 6 GB WD hard drive > > > > My problem: > > I was running 4.3-RELEASE just fine. I decided to upgrade to > > 4.4-RELEASE, hosed my machine, so I reinstalled 4.4 fresh. I've now > > been trying to compile 4.4-STABLE, but with no luck. > > > > I get all sorts of weirdness when I try to compile STABLE. The > > compiler segmentation faults and dumps core. Perl dumped core trying > > to recompile the kernel. Every so often during make buildworld, the > > machine arbitrarily reboots. That sounds nastily familiar. I'd agree with you that the hardware is unlikely to have suddenly broken, and I've seen a couple of cases where bad software can resemble bad hardware - in my case it was dodgy compiler flags from setting CPUTYPE. The problem was compounded by the fact it didn't break when I first built world, which meant every binary on the standard install was screwed. I managed to get out of it by going single user, unsetting CPUTYPE, and doing make buildworld -DNOCLEAN over and over again, until everything was built , then installing as normal. (make -j<anything> is not your friend on a shaky system, either) any binaries that repeatedly broke were replaced by scp'ed copies from a friends system. Evebtually I got it back up ,and I'm typing this on the same box, so it wasn't hardware, but it certainly looked like it at the time. It doesn't sound like this is your problem, but maybe some defaults have changed in 4.4-RELEASE, write caching by default, for example - maybe try setting hw.ata.wc=0 in /boot/loader.conf? -- Rasputin :: Jack of All Trades - Master of Nuns :: 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?20011019164318.A12619>