From owner-freebsd-stable Thu Aug 24 1:22:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fs2.orientasia.uni-bonn.de (fs2.orientasia.uni-bonn.de [131.220.92.154]) by hub.freebsd.org (Postfix) with ESMTP id 4D4EF37B42C for ; Thu, 24 Aug 2000 01:22:32 -0700 (PDT) Received: from localhost (admin@localhost) by fs2.orientasia.uni-bonn.de (8.9.3/8.9.3) with ESMTP id KAA83037 for ; Thu, 24 Aug 2000 10:22:23 +0200 (CEST) (envelope-from admin@fs2.orientasia.uni-bonn.de) Date: Thu, 24 Aug 2000 10:22:22 +0200 (CEST) From: Administrator OrientAsia To: stable@FreeBSD.ORG Subject: Re: WTF In-Reply-To: <200008232333.SAA15508@awww.jeah.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 23 Aug 2000, Chris Byrnes wrote: > I'm running 3.5-STABLE. > > Recently, my server has started rebooting, at random times, usually > actually quite religiously about every 2 days. > > I thought it might be a RAM problem. Replaced with brand new RAM. > Same problem. > > Any ideas, at all? Pllllllllllllease. I've had the same problem on a 4.X-STABLE machine for some time. In my case, it rebooted regularly and failed to compile larger stuff, such as kernels or make worlds, quite often. It stayed, even though I replaced the RAM. In my case, it was due to a faulty cache module (it's a board that still uses old COAST modules). It's running cacheless now, but it's running. Time to go looking for COAST modules, though :-) Philipp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message