From owner-freebsd-stable@FreeBSD.ORG Sat Oct 4 08:57:32 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 F0C2316A4BF for ; Sat, 4 Oct 2003 08:57:32 -0700 (PDT) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C14A44003 for ; Sat, 4 Oct 2003 08:57:31 -0700 (PDT) (envelope-from mike@sentex.net) Received: from avscan1.sentex.ca (avscan1.sentex.ca [199.212.134.11]) by smtp3.sentex.ca (8.12.9p2/8.12.9) with ESMTP id h94FvSHr088533; Sat, 4 Oct 2003 11:57:28 -0400 (EDT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by avscan1.sentex.ca (8.12.9p2/8.12.9) with ESMTP id h94FvUZR040427; Sat, 4 Oct 2003 11:57:30 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.9p1/8.12.9) with ESMTP id h94FvTdK002069; Sat, 4 Oct 2003 11:57:29 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.0.0.22.0.20031004115727.02ca49f8@209.112.4.2> X-Sender: mdtpop@209.112.4.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Sat, 04 Oct 2003 12:00:31 -0400 To: Omar From: Mike Tancsa In-Reply-To: <20031002103015.A61087@westside.urbanblight.com> References: <3F7B30EF.4080306@kmjeuro.com> <6.0.0.22.0.20031001160628.06a2bd60@209.112.4.2> <20031002103015.A61087@westside.urbanblight.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by Sentex Communications (avscan1/20021227) 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: Sat, 04 Oct 2003 15:57:33 -0000 Yes, but the system regularly made use of all the RAM and them some. It didnt take long to start swapping out files. This was not a hardware issue. The crash dumps (i had several) were in the same locations and not random. ---Mike At 10:30 AM 02/10/2003, Omar wrote: >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 >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"