From owner-freebsd-current@FreeBSD.ORG Mon Sep 19 13:10:00 2005 Return-Path: X-Original-To: current@freebsd.org 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 40F9B16A41F for ; Mon, 19 Sep 2005 13:10:00 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EB5C43D45 for ; Mon, 19 Sep 2005 13:09:59 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 93414 invoked from network); 19 Sep 2005 12:44:19 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 19 Sep 2005 12:44:19 -0000 Message-ID: <432EB8A4.5070004@freebsd.org> Date: Mon, 19 Sep 2005 15:09:56 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: Maxim Konovalov References: <20050919110006.R22597@mp2.macomnet.net> <432EADC6.80908@freebsd.org> <20050919164747.N85035@mp2.macomnet.net> In-Reply-To: <20050919164747.N85035@mp2.macomnet.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: sbflush_locked panic and tcp_sack 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, 19 Sep 2005 13:10:00 -0000 Maxim Konovalov wrote: > On Mon, 19 Sep 2005, 14:23+0200, Andre Oppermann wrote: > > >>Maxim Konovalov wrote: >> >>>Hi, >>> >>>I got a panic at the end of sbflush_locked() on recent -current when >>>open a large photo gallery with firefox. >>> >>>if (sb->sb_cc || sb->sb_mb || sb->sb_mbcnt) >>> panic("sbflush_locked: cc %u || mb %p || mbcnt %u", >>> sb->sb_cc, >>> (void *)sb->sb_mb, sb->sb_mbcnt); >>> >>>It seems I can reproduce this panic easily. Moreover, turning >>>tcp_sack off eliminates this panic. Does anybody see that? >>> >>>http://maxim.int.ru/stuff/panic/SONNIE >>>http://maxim.int.ru/stuff/panic/kgdb.typescript >>>http://maxim.int.ru/stuff/panic/sysctl-a >> >>This rings a bell. Sounds like a problem with delayed header drop in TCP >>segments. In tcp_input() have the variable "tlen" examined. > > Well, there is no tcp_input() in the backtrace. Yes, it must have happend before and left the socket buffer in an inconsistent state. -- Andre