From owner-freebsd-stable Mon Jun 10 0: 2:53 2002 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (65-85-207-106.client.dsl.net [65.85.207.106]) by hub.freebsd.org (Postfix) with ESMTP id 271EB37B401 for ; Mon, 10 Jun 2002 00:02:51 -0700 (PDT) Received: (from mike@localhost) by jason.argos.org (8.11.4/8.11.4) id g5A6xqc13428; Mon, 10 Jun 2002 02:59:52 -0400 Date: Mon, 10 Jun 2002 02:59:51 -0400 From: Mike Nowlin To: Oliver Crow Cc: freebsd-stable@freebsd.org Subject: Re: Clockwork 24 hour crash in 4.5-RELEASE-p5 Message-ID: <20020610025951.D13344@argos.org> References: <20020603192117.E79925-100000@iguana.simplexity.net> <20020609224325.T17826-100000@iguana.simplexity.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020609224325.T17826-100000@iguana.simplexity.net>; from ocrow@simplexity.net on Sun, Jun 09, 2002 at 11:08:08PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Recompiling the kernel without IPv6 support seems to prevent the crashes > (ie comment out 'options INET6' in kernel config). It is not clear what > precisely the problem is, but it seems likely that it's an interaction > between mpd and IPv6. Disabling either one appears to be a sufficent > workaround to prevent the crashes. Hmm - given that, I'd lean more towards something in IPv6 - the machine I have that's showing this problem isn't running mpd, although it does have IPv6... :( --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message