From owner-freebsd-current@FreeBSD.ORG Tue Dec 2 11:00:04 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 DB3D31065679 for ; Tue, 2 Dec 2008 11:00:04 +0000 (UTC) (envelope-from subbsd@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by mx1.freebsd.org (Postfix) with ESMTP id 6415D8FC22 for ; Tue, 2 Dec 2008 11:00:04 +0000 (UTC) (envelope-from subbsd@gmail.com) Received: by ey-out-2122.google.com with SMTP id 6so1218653eyi.7 for ; Tue, 02 Dec 2008 03:00:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:reply-to:to:subject:date :user-agent:mime-version:content-type:content-transfer-encoding :content-disposition:message-id; bh=QwHghVQTwxSEw4GVuRQs9HN5hkW54I1EcwWyRfNu63g=; b=C5qdlCRZSB8RW1jD+T0UrSpzNiQxSsI5R3zdNpUFrcTsZVXWU6uijvUgpnDe+CMl3u Be6ZAEk9MKzFMgldgsii+T7zDUGhS+QOoguPV/8qzKoM7kvbinqhGMjjk6ZBw6Bx4lAb 16XrAd6E4iTZb24K42lPzkVkpzn/yZ6QZvXxg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; b=UkN97x81cvFi5OI/Z12csiMcEqgGaAlQzntDgdeLzZHhwoFNE4DI23X+wEXArrMgAy 9tjYZfzT29whBIX/VIlq84JSu7QulUYfPAMEor3rfdP3JnfXly+TMcFmMubcRgV2byzZ /wI7lvAOIVF8OE+8cnr2mFGAUKsZJhCR9XTLk= Received: by 10.86.60.14 with SMTP id i14mr7103318fga.70.1228215603114; Tue, 02 Dec 2008 03:00:03 -0800 (PST) Received: from oleg.net.nevosoft.ru ([195.182.128.54]) by mx.google.com with ESMTPS id 4sm3200074fge.50.2008.12.02.03.00.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 02 Dec 2008 03:00:02 -0800 (PST) From: Ole To: freebsd-current@freebsd.org, pyunyh@gmail.com Date: Tue, 2 Dec 2008 13:59:56 +0300 User-Agent: KMail/1.10.1 (FreeBSD/7.1-PRERELEASE; KDE/4.1.1; i386; ; ) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812021359.56698.subbsd@gmail.com> Cc: 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: subbsd@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 11:00:04 -0000 Hello Maillist, ifconfig ale0: ale0: flags=8843 metric 0 mtu 1500 options=319b ether 00:22:15:92:4f:a0 inet 172.32.1.51 netmask 0xffff0000 broadcast 172.32.255.255 media: Ethernet autoselect (100baseTX ) status: active I see, the problem is floating and in my case depend from type of remote port on ethernet cable. For example when connect my book (with ale0) to 1Gbit/s pc port (with FreeBSD- Current and Marvell card (msk driver)) i get ale0: could not disable Tx/Rx MAC(0x00000008)! ale0: DMA read error! -- resetting and flapping interface forever when traffic flow. when i connection ale0 to 100Mbit/s switch port or to 100Mbit/s PC (with Windows OS) through cross-over cable, ale0 work perfect without any warning. Currenlty i reproduce problem only with PC:msk<->PC:ale link. I try to collect more information for other situation. PS: PC with FreeBSD/msk driver working with other (!= ale0) link (to switch or to PC) is fine. > 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