Date: Mon, 7 Dec 2009 12:56:18 -0800 From: Chris Cowart <ccowart@timesinks.net> To: Pyun YongHyeon <pyunyh@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: msk link problems on 8.0 Message-ID: <20091207205618.GC88840@marvin.timesinks.net> In-Reply-To: <20091207201737.GF1366@michelle.cdnetworks.com> References: <20091207021746.GA86085@marvin.timesinks.net> <20091207185606.GD1366@michelle.cdnetworks.com> <20091207194350.GB88840@marvin.timesinks.net> <20091207201737.GF1366@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--da4uJneut+ArUgXk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Pyun YongHyeon wrote: > On Mon, Dec 07, 2009 at 11:43:50AM -0800, Chris Cowart wrote: >> Pyun YongHyeon wrote: >>> On Sun, Dec 06, 2009 at 06:17:46PM -0800, Chris Cowart wrote: >>>> On a related note, last night, when the system did boot, I would >>>> also run into a problem where the following message would be logged: >>>> "msk0: Rx FIFO overrun!". Once logged, the NIC seemed to be >>>> completely wedged >>>=20 >>> At least this indicates you didn't use latest msk(4) in HEAD because >>> the message was removed there. >>=20 >> Sorry I was unclear on the chronology; I was seeing this behavior before >> I honed in on the link-state problem and built the msk(4) from HEAD. >>=20 >>>> and unusable. Doing ifconfig down/up did not help things. At the >>>> time, I hadn't discovered the physical down/up workaround, so I >>>> can't speak to whether that would have helped (and this error >>>> condition hasn't recurred (knock on wood)). I don't know if >>>> the issues are related or >>>=20 >>> I think it would be different issue, let's fix link state issue first. >>=20 >> I think you're right that there are two issues here; I think I may have >> confused matters a little by intertwining my observations from both of >> them. Given that I've tried that patch and experienced the same link >> state behavior, is there something else I can try? >>=20 >=20 > Hmm, that's strange. Let me summarize your issue. > You see "Waiting 30s for the default route interface" and you have > to wait until you finally got default route interface? Or does it > always time out for the default route interface and you always have > to wait 30 seconds? > Can msk(4) get an IP address via DHCP? I am seeing the "Waiting 30s for the default route interface" consistently on boot. If I take no action, the NIC will not work. The 30s will timeout, and the boot will continue without a default route interface.=20 Once I get a shell, I run `ifconfig msk0` and see: | media: Ethernet autoselect (1000baseT <full-duplex,flag0,flag1>) | status: active $ sudo tcpdump -nei msk0 not ether src host 00:16:cb:ae:5b:1f No packets will be captured though the broadcast domain is quite active (I'm excluding the ones that I'm attempting to send; I do see those). At this point, I physically disconnect and reconnect the cable. Immediately, the tcpdump begins showing output.=20 Instead of allowing the "Waiting 30s" timer to expire, I can disconnect/reconnect the cable during the boot process. If I do that, the interface begins working, dhclient does its business, and the system boots fine. A day later, it's still working. --=20 Chris Cowart http://www.timesinks.net/ --da4uJneut+ArUgXk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iQIcBAEBAgAGBQJLHWvxAAoJEGdJs2Q92uldoO8P/3Q5ZK68f0h3HShfLktW7o4c +vWeY2vluG93H3ktfj1m1rmOpmkSy7A1Gh+oxKV4J/rMtXCNt/EwKXQcyA5ofmZm RlShAK76uxdW+tDKIxQ/F8DvzWKako89eIqJfnsdSp1LEfBTSQQPK6gLY0C0TJ44 rE+dJhKExDikCztJ7Cz+SgyCnTkv3CDIVkUKeIUy7v5dO1SG7+cPH4eBAcvHDi1o 8MuyBINCCFPRUiQpk541uP9nWz9ohLRY/ErDXkpA67KUJm49gG90YQ6fqArxKPWs NNyQe0EEAY75BD9VbG5a+Bn5EM4sHlVEP689GoumFFavxN9mrhN6QmJFpmrWQyRf CctsxFFmjCR6nIlzBojT1CUbvhR7nvHHxTDBq9JKSyuLk1PBUQWE2BcmfoSPttSe uKDAV2Cw+LqRxlZE/YobwgZGhb8SN5KZ9GCKSSJtdxvPAbJlIGRP6Gelb+1bbGoX 9+GAPEC9hnrpvbIPlDlyYSosd80vha1/PDgEhkuvuKAWtYC8MsQgjZCwiPEQGh2/ UOXyaL7AjwylA1xaIYm6hYWHAvFQ0AW0jj+t9x9J564/LjUVV4+T2hYAzDXPgmYZ wpH4VoVo7qYtTzHHxirccsTvLtVn97RiaQGab7lwnXnTEpwJFzPxLuAwP+7NTM1Q w8B/8t+au1PU/zNazpOP =QfZT -----END PGP SIGNATURE----- --da4uJneut+ArUgXk--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091207205618.GC88840>