From owner-freebsd-net@FreeBSD.ORG Mon Apr 20 07:04:14 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FC9D106566B for ; Mon, 20 Apr 2009 07:04:14 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 74D388FC14 for ; Mon, 20 Apr 2009 07:04:14 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id E173031E23F; Mon, 20 Apr 2009 03:04:13 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Mon, 20 Apr 2009 03:04:13 -0400 X-Sasl-enc: 0DzKFVB5DHUG19qEN3d8YaxT7520jtapGhomFch1vi0e 1240211053 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 129362BE64; Mon, 20 Apr 2009 03:04:12 -0400 (EDT) Message-ID: <49EC1E6B.5080601@incunabulum.net> Date: Mon, 20 Apr 2009 08:04:11 +0100 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Sergey Vavilov References: <5D267A3F22FD854F8F48B3D2B5238193397DC21622@IRVEXCHCCR01.corp.ad.broadcom.com> <49EC1612.9080706@vavilov.org> In-Reply-To: <49EC1612.9080706@vavilov.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-net@freebsd.org" Subject: Re: ae on freebsd7.1 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, 20 Apr 2009 07:04:14 -0000 Sergey Vavilov wrote: > > Hello guys! > Somebody overcame the problem with Attansic L2 > (http://www.attansic.com/english/products/index.html) fast ethernet > interface on Freebsd-7.1-RELEASE? > Thank you! I've seen this happen after a suspend/resume cycle on the ASUS EeePC 701. It looks pretty normal, that is, without getting into the nitty gritty of how the driver is queueing frames (no free time for that), and the card will begin operating again OK after the watchdog timeout. My understanding is that the design of this part isn't great. Whether these TX interrupt issues are down to the design or driver I don't know.