From owner-freebsd-stable@FreeBSD.ORG Wed Apr 2 00:39:20 2014 Return-Path: Delivered-To: freebsd-stable@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 2FD6AD6A; Wed, 2 Apr 2014 00:39:20 +0000 (UTC) Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) (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 E7973FA8; Wed, 2 Apr 2014 00:39:19 +0000 (UTC) Received: by mail-pb0-f49.google.com with SMTP id jt11so10511052pbb.8 for ; Tue, 01 Apr 2014 17:39:19 -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=Gu+q8mteaHNquYTMkSgM9ak+Dqxi8ImabSIudIvom70=; b=JqCmpZ4evoeZB1X7ZNz58s43kQmpBrIGVoEgW9rnsX/UwVe+R/WLnzRjfNJK8sqUZu JhI1mZYPQ0MkFKK5IKLCKk6TukrrXWSORxtCnxrYQxthwCUeoWuJi6O5/rvzjnc9FbpI JjguSa8rW8kxR5Lbs4bR9aqq2LceKtdlKF5TiGlbq7VWKFP6kezqdRYisKfeemDvBdZJ n8cTyaVPbaW4czmu3GQNIeZP8/doGfqu976j9x+KOip0ooQbDR1ZhvACofl8WPM+DAyb k+EOVGFGJbpW+sVR5f93SPOnB94Mh/TOd81nzoMNLRJKc699TQA5YI0DgAaAFX0YWO3Y Peqw== X-Received: by 10.66.164.36 with SMTP id yn4mr34243512pab.25.1396399159559; Tue, 01 Apr 2014 17:39:19 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPSA id nx12sm1281627pab.6.2014.04.01.17.39.16 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 01 Apr 2014 17:39:18 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 02 Apr 2014 09:39:13 +0900 From: Yonghyeon PYUN Date: Wed, 2 Apr 2014 09:39:12 +0900 To: Chris H Subject: Re: miibus0: mii_mediachg: can't handle non-zero PHY instance 31 Message-ID: <20140402003912.GA2938@michelle.cdnetworks.com> References: <2598eeb4c68e23df0789e5e3e8f46d76.authenticated@ultimatedns.net> <20140331050002.GC1359@michelle.cdnetworks.com> <20140401065842.GA1364@michelle.cdnetworks.com> <1396384167.81853.210.camel@revolution.hippie.lan> <41917a9e67d0f4519df4b55f3aa6ebe3.authenticated@ultimatedns.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41917a9e67d0f4519df4b55f3aa6ebe3.authenticated@ultimatedns.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net , freebsd-stable , Ian Lepore X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Apr 2014 00:39:20 -0000 On Tue, Apr 01, 2014 at 01:40:58PM -0700, Chris H wrote: > > On Tue, 2014-04-01 at 13:19 -0700, Chris H wrote: > >> [...] > >> miibus0: on nfe0 > >> rlphy0: PHY 0 on miibus0 > >> rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow > >> rlphy1: PHY 1 on miibus0 > > [...]---big-snip--8<--- > >> miibus0: mii_mediachg: can't handle non-zero PHY instance 1 > >> > >> As you can see, it looks much the same. I have no idea what > >> I should do to better inform the driver/kernel how to better > >> handle it. Or is it the driver, itself? > >> > >> Thank you again, for your thoughtful response. > >> > >> --Chris > >> > > > > I think the way to fix a phy that responds at all addresses is to set a > > hint in loader.conf masking out the ones that aren't real, like so: > > > > hint.miibus.0.phymask="1" > > > > You might be able to set ="0x00000001" to make it more clear it's a > > bitmask, but I'm not sure of that. > > Thank you very much for the hint. I'll give it a shot. > Any idea why this is happening? I have 4 other MB's using the Nvidia > chipset, and the nfe(4) driver. But they don't respond this way. > If some nfe(4) variants badly behave in probing stage, this should be handled by driver. We already have too many hints and tunables and I don't think most users know that. In addition, adding additional NIC may change miibus instance number. Could you show me the output of 'kenv | grep smbios'?