From owner-freebsd-current@FreeBSD.ORG Sun Oct 17 21:16:36 2004 Return-Path: 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 1823D16A4D1 for ; Sun, 17 Oct 2004 21:16:36 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE1C743D45 for ; Sun, 17 Oct 2004 21:16:35 +0000 (GMT) (envelope-from marchenko@gmail.com) Received: by mproxy.gmail.com with SMTP id 74so129333rnk for ; Sun, 17 Oct 2004 14:16:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=O/6YjXkw+uOz8JBTs5H7gOaa445gNmnZKpRo9iHVCLBMxOps720+ASKgf2YfkoAjzTMWFKpQZunb3u+4CbNPJeq5f5gFXfui1qweXlRlvzv+gRDr2VXq5fogEgwZBVCjb5uHDLrxe7uoLyDv0Qmv4xcApsvuZvchENz501Pw3UY Received: by 10.38.81.49 with SMTP id e49mr1131958rnb; Sun, 17 Oct 2004 14:16:34 -0700 (PDT) Received: by 10.38.22.66 with HTTP; Sun, 17 Oct 2004 14:16:34 -0700 (PDT) Message-ID: Date: Sun, 17 Oct 2004 17:16:34 -0400 From: Vlad To: Robert Watson In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041015174542.61606d63.ubm@u-boot-man.de> cc: scottl@freebsd.org cc: current@freebsd.org cc: Marc UBM Bocklet Subject: Re: [BETA7-panic] sodealloc(): so_count 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Vlad List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2004 21:16:36 -0000 Robert, is there a specific condition when that happens? I tried to simulate heavy tcp traffic from number of sources but could not induct the panic by such artificial traffic. It happened to me only in 'natural' way ;) so maybe if you know exactly how to trigger it, and share that with us, we could do some workaround on live production servers so it doesn't happen, until it's fixed in the code? > The good news and the bad news: after spending a day or two hacking up an > IP stack simulator to simulate various nasty combinations of TCP packets, > I've managed to reproduce the problem, and am able to get a core. I'm > currently working on tracking down the problem. -- Vlad