From owner-freebsd-current@FreeBSD.ORG Fri Aug 13 06:40:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71A1D16A4CE for ; Fri, 13 Aug 2004 06:40:28 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 7A8B743D2F for ; Fri, 13 Aug 2004 06:40:27 +0000 (GMT) (envelope-from sebastian.ssmoller@gmx.net) Received: (qmail 16001 invoked by uid 65534); 13 Aug 2004 06:40:25 -0000 Received: from pD9E81BF6.dip.t-dialin.net (HELO tyrael.linnet) (217.232.27.246) by mail.gmx.net (mp009) with SMTP; 13 Aug 2004 08:40:25 +0200 X-Authenticated: #15005775 Date: Fri, 13 Aug 2004 08:42:44 +0200 From: sebastian ssmoller To: freebsd-current@freebsd.org Message-Id: <20040813084244.7efee5a8.sebastian.ssmoller@gmx.net> In-Reply-To: References: <20040812171410.GA91666@neo.redjade.org> <200408121938.04611.max@love2party.net> <200408122302.19418.max@love2party.net> <20040813073216.3f09e114.sebastian.ssmoller@gmx.net> X-Mailer: Sylpheed version 0.9.9-gtk2-20040229 (GTK+ 2.4.1; i386-portbld-freebsd5.2.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Panic in nd6_slowtimo() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Aug 2004 06:40:28 -0000 (...) > > > > hi, > > if i remember correctly i got this panic from time to time on my > > workstation. what i did as a "work-around" i guess was to disable > > ipv6 > > (option INET6). > > > > the system runs stable now but i had to configure X11 to -nolisten > > tcp > > which makes it difficult to start X11 progs from another user :) > > > > have a look at: > > http://lists.freebsd.org/pipermail/freebsd-current/2004-January/019524.html > > > > I would be interested to know if this still happens. We've been > trying to fix up the IPv6 code. I am running IPv6 on several machines > (CURRENT and STABLE) and have yet to see this. I am also using > neighbor discovers (nd) extensively. i dont know whether this prob still exists. i run 5.2.1 on this system (inet6 disabled as i said) and actually i do not really want to update to -current at the moment cause this is my "production" workstation. :( unfortunately i could not reproduce this problem on my test system (inet6 enabled; using pf) ... but what i can do is, i can build a current kernel only, reboot the system with it, start pf, connect to the internet (dsl) and see whether this panic occurs again. i dont know whether this will work .... (?) thx regards, seb > > Later, > George