From owner-freebsd-stable@FreeBSD.ORG Thu Nov 25 08:18:22 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CB3D16A4CE for ; Thu, 25 Nov 2004 08:18:22 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F36843D4C for ; Thu, 25 Nov 2004 08:18:22 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 33A6072DD4; Thu, 25 Nov 2004 00:18:22 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 2E69172DCB; Thu, 25 Nov 2004 00:18:22 -0800 (PST) Date: Thu, 25 Nov 2004 00:18:22 -0800 (PST) From: Doug White To: Andrei Grudiy In-Reply-To: <20041115084956.GA24138@interexc.com> Message-ID: <20041124234936.K2006@carver.gumbysoft.com> References: <20041115084956.GA24138@interexc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: 100.chksetuid in /etc/periodic/security resets the mashine X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Nov 2004 08:18:22 -0000 Please don't crosspost lists, particularly -security (which is totally unrelated) and -questions and another list (which is generally redundant). I've reset the cc: to -stable since thats the only one of the 3 I'm subscribed to. Thanks! On Mon, 15 Nov 2004, Andrei Grudiy wrote: > Hello, kolleages! > I have a problem. > When I (or system) start the script 100.chksetuid in > /etc/periodic/security my machine resets. This is probably a hardware problem. chksetuid does a full scan of the filesystem(s) and either the load from the scan or some secondary effect (low voltage, overtemperature, bad memory) causes the reset. Also, spontaneous resets are tough to cause in software running in protected mode without help from bad hardware :-) I'd check the usual suspects: turn off any overclocking, check heat sinks, fans, and temperature sensors, and if your machine's vendor offers a diagnostic tool, run it on repeat for a day or two. Also set up a serial console and run the script manually and see if you are getting a panic or some other output. > The machine: > Timecounter "i8254" frequency 1193182 Hz > CPU: Intel(R) Xeon(TM) CPU 3.06GHz (3056.82-MHz 686-class CPU) > System version: > FreeBSD 4.10-STABLE #0: Mon Nov 8 06:50:54 PST 2004 This seems like a server-class machine, which may also have some onboard monitoring which may have logged something. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org