From owner-freebsd-stable@FreeBSD.ORG Wed Oct 1 13:07:25 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 D93AE16A4B3; Wed, 1 Oct 2003 13:07:25 -0700 (PDT) Received: from avscan2.sentex.ca (avscan2.sentex.ca [199.212.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE66C43FDD; Wed, 1 Oct 2003 13:07:24 -0700 (PDT) (envelope-from mike@sentex.net) Received: from localhost (localhost [127.0.0.1]) by avscan2.sentex.ca (Postfix) with ESMTP id B187C59D8E; Wed, 1 Oct 2003 16:07:15 -0400 (EDT) Received: from avscan2.sentex.ca ([127.0.0.1]) by localhost (avscan2.sentex.ca [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 66419-20; Wed, 1 Oct 2003 16:07:15 -0400 (EDT) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by avscan2.sentex.ca (Postfix) with ESMTP id 99DCA59D8D; Wed, 1 Oct 2003 16:07:15 -0400 (EDT) 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 h91K7EdK089264; Wed, 1 Oct 2003 16:07:14 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.0.0.22.0.20031001160628.06a2bd60@209.112.4.2> X-Sender: mdtpop@209.112.4.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Wed, 01 Oct 2003 16:09:58 -0400 To: deischen@freebsd.org From: Mike Tancsa In-Reply-To: References: <3F7B30EF.4080306@kmjeuro.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by Sentex Communications (avscan2/20030616p5) 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: Wed, 01 Oct 2003 20:07:26 -0000 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