From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 23 12:49:05 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 838E216A4CF for ; Fri, 23 Jan 2004 12:49:05 -0800 (PST) Received: from mail.advantagecom.net (mail.advantagecom.net [65.103.151.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id 771FD43D2D for ; Fri, 23 Jan 2004 12:48:38 -0800 (PST) (envelope-from andykinney@advantagecom.net) Received: from SCSI-MONSTER (scsi-monster.advantagecom.net [207.109.186.200]) by mail.advantagecom.net (8.11.6/8.11.6) with ESMTP id i0NKkcX16514; Fri, 23 Jan 2004 12:46:39 -0800 From: "Andrew Kinney" Organization: Advantagecom Networks, Inc. To: Bogdan TARU , freebsd-hackers@freebsd.org Date: Fri, 23 Jan 2004 12:48:03 -0800 MIME-Version: 1.0 Message-ID: <40111803.25970.2F6461BE@localhost> Priority: normal In-reply-to: <20040123125040.GA42187@icomag.de> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: Re: 4.9 kernel panics on a poweredge 2650 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: andykinney@advantagecom.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jan 2004 20:49:05 -0000 On 23 Jan 2004 at 13:50, Bogdan TARU wrote: > > > Hi hackers, > > I am experiencing kernel panics on a poweredge 2650 each day around > 3am (usually the machine comes up at 3:04am). The kernel panics are > reproductable by running: /etc/periodic/security/100.chksetuid (in > fact by runnning find on /usr with -perms). The problem lies > somewhere in /usr/ports. Deleting the /usr/ports tree doesn't solve > it, trying a cvs up of /usr/ports results in a crash again. > Our experience is that repetitive crashes when dealing with large numbers of files (like the ports tree) generally points to hitting some OS resource limit. Some things to check that may or may not apply to this particular problem: sysctl vm.zone Make sure you're not hitting any of those limits. sysctl vm.kvm_size sysctl vm.kvm_free If kvm_free is running low just prior to the crash, you might want to increase your KVA_PAGES (see lint) and rebuild your kernel. Of course, this is all hit and miss guess work until you have a crash dump, so getting a crash dump and a traceback from a kernel identical to your running kernel with debugging symbols would be a logical first step if you want to avoid any guessing. If your tracebacks show failures in random locations, you're probably looking at bad RAM. If you always fail in the same spot with each crash, then it is just a matter of determining why and correcting it. I believe the freebsd developer's handbook has instructions on how to setup a system to do an automatic crash dump for any panic. It is relatively straightforward. Sincerely, Andrew Kinney President and Chief Technology Officer Advantagecom Networks, Inc. http://www.advantagecom.net