On Sun, Jun 09, 2013 at 12:21:37PM +0200, Alban Hertroys wrote: > I'm having an issue where my fxp0 interface keeps looping between DOWN/UP, > with dhclient requesting a lease each time in between. I think it's caused by > dhclient: > > solfertje # dhclient -d fxp0 > DHCPREQUEST on fxp0 to 255.255.255.255 port 67 > send_packet: Network is down > DHCPREQUEST on fxp0 to 255.255.255.255 port 67 > DHCPACK from 109.72.40.1 > bound to 141.105.10.89 -- renewal in 7200 seconds. > fxp0 link state up -> down > fxp0 link state down -> up > DHCPREQUEST on fxp0 to 255.255.255.255 port 67 > DHCPACK from 109.72.40.1 > bound to 141.105.10.89 -- renewal in 7200 seconds. > fxp0 link state up -> down > fxp0 link state down -> up > DHCPREQUEST on fxp0 to 255.255.255.255 port 67 > DHCPACK from 109.72.40.1 > bound to 141.105.10.89 -- renewal in 7200 seconds. > fxp0 link state up -> down > fxp0 link state down -> up > DHCPREQUEST on fxp0 to 255.255.255.255 port 67 > DHCPACK from 109.72.40.1 > bound to 141.105.10.89 -- renewal in 7200 seconds. > fxp0 link state up -> down > fxp0 link state down -> up > DHCPREQUEST on fxp0 to 255.255.255.255 port 67 > DHCPACK from 109.72.40.1 > bound to 141.105.10.89 -- renewal in 7200 seconds. > fxp0 link state up -> down > ^C > > In above test I turned off devd (/etc/rc.d/devd stop) and background dhclient > (/etc/rc.d/dhclient stop fxp0), and I still go the above result. There's > practically no time spent between up/down cycles, this just keeps going on > and on. > fxp0 is the only interface that runs on DHCP. The others have static IP's. > > Initially I thought the issue might be caused by devd, because I have both > ethernet and 822.11 type NICs (2x ethernet, 1x wifi) in that system. > > This is 9-STABLE from yesterday. > > Before, I had 9-RELEASE running on this system with the same config, and that > worked well.
And so what I predicted begins... The issue is described in the 8.4-RELEASE Errata Notes; the driver is using the same driver version as in stable/9, hence you're experiencing the same problem. See Open Issues: http://www.freebsd.org/releases/8.4R/errata.html No fix for this has been committed. It is still under discussions by multiple kernel folks as to where the fix should be applied (dhclient or the fxp(4) driver), because the changes made to dhclient (that tickle this bug) may actually affect more drivers than just fxp(4). You can start by reading the (extremely long but very informative) thread here. I do urge you to read all the posts, not skim them: http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073440.html http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/thread.html#73440 The only known workarounds at this time are: a) Cease use of DHCP; set a static IP in rc.conf, b) Try some of the patches mentioned within the above thread, specifically this one: http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073581.html The patch is for head (CURRENT) so it may not patch cleanly. If not, you can try to work the patch in yourself/by hand, or you can ask Yong-Hyeon or others for help. > I'm not sure it's related, but on the wireless interface I get alot of: > Jun 9 12:08:11 solfertje kernel: ath0: stuck beacon; resetting (bmiss count > 4) Absolutely 100% unrelated. That issue has been around for years, and the root cause varies tremendously. I discussed it back in February 2011: http://lists.freebsd.org/pipermail/freebsd-stable/2011-February/061700.html If you want to know how I solved that problem, I can tell you, but I'm certain you won't be happy to hear what I have to say. If you're concerned about this problem, please start another thread discussing it. I'm sure Adrian Chadd can provide you lots of insights, but most of them are already in his response to my above thread/post. > {snipping other stuff} -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | _______________________________________________ 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"
