From owner-freebsd-questions@FreeBSD.ORG Tue Sep 16 08:38:05 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 53AE7B6D; Tue, 16 Sep 2014 08:38:05 +0000 (UTC) Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (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 1F9E0947; Tue, 16 Sep 2014 08:38:05 +0000 (UTC) Received: by mail-pa0-f44.google.com with SMTP id kx10so8357771pab.17 for ; Tue, 16 Sep 2014 01:38:02 -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=U5MQzLGn8TpjgYhKOnifjJSUBYGETx31AKJjFjS88B4=; b=B7nGGO05xD+nnIBlZ6UmW3TOOaf9g/0J3yZ2frKKNgG3EDRMvyffehgKG3fjJNLBtP ropMBemn6hV++XpySSqRozJhVn4MuG4e72jIW779L/diKbZEVz5JKBOQ0S3sZoSCFJl6 pFJUm0yWFQfjLF/UnW3OPU2eVXqNiB7GwoJAcHa3gH8RJFgYIiw03hCz8S1Bwjqqr7Ny G/covxW7rUoZJOkUKMDg53PDi8VJc29w0C5UqCc6XRoAzIKIRrMzB//RdpjYycgVsQkl V2KPlb+LcU8YOxkSAWustV2m1ZXbhSmz0zG3n4s0ASsDx6pxYH6dpn4Xiwl7Jtl2azV4 Qj2g== X-Received: by 10.66.243.6 with SMTP id wu6mr12779212pac.157.1410856682477; Tue, 16 Sep 2014 01:38:02 -0700 (PDT) Received: from pyunyh@gmail.com ([106.247.248.2]) by mx.google.com with ESMTPSA id uf6sm13987544pac.16.2014.09.16.01.37.58 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 16 Sep 2014 01:38:01 -0700 (PDT) From: Yonghyeon PYUN X-Google-Original-From: "Yonghyeon PYUN" Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 16 Sep 2014 17:37:49 +0900 Date: Tue, 16 Sep 2014 17:37:49 +0900 To: Brett Glass Subject: Re: jme interface bounces up and down, up and down.... Message-ID: <20140916083749.GA988@michelle.fasterthan.com> Reply-To: pyunyh@gmail.com References: <201409141629.KAA29705@mail.lariat.net> <20140915060819.GA967@michelle.fasterthan.com> <201409151447.IAA08325@mail.lariat.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201409151447.IAA08325@mail.lariat.net> User-Agent: Mutt/1.4.2.3i Cc: 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: Tue, 16 Sep 2014 08:38:05 -0000 On Mon, Sep 15, 2014 at 08:19:37AM -0600, Brett Glass wrote: > At 12:08 AM 9/15/2014, Yonghyeon PYUN wrote: > > >Would you show me the output of dmesg(jme(4) and jmphy(4) only) to > >know exact chip revision? > > Here you are. > > jme0: port > 0xec80-0xecff,0xe800-0xe8ff mem 0xfbffc000-0xfbfff > fff irq 18 at device 0.0 on pci1 > jme0: MSIX count : 8 > jme0: MSI count : 8 > jme0: attempting to allocate 1 MSI-X vectors (8 supported) > msi: routing MSI-X IRQ 256 to local APIC 0 vector 52 > jme0: using IRQ 256 for MSI-X > jme0: Using 1 MSIX messages. > jme0: PCI device revision : 0x0250 > jme0: Chip revision : 0x11 ^^^^^^^^^^^^^^^^^^^^^^^^^^ Initially I suspected you might have relatively new JMC25x controller but it seems you have early revision of the controller(JMC250 A2). Early revision of the controller has 1000baseT link establishment issue with 802.3az capable switches. The issue is explained in jme(4) man page. The known workaround is to manually set 100baseTX media. I recall you mentioned Linux had no problems so I wonder Linux was able to establish a 1000baseT link. In theory, the workaround could be implemented in driver but it is layering violation and will have to duplicate lots of work done by mii(4). > jme0: ethernet hardware address not found in EEPROM. > jme0: PHY is at address 1. > jme0: Read request size : 512 bytes. > jme0: TLP payload size : 128 bytes. > miibus0: on jme0 > jmphy0: PHY 1 on miibus0 > jmphy0: OUI 0x00d831, model 0x0021, rev. 1 > jmphy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, > 100baseTX-FDX, 100baseTX-FDX-flow, > 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, > 1000baseT-FDX-flow, 1000baseT-FDX > -flow-master, auto, auto-flow > jme0: bpf attached > jme0: Ethernet address: e0:cb:4e:54:23:ac > > I do not particularly like JMicron chips (their faulty SSD > controllers have cost me a lot of time and money), but that's I don't have experiences with other JMicron products so can't comment on SSD. JMC25x may not be world best gigabit ethernet controller but I was quite satisfied with its high performance and clear documentation and Vendor's support. > what's on the motherboard of this Asus. So, I need to find a way to > make it work. > > --Brett Glass >