Date: Tue, 27 Jul 2004 21:41:14 +0100 From: Mark Ovens <marko@freebsd.org> To: freebsd-questions@freebsd.org Subject: Re: Random Freeze Message-ID: <4106BDEA.8000405@freebsd.org> In-Reply-To: <410698D0.7010406@orchid.homeunix.org> References: <0E1A1C28F9D61A4D8B6F70AFA3C1B1E42831@srvw2000-cnv1.cnv.local> <38a23c360407220825778b6c68@mail.gmail.com> <4100214E.4090405@orchid.homeunix.org> <4106538D.2070506@freebsd.org> <410698D0.7010406@orchid.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Karol Kwiatkowski wrote: > Mark Ovens wrote: > >> I'm seeing the same problem on my dual Athlon box. The freezes are >> totally random AFAICT, sometimes when the machine is just idling. >> >> I've not used any CPU-specific make options but may try setting some to >> see if it makes a difference. One thing though, I only have >> >> cpu I686_CPU >> >> set, not I486_CPU and I586_CPU as well, maybe that could be a problem? > > AFAIK, that's a proper setting for Athlons. What I recommend is you > shouldn't play with make options before setting up a stable system > (sorry if that's too obvious). > >> I'm running -CURRENT and the build I did on 8 April didn't have this >> problem but it started with the next build I did a couple of weeks ago. >> I've cvsup'd and rebuilt a couple of times since, the last on 25 July, >> but the problem persists. > > I don't have much experience with CURRENT (and with SMP) but if you > didn't change the config files it looks like something in the code (this > is possible in CURRENT, right?). Only thing I can think of is reading > freebsd-current and searching the archives. Not much from me, sorry. > I've noticed something; it only seems to freeze when I'm in X. I had the machine up for over 30 hours at the command line yesterday whilst I upgraded some ports, including KDE (which was why I did it from the command line). I rebooted it when I'd finished. I've never had it stay up anywhere near that long since the 8 April build. Some conflict between XFree86 (4.3.0) and -CURRENT/5.2.1-RELEASE? Also, my machine dual-boots with XP and that stays up for days at a time so, in my case at least, I doubt it's hardware, plus I've run memtest86 and it was OK. Thanks for the input. I'm going to subscribe to freebsd-current and search the archives. Regards, Mark > Regards, > > Karol >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4106BDEA.8000405>