From owner-freebsd-current@FreeBSD.ORG Wed May 21 06:40:04 2003 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 769FC37B404 for ; Wed, 21 May 2003 06:40:04 -0700 (PDT) Received: from ion.gank.org (ion.gank.org [198.78.66.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A98C43FAF for ; Wed, 21 May 2003 06:40:03 -0700 (PDT) (envelope-from craig@xfoil.gank.org) Received: from localhost (ion.gank.org [198.78.66.164]) by ion.gank.org (GankMail) with ESMTP id 4D43A2C61E; Wed, 21 May 2003 08:40:03 -0500 (CDT) Received: from ion.gank.org ([198.78.66.164]) by localhost (ion.gank.org [198.78.66.164]) (amavisd-new, port 10024) with LMTP id 23641-06-2; Wed, 21 May 2003 08:40:03 -0500 (CDT) Received: from owen1492.uf.corelab.com (pix.corelab.com [12.45.169.2]) by ion.gank.org (GankMail) with ESMTP id B09532B853; Wed, 21 May 2003 08:40:02 -0500 (CDT) From: Craig Boston To: AIDA Shinra In-Reply-To: <86k7ck4exw.wl@j10n.org> References: <1053466303.815.22.camel@owen1492.uf.corelab.com> <20030521065152.GA725@laptop.6bone.nl> <86k7ck4exw.wl@j10n.org> Content-Type: text/plain Organization: Message-Id: <1053524410.31600.8.camel@owen1492.uf.corelab.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 21 May 2003 08:40:11 -0500 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: Reproducable panic in in6_pcbbind 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: Wed, 21 May 2003 13:40:04 -0000 > I experienced the same kgdb trace last manth. I found the crashdump > lied about where the trap occured. What DDB prints? If the true trap > point is at in6_pcbbind() in netinet6/in6_pcb.c, the problem may be > same to kern/50621. This may be the same problem. It happens if I disconnect and quickly reconnect the ssh session (causing ssh to open a listener socket on ::1). I thought it might be related to TIME_WAIT, and kern/50621 seems to point to that as well. I do have a serial console hooked up, so as soon as I get a moment when I can remount everything read-only I'll try to trigger the bug and see what DDB says. Craig