From owner-freebsd-net@FreeBSD.ORG Wed Aug 23 18:46:11 2006 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 E9ACC16A4DA; Wed, 23 Aug 2006 18:46:11 +0000 (UTC) (envelope-from prvs=julian=383e896f4@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACB5A43D55; Wed, 23 Aug 2006 18:46:09 +0000 (GMT) (envelope-from prvs=julian=383e896f4@elischer.org) Received: from unknown (HELO [10.251.18.229]) ([10.251.18.229]) by a50.ironport.com with ESMTP; 23 Aug 2006 11:46:08 -0700 Message-ID: <44ECA26F.2080204@elischer.org> Date: Wed, 23 Aug 2006 11:46:07 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gleb Smirnoff References: <20060823161649.GE76666@cell.sick.ru> In-Reply-To: <20060823161649.GE76666@cell.sick.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: brad@openbsd.org, David Christensen , oleg@freebsd.org, net@freebsd.org Subject: Re: bge(4) one packet wedge 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: Wed, 23 Aug 2006 18:46:12 -0000 Gleb Smirnoff wrote: > Colleagues, > > I've faced a problem in bge(4) when a single packet is in the RX >ring, but it isn't noticed by the driver. A reception of a packet >triggers interrupt and both packets are processed - an old one >and the new one. > > To reproduce the problem you need to run netperf (from ports >collection): netserver on another host (10.0.0.1) and netperf on >the host, where tested bge(4) is installed - 10.0.0.2. No traffic >except netperf's should flow through this NIC, or the problem won't >be reproduced! > > So, I run netperf client and simultaneously tcpdump on the >another host. After few seconds there is a wedge. The last packet >seen on 10.0.0.1 is the packet sent by 10.0.0.1 to 10.0.0.2. However >it isn't seen on 10.0.0.2. > >Ok, let's look at the receive ring: > >(kgdb) p $sc->bge_rx_saved_considx >$14 = 51 >(kgdb) p $sc->bge_ldata.bge_status_block->bge_idx[0].bge_rx_prod_idx >$15 = 51 > >Looks like there is nothing to process. > >However, if I run 'ping -c 1 10.0.0.2' I will get an interrupt and read >two packets: first the old packet, and then recently > Is there any IPMI set up on the machine? is it possible that some extra circuitry involved with ipmi is holding the packet? >sent ping. > > >