From owner-freebsd-current@FreeBSD.ORG  Mon Sep 19 07:12:15 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 C6AA116A41F
	for <current@freebsd.org>; Mon, 19 Sep 2005 07:12:15 +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 2704C43D45
	for <current@freebsd.org>; Mon, 19 Sep 2005 07:12:14 +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 j8J7C41d022899
	for <current@freebsd.org>; Mon, 19 Sep 2005 11:12:12 +0400 (MSD)
	(envelope-from maxim@macomnet.ru)
Date: Mon, 19 Sep 2005 11:12:04 +0400 (MSD)
From: Maxim Konovalov <maxim@macomnet.ru>
To: current@freebsd.org
Message-ID: <20050919110006.R22597@mp2.macomnet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: 
Subject: 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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Sep 2005 07:12:15 -0000

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

-- 
Maxim Konovalov