From owner-freebsd-questions@FreeBSD.ORG Sun Mar 9 12:34:23 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 209831065672 for ; Sun, 9 Mar 2008 12:34:23 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.ilk.org (dsl092-078-145.bos1.dsl.speakeasy.net [66.92.78.145]) by mx1.freebsd.org (Postfix) with ESMTP id DC0218FC1F for ; Sun, 9 Mar 2008 12:34:22 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from Lowell-Desk.lan (Lowell-Desk.lan [172.30.250.6]) by be-well.ilk.org (Postfix) with ESMTP id DA7B62842F for ; Sun, 9 Mar 2008 08:34:19 -0400 (EDT) Received: by Lowell-Desk.lan (Postfix, from userid 1147) id DC70A1CC49; Sun, 9 Mar 2008 08:34:18 -0400 (EDT) To: freebsd-questions@freebsd.org References: <15921128.post@talk.nabble.com> From: Lowell Gilbert Date: Sun, 09 Mar 2008 08:34:18 -0400 In-Reply-To: <15921128.post@talk.nabble.com> (Ofloo's message of "Sat\, 8 Mar 2008 14\:09\:27 -0800 \(PST\)") Message-ID: <44bq5om5yt.fsf@Lowell-Desk.lan> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: IPv6 6to4 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2008 12:34:23 -0000 Ofloo writes: > When using 6to4 extensively the system crashes I've never had this with gif > tunnels though every since I've started using 6to4 and stf interface this > happens especially when the v6 gateway is unreachable for short time, .. > > I haven't seen the error yet but I do know i had this before, well it's not > showing in the /var/log/all.log nor /var/log/messages, however I do remember > something about non-sleeping thread or something.. > > If anyone needs more info let me know I'll be more then happy to provide a > system to test on if required currently i have 3 exact systems which have > this issue. See the kernel debugging section in the Developers' Handbook. You don't mention what version you're running, but you may want to update to something recent.