Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Aug 2009 14:49:32 -0700
From:      Pyun YongHyeon <pyunyh@gmail.com>
To:        Ryan Rogers <webmaster@doghouserepair.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: nfe problem on 8.0-BETA2
Message-ID:  <20090812214932.GH55129@michelle.cdnetworks.com>
In-Reply-To: <4A679223.10604@doghouserepair.com>
References:  <d873d5be0907212218nde4167bw8e4e9951659b3729@mail.gmail.com> <4A66CFFC.30601@doghouserepair.com> <d873d5be0907220156j7cac4426mbee20918f62aea9@mail.gmail.com> <11167f520907220200m5dd456dfs2ad53d4b579b851b@mail.gmail.com> <4A66D587.9060001@haruhiism.net> <d873d5be0907220228vb172012ie6e7a7ef4b86f25c@mail.gmail.com> <11167f520907220326m430709efv7aa6c779f9511b78@mail.gmail.com> <20090722211600.GC1184@weongyo.local> <4A679223.10604@doghouserepair.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--ALfTUftag+2gvp1h
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Jul 22, 2009 at 03:26:43PM -0700, Ryan Rogers wrote:
> Weongyo Jeong wrote:
> >On Wed, Jul 22, 2009 at 05:26:07AM -0500, Sam Fourman Jr. wrote:
> >>>svn co svn://svn.freebsd.org/base/head
> >>>svn merge -c -193289
> >>>
> >>>Thereafter, in the root of the repo:
> >>>svn up
> >>>svn merge
> >>Confirmed, running the above set of commands fixed my 88E1116 nfe problem
> >>everything works as it should now. thanks guys for the help.
> >>
> >>Sam Fourman Jr.
> >>
> >>ps. svn was WAY faster than csup, I think I am going to use svn all
> >>the time now.
> >
> >I know that yongari@ knows what the problem is and the solution but he
> >could not access the internet right now due to relocation to USA.
> >
> >It looks he is busy with looking for house and etc...
> >
> >regards,
> >Weongyo Jeong
> >
> >
> >
> 
> Well, the good news is that r193289 was the only thing keeping my nics 
> from working.  I was able to update to current as of today and revert 
> that patch, and everything is working nicely now.  So I'll just keep my 
> eye on the commit logs and patch that up by hand whenever I need to 
> update until yongari is able to get situated.
> 

Would you try attached patch and let me know how it goes on your
box?

--ALfTUftag+2gvp1h
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="e1000phy.88E1116.diff"

Index: sys/dev/mii/e1000phy.c
===================================================================
--- sys/dev/mii/e1000phy.c	(revision 196104)
+++ sys/dev/mii/e1000phy.c	(working copy)
@@ -151,12 +151,13 @@
 		if (PHY_READ(sc, E1000_ESSR) & E1000_ESSR_FIBER_LINK)
 			sc->mii_flags |= MIIF_HAVEFIBER;
 		break;
+	case MII_MODEL_MARVELL_E1116:
 	case MII_MODEL_MARVELL_E1149:
 		/*
-		 * Some 88E1149 PHY's page select is initialized to
-		 * point to other bank instead of copper/fiber bank
-		 * which in turn resulted in wrong registers were
-		 * accessed during PHY operation. It is believed that
+		 * Some 88E1116 and 88E1149 PHY's page selection is
+		 * initialized to point to other bank instead of
+		 * copper/fiber bank which in turn resulted in accessing
+		 * wrong registers during PHY operation. It is believed
 		 * page 0 should be used for copper PHY so reinitialize
 		 * E1000_EADR to select default copper PHY. If parent
 		 * device know the type of PHY(either copper or fiber),

--ALfTUftag+2gvp1h--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090812214932.GH55129>