From owner-freebsd-stable@FreeBSD.ORG  Wed Oct  1 12:59:55 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 3F0CC16A4B3
	for <stable@freebsd.org>; Wed,  1 Oct 2003 12:59:55 -0700 (PDT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7F3C543F3F
	for <stable@freebsd.org>; Wed,  1 Oct 2003 12:59:54 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id h91JxrgG003946;
	Wed, 1 Oct 2003 15:59:53 -0400 (EDT)
Date: Wed, 1 Oct 2003 15:59:53 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: "Karl M. Joch" <k.joch@kmjeuro.com>
In-Reply-To: <3F7B30EF.4080306@kmjeuro.com>
Message-ID: <Pine.GSO.4.10.10310011556370.2470-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Reply-To: deischen@freebsd.org
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Oct 2003 19:59:55 -0000

On Wed, 1 Oct 2003, Karl M. Joch wrote:

> Mike Tancsa wrote:
> 
> > 
> > Actually, one note on this, I had a server that was panicing similar to 
> > this that DES was kind enough to look at a while ago.  The problem was 
> > never tracked down, but I found that taking INET6 out of the kernel 
> > solved the problem.  I asked michael@gargantuan.com if this was possible 
> > to try, and he said they make heavy use of INET6 so they could not take 
> > it out. The other user seeing similar crashes (tss@reflection.co.jp) 
> > also makes use of INET6. It could of course be total coincidence and 
> > have nothing to do with it.

You can also try setting your clocks ahead (or back) and see
if the crashes move with the time change.

I also saw in one of the crashes that ntpd was running.
Could there be some sort of race with that?

-- 
Dan Eischen