From owner-freebsd-net@FreeBSD.ORG Mon Oct 3 09:16:21 2005 Return-Path: X-Original-To: net@freebsd.org Delivered-To: freebsd-net@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70C8716A41F for ; Mon, 3 Oct 2005 09:16:21 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5C0043D48 for ; Mon, 3 Oct 2005 09:16:18 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id j939GGWc055168 for ; Mon, 3 Oct 2005 13:16:16 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id j939GGiP055167 for net@freebsd.org; Mon, 3 Oct 2005 13:16:16 +0400 (MSD) (envelope-from yar) Date: Mon, 3 Oct 2005 13:16:15 +0400 From: Yar Tikhiy To: net@freebsd.org Message-ID: <20051003091615.GB50141@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i Cc: Subject: Easily fixable nge(4) issue? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Oct 2005 09:16:21 -0000 Folks, Has anybody looked at kern/86618? It looks like a piece of cake. Yuriy, the originator, tells that nge(4) panics his RELENG_6 and HEAD systems, but adding M_ZERO to contigmalloc() flags at one spot in if_nge.c is enough to get rid of the trouble (patch included.) Yuriy and yours truly were communicating over a VLAN issue and he drew my attention to the PR, but unfortunately I don't have any nge(4) hardware. If there is consensus that the problem description and fix are correct, I can back the solution with my commit bit. -- Yar