Date: Sat, 03 Oct 2009 22:58:26 +0400 From: Kamigishi Rei <spambox@haruhiism.net> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: Another panic (during netisr?) Message-ID: <4AC79ED2.5060507@haruhiism.net> In-Reply-To: <20091002191255.J26486@maildrop.int.zabbadoz.net> References: <4AC61ED6.1090802@haruhiism.net> <20091002191255.J26486@maildrop.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AC79ED2.5060507>