From owner-freebsd-questions@FreeBSD.ORG Wed Sep 17 01:06:28 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A9E0BC89; Wed, 17 Sep 2014 01:06:28 +0000 (UTC) Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (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 723A2864; Wed, 17 Sep 2014 01:06:28 +0000 (UTC) Received: by mail-pa0-f41.google.com with SMTP id bj1so938738pad.14 for ; Tue, 16 Sep 2014 18:06:28 -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:content-transfer-encoding :in-reply-to:user-agent; bh=D81u4rSFHYDZa0TKVt+TMME4aaA0hbzPOtmcXJeHaY4=; b=BkX69iMAFoo9L0Q9+/sPyEqLH84w1bVwWOhnCop3aPoAFVvpSgZfTX8Ua6EKSKlv69 ZMAbmeS7h8Km9ukl0D9PcTva396aCg/HBKq055G3srZrkPTouab1fYMndPKMKu7ipyb1 rH7QnCSZ32bPoQsjEME1kmOGeKSCqDUNbapeVf7tO1m6SjCZUvc3Rw1yvEb8CQpKAo93 XywURaqNgOR4ho/+yfI1mKVFlBVb56QlJpCk30QH+fMBdfvag4YLmOdWIsfqOQV+5Q2k +y6hAm70eEvU4mlAjvpFZqt8zlekK/BucbVc19x1NycvprJVvlQDj87Y+IbRZb9ApC5P 2Naw== X-Received: by 10.68.103.4 with SMTP id fs4mr55760656pbb.58.1410915987979; Tue, 16 Sep 2014 18:06:27 -0700 (PDT) Received: from pyunyh@gmail.com ([106.247.248.2]) by mx.google.com with ESMTPSA id fl15sm15162566pdb.92.2014.09.16.18.06.23 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 16 Sep 2014 18:06:26 -0700 (PDT) From: Yonghyeon PYUN X-Google-Original-From: "Yonghyeon PYUN" Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 17 Sep 2014 10:06:14 +0900 Date: Wed, 17 Sep 2014 10:06:14 +0900 To: Jim Thompson Subject: Re: jme interface bounces up and down, up and down.... Message-ID: <20140917010614.GB1102@michelle.fasterthan.com> Reply-To: pyunyh@gmail.com References: <201409141629.KAA29705@mail.lariat.net> <20140915060819.GA967@michelle.fasterthan.com> <201409151447.IAA08325@mail.lariat.net> <20140916083749.GA988@michelle.fasterthan.com> <201409161727.LAA25854@mail.lariat.net> <201409162353.RAA00829@mail.lariat.net> <27534E06-CC9B-4A4D-8A7A-9C68ECB760BC@netgate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <27534E06-CC9B-4A4D-8A7A-9C68ECB760BC@netgate.com> User-Agent: Mutt/1.4.2.3i Cc: Brett Glass , questions@freebsd.org, net@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2014 01:06:28 -0000 On Tue, Sep 16, 2014 at 07:59:18PM -0500, Jim Thompson wrote: > > > On Sep 16, 2014, at 6:53 PM, Brett Glass wrote: > > > > At 05:27 PM 9/16/2014, Chris Hill wrote: > > > >> On Tue, 16 Sep 2014, Brett Glass wrote: > >> > >>> So, what is the best solution? I cannot throw out the machine, and > >>> because I am using a VLAN switch to multiplex the port to three LANs > >>> I do not want to reduce the speed to 100 Mbps. Ideas? > >> > >> The man page mentioned says that if "the link partner enabled the IEEE 802.3az Energy Efficient Ethernet feature, the controller will not be able to establish a 1000baseT link." Maybe disable 802.3az on that port, if you can. Just a thought. > > > > It's a Netgear "green" switch, model GS105E. It has no way to disable 802.3az. > > The linux jmebp-1.0.8.5 driver from the JMicron website > > ftp://driver.jmicron.com.tw/Ethernet/Linux/jmebp-1.0.8.5.tar.bz > > provides a workaround for the issue. It adds the delay_time module parameter, which causes the network card to attempt a fall back to 100 mbps after it cannot connect for several seconds (by default 11). With this, link detection “works”, but the connection is 100Mbps. This is likely the reason the "problem didn't seem to occur with the bundled Linux distro.” > I recall the workaround was suggested by the Vendor but I didn't incorporate it into the driver due to other reasons. The end result is the same if users can manually reduce the speed to 100Mbps.