On Tue, May 28, 2013 at 03:34:00PM -0400, Michael L. Squires wrote: > Short answer: it didn't work.
[...] > Patch did not solve the problem on the home NAT box. I'll try it on the Hmm, I can't reproduce it on my box. I double checked every possible controller initialization sequences in driver but couldn't find a clue. Let you know if I manage to narrow down the issue. > second 1U box at work tomorrow. > > I applied the patch (see below) and recompiled/reinstalled world. > Rebuilding kernel should be enough. > root@familysquires:/usr/src/sys/dev/fxp # uname -a > FreeBSD familysquires.net 8.4-RELEASE FreeBSD 8.4-RELEASE #54: Sun May 26 > 22:56:19 EDT 2013 r...@familysquires.net:/usr/obj/usr/src/sys/NEWGATE > i386 > > drwxr-xr-x 236 root 3584 May 28 10:28 ../ > -rw-r--r-- 1 root 95366 May 28 10:28 if_fxp.c > -rw-r--r-- 1 root 94968 Mar 28 09:04 if_fxp.c.orig > -rw-r--r-- 1 root 15638 Mar 28 09:04 if_fxpreg.h > -rw-r--r-- 1 root 8717 Mar 28 09:04 if_fxpvar.h > -rw-r--r-- 1 root 23009 Mar 28 09:04 rcvbundl.h > > One immediate difference in behavior is that without the modified rc.conf > the box was unable to use ntp to the outside world; it eventually sync'd on > my internal ntp server. With the modified rc.conf the box immediately > sync'd to an ntp server in the outside world. > There is a side-effect of the rc.conf workaround. Parallel detection may or may not work and generally can result in duplex mismatch. _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
