From owner-freebsd-current@FreeBSD.ORG Tue Dec 2 01:22:49 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EC801065670 for ; Tue, 2 Dec 2008 01:22:48 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.190]) by mx1.freebsd.org (Postfix) with ESMTP id 808878FC13 for ; Tue, 2 Dec 2008 01:22:48 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by ti-out-0910.google.com with SMTP id a1so1651918tib.3 for ; Mon, 01 Dec 2008 17:22:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=J8MXmNpwWpf5hsT+/Pd6VOzjOlGxpQmXoy78DzhcbLE=; b=Lv304RaIv7iyWcaZJzWShecyPTmcTumTsHm5be+uGiuPfcC8JMnQuNnhFU/xVNIRNK z973cgBTfJr3QtD1y6YDHRTz0qePHntaXxYrcRzd5OGa0AA/Pbbe7Ra7LXVA51w5ctw5 yfMrAOeBuCoxETQ//NiWQ9+NMOnErNCndoKgU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=f3K3PoB8I/Be6m/TQfnGF0g4iUXe+5DuGntSLS0o6OJi3p8C085j7DX46QZYHJBWdx n+/Yd/gaaGUQEcZ0E4vTujrCHIJm7BiPJqAhTzka4nEFZJubzBTiEun+afaUrpBjl5X4 rPUUEmX4BDZqF8Y4j3TTWPW96HxPZVZTViSb8= Received: by 10.110.42.17 with SMTP id p17mr8103592tip.35.1228180967183; Mon, 01 Dec 2008 17:22:47 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([211.53.35.84]) by mx.google.com with ESMTPS id y3sm2584146tia.6.2008.12.01.17.22.43 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 01 Dec 2008 17:22:45 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id mB21Mbl4005606 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Dec 2008 10:22:37 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id mB21MbXP005605; Tue, 2 Dec 2008 10:22:37 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 2 Dec 2008 10:22:37 +0900 From: Pyun YongHyeon To: Ole Vole Message-ID: <20081202012237.GB5306@cdnetworks.co.kr> References: <200812020102.04504.subbsd@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200812020102.04504.subbsd@gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: ale driver on asus eeepc 901 could not disable Tx/Rx under traffic flow X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2008 01:22:49 -0000 On Tue, Dec 02, 2008 at 01:02:04AM +0300, Ole Vole wrote: > Hello Maillist, > > Im using FreeBSD-CURRENT (from 01122008 snap from cvs) and got looped notice > in dmesg buffer when LAN Ethernet generate some traffic: > .. > ale0: could not disable Tx/Rx MAC(0x00000008)! > ale0: DMA read error! -- resetting > .. > ale0: could not disable Tx/Rx MAC(0x00000008)! > .. > with flapping interface (link going to down and back up). > Hmm, there was similiar report but I couldn't reproduce this on my box. In fact I'm out of idea why it happens. Since I have no access to datasheet I'm not sure what can be done at the moment. Even a developer in Atheros answered that changing mainboard would be the first step to diagnose the issue. :-( > ifconfig ale0 -txcsum -rxcsum -tso and forcing link for media 10BaseT/UTP is > in vain. > There are a couple of magic values related with PHY in Linux driver which I didn't want to include as I don't understand what it does. Do you use 10baseT media? Would you show me the output of "ifconfig ale0"? > Under small traffic flow ale0 work is fine without errors. Somebody meet with > like similar prombel on Asus eee pc 901 ? Thanks Anyway, I'll let you know if I mange to find a clue to the issue. -- Regards, Pyun YongHyeon