From owner-freebsd-net@FreeBSD.ORG Tue Sep 30 08:52:37 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4A0726CF for ; Tue, 30 Sep 2014 08:52:37 +0000 (UTC) Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1EBD85E2 for ; Tue, 30 Sep 2014 08:52:37 +0000 (UTC) Received: by mail-pd0-f173.google.com with SMTP id g10so1472088pdj.4 for ; Tue, 30 Sep 2014 01:52:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=saiXql5W3xRaOczmn9rWDpTf3/f9fNvilTvaXpjW9co=; b=ygiBwZbWn4wklmBoGrgPqpUMd27IZsjgRqVOxoTgwnHhc54OoMTM1tzNoIMNydKP39 HaF2P6wctA95gJ0kIhkUGI30gh+0Z/tL/Ex2z8UtE1hfOt28LGvk1qqDkX1V+4o3BGsD Bj9464yNNsNQoRcDmyAT4hTRPsn0QaNBUIAoxYunq+ui3KHhWS9PTfKhen9r9IltbHfG r3fnlD/H8yloaoIMSPeIKLmdJvfMD9Pg3+YN7vdhXC3aNLsE9+uJDDwfJ7Y19dv5iu4a hkaYT5wRTAtmb8cLSuUv4gQJrAehnZXCnqQYhkxcAeCZSHO1teOopbSs4PtoaOCE+wfY syvQ== X-Received: by 10.68.201.230 with SMTP id kd6mr69118014pbc.74.1412067156603; Tue, 30 Sep 2014 01:52:36 -0700 (PDT) Received: from pyunyh@gmail.com ([106.247.248.2]) by mx.google.com with ESMTPSA id hr1sm14515190pbb.17.2014.09.30.01.52.32 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 30 Sep 2014 01:52:35 -0700 (PDT) From: Yonghyeon PYUN X-Google-Original-From: "Yonghyeon PYUN" Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 30 Sep 2014 17:52:28 +0900 Date: Tue, 30 Sep 2014 17:52:28 +0900 To: Nils Beyer Subject: Re: [CFT] alc(4) QAC AR816x/AR817x ethernet controller support Message-ID: <20140930085228.GB969@michelle.fasterthan.com> Reply-To: pyunyh@gmail.com References: <20140930015741.GA2451@michelle.fasterthan.com> <20140930082053.4D9EFF8F@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140930082053.4D9EFF8F@hub.freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 08:52:37 -0000 On Tue, Sep 30, 2014 at 10:20:31AM +0200, Nils Beyer wrote: > Hi Yonghyeon, > > Yonghyeon PYUN wrote: > > I've added support for QAC AR816x/AR817x ethernet controllers. It > > passed my limited testing and I need more testers. You can find > > patches from the following URLs. [...] > > My NIC (System: "Dell Inc. Vostro 3460"): > ------------------------------------------------------------------------------- > none2@pci0:2:0:0: class=0x020000 card=0x05621028 chip=0x10911969 rev=0x10 hdr=0x00 > vendor = 'Atheros Communications Inc.' > device = 'AR8161 Gigabit Ethernet' > class = network > subclass = ethernet > ------------------------------------------------------------------------------- > > I've successfully applied both of your patches to 10.1-BETA3 (r272295) sources > and rebuilt the kernel. > Thanks for testing and detailed report. > Then I've connected a network cable and rebooted. I've got a link and performed > an "iperf" test. The results are really good: around 930 Mbit/s TX and 840 > Mbit/s RX. CPU load during that test: "70.75% kernel{alc0 taskq}". > Hmm, the RX performance number looks bad to me. You have to see more than 920Mbps. Could you show me the output of "pciconf -lcbv"? > Then I've dis- and reconnected the network cable. Unfortunately, I cannot get a > link anymore; it stays at: "status: no carrier" - tried "ifconfig down/up", re- > connecting the network cable several times, but it stays down. After another > reboot the link can be established again. > > That doesn't always happen. Sometimes I easily get a link again, sometimes not > and I need to reboot. > I thought I verified link lost condition before requesting test. After reading your mail, I was successfully reproduce it with engineering sample board. It seems when link lost time lasts long enough alc(4) fails to re-establish a link. I don't have idea how to address that at this moment but I'll let you know if I manage to find a clue. > If you need any further information or debugging, please let me know. For now, > I'm using "if_alc" as an unloadable module - in case the NIC stalls for some > reason; and am quite happy about being able to use that NIC now. > > Thanks for having added support for these NICs. > > > Because I'm not using CURRENT, I've replied to the "net" mailing list. I hope, > it is okay for you... > That's ok.