From owner-freebsd-current@FreeBSD.ORG Thu Jan 19 01:01:46 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2237106566C for ; Thu, 19 Jan 2012 01:01:46 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from sarah.protected-networks.net (sarah.protected-networks.net [IPv6:2001:470:1f07:4e1::1]) by mx1.freebsd.org (Postfix) with ESMTP id BE5A68FC15 for ; Thu, 19 Jan 2012 01:01:46 +0000 (UTC) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [202.12.127.84]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "Iain Butler", Issuer "RSA Class 2 Personal CA" (verified OK)) (Authenticated sender: imb@protected-networks.net) by sarah.protected-networks.net (Postfix) with ESMTPSA id 8AD5360DF; Wed, 18 Jan 2012 20:01:45 -0500 (EST) DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=RXjRw5bQ5TxogArY9LuhskvlEHjoz8Xoq+C0f0Rm8F6TW+tuN0k3IDi7lTtp3FAMk UhGeO3tqWyOVNFBTbL0Nvp8U2Wdi9+xCeMIBCgNJNl+aqHQFvDjqhFMsC0rMp8D Message-ID: <4F176B76.5010809@protected-networks.net> Date: Wed, 18 Jan 2012 20:01:42 -0500 From: Michael Butler User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:9.0) Gecko/20111223 Thunderbird/9.0 MIME-Version: 1.0 To: pyunyh@gmail.com References: <4F174C4F.2010302@protected-networks.net> <20120119005457.GE7469@michelle.cdnetworks.com> In-Reply-To: <20120119005457.GE7469@michelle.cdnetworks.com> X-Enigmail-Version: undefined OpenPGP: id=0442D492 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: Intermittent re0 phy failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2012 01:01:47 -0000 On 01/18/12 19:54, YongHyeon PYUN wrote: > On Wed, Jan 18, 2012 at 05:48:47PM -0500, Michael Butler wrote: >> At random intervals, when re0 is without any significant load; idle for >> lengthy periods, I see .. >> >> kernel: re0: PHY read failed >> last message repeated 4 times >> kernel: re0: link state changed to DOWN >> >> Unplugging the cable and re-inserting is sufficient to restore >> functionality. >> >> kernel is @ SVN r230276 >> >> Any ideas how to track this down? > > Knowing which kind of controller you have would be more helpful. > Show me both re(4)/rgephy(4) related message from dmesg and > 'devinfo -rv | grep rgephy' output. > As requested: dmesg: re0: port 0x2000-0x20ff mem 0xf0700000-0xf0700fff,0xf0200000-0xf0203fff irq 17 at device 0.0 on pci3 re0: MSI count : 1 re0: MSI-X count : 4 re0: attempting to allocate 1 MSI-X vectors (4 supported) msi: routing MSI-X IRQ 257 to local APIC 0 vector 51 re0: using IRQ 257 for MSI-X re0: Using 1 MSI-X message re0: ASPM disabled re0: Chip rev. 0x28000000 re0: MAC rev. 0x00000000 miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: OUI 0x00e04c, model 0x0011, rev. 2 rgephy0: 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 devinfo -rv | grep rgephy rgephy0 pnpinfo oui=0xe04c model=0x11 rev=0x2 at phyno=1 imb