From owner-freebsd-net@freebsd.org Wed Jun 14 15:42:44 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6995B94D28 for ; Wed, 14 Jun 2017 15:42:44 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B08F168E7E; Wed, 14 Jun 2017 15:42:44 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 5516A260858; Wed, 14 Jun 2017 17:42:42 +0200 (CEST) Subject: Re: axge0 and AX88179 To: syrinx@freebsd.org, Tom Huerlimann Cc: "freebsd-net@FreeBSD.org" References: <008701d2d585$f1977f90$d4c67eb0$@thuinformatik.ch> <2248eb55-c402-cdb9-2648-986a0ed9663a@selasky.org> <00f201d2d593$734c6160$59e52420$@thuinformatik.ch> From: Hans Petter Selasky Message-ID: <43b6b5de-1c36-bc16-1472-001e48184fdc@selasky.org> Date: Wed, 14 Jun 2017 17:40:38 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Jun 2017 15:42:45 -0000 Hi Tom, Thanks for shipping me your device. I've now done some basic tests and your device shows varying results. When connecting it to a GBit capable ethernet port using a short cable, it ends up negotiating 10MBit link speed, whilst connecting to another other port, 1Gbit link speed. When connecting another such device using the same chip and phy and everything, only a different PCB layout, 1GBit/s is always negotiated. Running a simple back2back iperf test gives me: iperf -i 1 -P4 -c 1.1.1.1 ------------------------------------------------------------ Client connecting to 1.1.1.1, TCP port 5001 TCP window size: 32.8 KByte (default) ------------------------------------------------------------ [ 3] local 1.1.1.2 port 20458 connected with 1.1.1.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0- 1.0 sec 81.4 MBytes 683 Mbits/sec [ 3] 1.0- 2.0 sec 86.2 MBytes 724 Mbits/sec [ 3] 2.0- 3.0 sec 86.2 MBytes 724 Mbits/sec [ 3] 3.0- 4.0 sec 86.4 MBytes 725 Mbits/sec [ 3] 4.0- 5.0 sec 86.2 MBytes 724 Mbits/sec [ 3] 5.0- 6.0 sec 86.4 MBytes 725 Mbits/sec [ 3] 6.0- 7.0 sec 86.0 MBytes 721 Mbits/sec [ 3] 7.0- 8.0 sec 86.4 MBytes 725 Mbits/sec [ 3] 8.0- 9.0 sec 86.1 MBytes 722 Mbits/sec [ 3] 9.0-10.0 sec 86.1 MBytes 722 Mbits/sec [ 3] 0.0-10.0 sec 858 MBytes 719 Mbits/sec 1) Can you try to override the link speed negotiated: ifconfig ueX media 100baseTX mediaopt full-duplex 2) Can you try to enable flowcontrol: ifconfig ueX media autoselect mediaopt flowcontrol 3) The full list of medias accepted is available by entering: ifconfig -m ueX If none of the above helps, I'm afraid your device might suffer from an electrical design problem. --HPS