From owner-freebsd-questions@FreeBSD.ORG Fri Jul 25 11:17:43 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E61C37B404 for ; Fri, 25 Jul 2003 11:17:43 -0700 (PDT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA17243FAF for ; Fri, 25 Jul 2003 11:17:42 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: from be-well.ilk.org (be-well.no-ip.com[66.30.200.37]) by comcast.net (rwcrmhc13) with ESMTP id <2003072518174201500qlj47e>; Fri, 25 Jul 2003 18:17:42 +0000 Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37] (may be forged)) by be-well.ilk.org (8.12.9/8.12.9) with ESMTP id h6PIHfM1006123; Fri, 25 Jul 2003 14:17:41 -0400 (EDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.9/8.12.6/Submit) id h6PIHeqB006120; Fri, 25 Jul 2003 14:17:40 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-questions-local@be-well.ilk.org using -f Sender: lowell@be-well.no-ip.com To: Andrea Venturoli References: <200307231425.h6NEPFMG002436@soth.ventu> From: Lowell Gilbert Date: 25 Jul 2003 14:17:40 -0400 In-Reply-To: <200307231425.h6NEPFMG002436@soth.ventu> Message-ID: <44y8ymii7v.fsf@be-well.ilk.org> Lines: 11 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: Crash with bpf X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 18:17:43 -0000 Andrea Venturoli writes: > The problem has started to show after an upgrade to 4.6 or 4.7 I believe (but I cannot recall exactly). > I might as well try an upgrade to 4.8, but I'd rather have more insight. It's more work to try to track the problem if you're using different code than (for example, I am on my) system, so upgrading is a help to the person trying to track it. I don't have enough time to go into this in depth, but see if the problem is affected by increasing the number of mbufs.