From owner-freebsd-questions Mon Sep 4 6:38:36 2000 Delivered-To: freebsd-questions@freebsd.org Received: from relay2.inwind.it (relay2.inwind.it [212.141.53.73]) by hub.freebsd.org (Postfix) with ESMTP id B1FAB37B42C for ; Mon, 4 Sep 2000 06:38:32 -0700 (PDT) Received: from bartequi.ottodomain.org (212.141.78.199) by relay2.inwind.it (5.1.046) id 39AF9CE300012B95; Mon, 4 Sep 2000 15:38:25 +0200 From: Salvo Bartolotta Date: Mon, 04 Sep 2000 14:38:06 GMT Message-ID: <20000904.14380600@bartequi.ottodomain.org> Subject: Re: A sick little box To: Daan Franke Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <3182D9D293F2D211B15A00500416D4902E1571@baco.websilon.nl> References: <3182D9D293F2D211B15A00500416D4902E1571@baco.websilon.nl> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 9/4/00, 1:20:35 PM, Daan Franke wrote regarding A = sick little box: > Hi, > I have a box here at work doing natd services for my company. It works= =20 fine > but suddenly reboots out of nowhere with no appearant reason or > circumstances. The logs say nothing about the reboot except that it=20 isn't > done with the proper sequence. > I also tried to recompile my kernel but that was a no go because of=20 this > error on the make depend (it also gives this error on the GENERIC=20 kernel) > I get this error message: > =3D=3D=3D> agp > @ -> /usr/src/sys > machine -> /usr/src/sys/i386/include > make: don't know how to make agp_if.c. Stop > *** Error code 2 > Stop in /usr/src/sys/modules. > *** Error code 1 > Stop in /usr/src/sys/compile/GBL. > My theories are limited because of the lack of messages I get from=20 logs and > such. > Im looking for reasons why this would happen. > Info of box: > pII 350 > 256 MB of RAM > SCSI HD > ATAPI CD-ROM > FreeBSD 4.0-RELEASE > Thanks for reading this and if you want, reply. > Daan Franke > System Engineer Dear Daan Franke, In a good number of such cases, the culprit turns out to be bad=20 hardware: bad RAM, bad cache, inadequate cooling, etc. A careful=20 investigation will spot any bad harware. As far as your build errors are concerned, I may be completely wrong,=20 but I am afraid that, after cvsup'ing your sources, you have not=20 followed the instructions found in /usr/src/UPDATING. The kernel build=20 procedure, in that specific case (after cvsup'ing), changed a couple=20 of months ago. HTH, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message