From owner-freebsd-current@FreeBSD.ORG Mon Jun 13 01:49:43 2005 Return-Path: X-Original-To: freebsd-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 4A94016A41C for ; Mon, 13 Jun 2005 01:49:43 +0000 (GMT) (envelope-from pquerna@apache.org) Received: from utopia.in.force-elite.com (force-elite.com [216.255.199.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5DFA43D4C for ; Mon, 13 Jun 2005 01:49:42 +0000 (GMT) (envelope-from pquerna@apache.org) X-AuthUser: chip@force-elite.com Received: from [10.0.0.41] (10.0.0.41:2274) by utopia.in.force-elite.com with [XMail 1.17 (Linux/Ix86) ESMTP Server] id for from ; Sun, 12 Jun 2005 18:49:42 -0700 Message-ID: <42ACE639.8030509@apache.org> Date: Sun, 12 Jun 2005 18:49:45 -0700 From: Paul Querna User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: q@onthenet.com.au Subject: Panic with nve 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, 13 Jun 2005 01:49:43 -0000 Using the 6.0-CURRENT June 2nd Snapshot, I get a panic pretty quickly when using an original NForce 1 MCP Network Card(new nve driver). This has happened while I was running sysinstall via pxeboot, and starting a ftp install. This is what I copied from the screen, omitting some things later in the stack trace: anic: nve_ifstart: attempted use of a free mbuf! cpuid = 0 KBD: enter: panic [thread pid 35 tid 100022 ] Stopped at kdb_enter+0x2b db>trace kdb_enter(x0855c9c) at kdb_enter 0x2b panic(c082ad05,c08154dc,c1a388fc,c1a38800,ce7ebc80) at panic+0x127 nve_ifstart(c1a38800,) at nve_ifstart+0x366 if_start(c1a38800) at if_start+0x7b ether_output_frame(c1a38800,v1b35300,0,0,0) at ether_output_frame+0x1d9 ether_output(c1a38800,v1b35300,,c1ab67d0,c1ba8c60,v1b58b00) at ether_output+0x384 ip_output() tcp_output() ip_input() netisr_processqueue() swi_net(0) .... I don't have the gear locally to setup a serial console, so I am hoping this is enough to give someone a clue. It looks easy to reproduce, and I am happy to provide more information if needed. I did find a mention of a similar panic back in October of 2004, but it was for the fxp driver: http://lists.freebsd.org/pipermail/freebsd-net/2004-October/005222.html Thanks, -Paul Querna