From owner-freebsd-current@FreeBSD.ORG Mon Sep 19 12:49:07 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 8DDBB16A421; Mon, 19 Sep 2005 12:49:07 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFF2443D45; Mon, 19 Sep 2005 12:49:06 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.13.3/8.13.3) with ESMTP id j8JCn51O085194; Mon, 19 Sep 2005 16:49:05 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Mon, 19 Sep 2005 16:49:05 +0400 (MSD) From: Maxim Konovalov To: Andre Oppermann In-Reply-To: <432EADC6.80908@freebsd.org> Message-ID: <20050919164747.N85035@mp2.macomnet.net> References: <20050919110006.R22597@mp2.macomnet.net> <432EADC6.80908@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 12:49:07 -0000 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. -- Maxim Konovalov