From owner-freebsd-stable@FreeBSD.ORG Thu Oct 2 07:30:18 2003 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 0AAC316A4B3 for ; Thu, 2 Oct 2003 07:30:18 -0700 (PDT) Received: from mx2.biglist.com (westside.urbanblight.com [216.223.208.40]) by mx1.FreeBSD.org (Postfix) with SMTP id 0582843FF2 for ; Thu, 2 Oct 2003 07:30:17 -0700 (PDT) (envelope-from omar@mx2.biglist.com) Received: (qmail 61725 invoked by uid 601); 2 Oct 2003 14:30:15 -0000 Date: Thu, 2 Oct 2003 10:30:15 -0400 From: Omar To: Mike Tancsa Message-ID: <20031002103015.A61087@westside.urbanblight.com> References: <3F7B30EF.4080306@kmjeuro.com> <6.0.0.22.0.20031001160628.06a2bd60@209.112.4.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <6.0.0.22.0.20031001160628.06a2bd60@209.112.4.2>; from mike@sentex.net on Wed, Oct 01, 2003 at 04:09:58PM -0400 cc: stable@freebsd.org Subject: Re: panics on 24 hour boundaries 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, 02 Oct 2003 14:30:18 -0000 Have you replaced the memory? As FreeBSD uses more and more of the RAM, maybe it's running into an issue where one of your modules is faulty, and problem isn't exposed until there's sufficient memory usage. Omar On Wed, Oct 01, 2003 at 04:09:58PM -0400, Mike Tancsa wrote: > At 03:59 PM 01/10/2003, Daniel Eischen wrote: > > >You can also try setting your clocks ahead (or back) and see > >if the crashes move with the time change. > > Tried that and it didnt make a difference. Also, at the time, the box > seemed to panic when periodic was running. BUT if I changed the daily > scripts to run a few hours after boot time, it would not die. I could run > daily to my hearts content manually, but no crash. (I also made sure than > the disk cache would be flushed by running md5 on a 1 gig file a couple of > time in case it was some combo disk / cache issue). In my case, removing > INET6 from the kernel totally solved the problem. > > ---Mike