From owner-freebsd-current@FreeBSD.ORG Mon Jun 29 14:50:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 580161065707 for ; Mon, 29 Jun 2009 14:50:12 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from fujibayashi.jp (karas.fujibayashi.jp [77.221.159.4]) by mx1.freebsd.org (Postfix) with ESMTP id 066738FC28 for ; Mon, 29 Jun 2009 14:50:12 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from [192.168.0.2] (ppp91-122-47-189.pppoe.avangarddsl.ru [91.122.47.189]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by fujibayashi.jp (Postfix) with ESMTPSA id AD8AB78F7F; Mon, 29 Jun 2009 18:50:10 +0400 (MSD) Message-ID: <4A48D4A2.8010207@haruhiism.net> Date: Mon, 29 Jun 2009 18:50:10 +0400 From: Kamigishi Rei User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Lawrence Stewart References: <4A45ABB1.7040506@haruhiism.net> <4A48CE02.5000200@freebsd.org> In-Reply-To: <4A48CE02.5000200@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: r194546 amd64: kernel panic in tcp_sack.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 29 Jun 2009 14:50:12 -0000 Lawrence Stewart wrote: > I'm not intimately familiar with our SACK implementation, and these > things are often extremely painful to track down. First step: is the > panic reproducible? So far I couldn't reproduce it, but I think the fact that I couldn't reproduce it has something to do with frequent reboots due to buildworld/buildkernel lately because of other problems. > How did you try to get it to save the core? A dump would be very > useful to have around. Since I'm not much of an expert in the kernel debugger, I tried to let it continue with the panic, i.e. typed 'continue' which produced a fatal trap 12 right after "Dumping XXXX MB: (~3 values were here)". -- Kamigishi Rei KREI-RIPE