From owner-freebsd-current@FreeBSD.ORG Sat Oct 3 18:58:26 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 1CB121065670 for ; Sat, 3 Oct 2009 18:58:26 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from mail.haruhiism.net (remilia.fujibayashi.jp [92.243.64.6]) by mx1.freebsd.org (Postfix) with ESMTP id C62048FC12 for ; Sat, 3 Oct 2009 18:58:25 +0000 (UTC) Received: from [192.168.0.2] (ppp91-122-47-189.pppoe.avangarddsl.ru [91.122.47.189]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.haruhiism.net (Postfix) with ESMTPSA id A2DD742F56; Sun, 4 Oct 2009 03:58:21 +0900 (JST) Message-ID: <4AC79ED2.5060507@haruhiism.net> Date: Sat, 03 Oct 2009 22:58:26 +0400 From: Kamigishi Rei User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.4pre) Gecko/20090915 Thunderbird/3.0b4 MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <4AC61ED6.1090802@haruhiism.net> <20091002191255.J26486@maildrop.int.zabbadoz.net> In-Reply-To: <20091002191255.J26486@maildrop.int.zabbadoz.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current Subject: Re: Another panic (during netisr?) 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: Sat, 03 Oct 2009 18:58:26 -0000 Hello, On 02.10.2009 23:14, Bjoern A. Zeeb wrote: >> This is on FreeBSD 8.0-BETA3 (Ameagari) #23 r196460: Mon Aug 24 >> 00:36:33 JST 2009; not sure if it has been witnessed or fixed. I've >> been running it without restarts to test the stability and here we go: >> >> Unread portion of the kernel message buffer: >> panic: tcp_input: so == NULL > > This looks like an explicit panic unrelated to the netisr in first > place. > > More likely a race condition with socket teardown which should not > happen in theory;) Oh, so it's just like that panic in tcp_sack then. ;) I've replaced the CPU in the server (was: dual core, now: quad core) for even more chances for a race condition to strike; waiting for this one to re-appear again now on 8.0-RC1 ;) (Though 39 days of uptime was a pretty good result for BETA3, I can't say I'm satisfied, as I have yet to see my 7.2-STABLE server panic; 39 days is not impressive when it comes to production use including running ircd for a large network.) I do indeed hope that it will never happen again. -- Kamigishi Rei KREI-RIPE fujibayashi.jp