Date: Mon, 7 Dec 2009 11:43:50 -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: <20091207194350.GB88840@marvin.timesinks.net> In-Reply-To: <20091207185606.GD1366@michelle.cdnetworks.com> References: <20091207021746.GA86085@marvin.timesinks.net> <20091207185606.GD1366@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--l76fUT7nc3MelDdI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Pyun YongHyeon wrote:
> On Sun, Dec 06, 2009 at 06:17:46PM -0800, Chris Cowart wrote:
>> Having read the PR, I copied sys/dev/{msk,e1000} from HEAD into the
>=20
> I think the PR has nothing to do with this issue.
You're right. I found it when I was hunting for an explanation to the
hanging that seemed to come hand-in-hand with "Rx FIFO overrun" logs.
>> 8.0-p1 source tree and installed the resulting kernel. The behavior
>> did not change. If anyone has any alternative patching I could do,
>> either against 8.0 or HEAD for these drivers, I'd be more than
>> willing to try them out.
>=20
> There was a similar report on missing link state change and I think I
> committed fix. Are you sure you used latest if_msk.c(r199413) in HEAD?
> See if you have the following patch.
> http://svn.freebsd.org/viewvc/base/head/sys/dev/msk/if_msk.c?r1=3D199012&=
r2=3D199413&view=3Dpatch
I did get the file from HEAD, and I have verified that:
| if ((sc_if->msk_flags & MSK_FLAG_LINK) =3D=3D 0) |
msk_miibus_statchg(sc_if->msk_if_dev);
is in the patched kernel I built.
> > 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.
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.
> > 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.
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?
Thanks,
--=20
Chris Cowart
http://www.timesinks.net/
--l76fUT7nc3MelDdI
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)
iQIcBAEBAgAGBQJLHVr1AAoJEGdJs2Q92uldQboQAIVH1pzoqXDuKf3GMZlnFafc
ML0UPM5VH0YTijiro13TU1VL2zp5m0Qn5zpKbGUzmGeP7147mkjOT9PI11HJqixU
XlFxIDNl+icEun0G4BHc8Us5IjdioI7hJtKwXflFutBKhzg+ZWFcKHRrQHm8r+L0
J/pktvh9pQffVHN+J00F8rD+AiFhPoS6le3Bu+ZYY7R/p/ewObOgGWIDJiEjIgGI
umvFJDz3P4LY666L3miXEXTxIqIR6Pp85RrDsd8zBoD5/1MAPYuUV18qI+gN3+PJ
tLwy3XJYj/wSzoN7y9ffR8XqjVrJ9yqF0X30w/3P9MZq9NfVpp5vfoxOYp/Sre9M
d1vKUYlXyR7WXdeWg7K89oSB5ERX+yRnEkbZMoLav6QDWv7sh2YgUPt4BgBrYthC
habIoBNVPPV7gKu3oA4xEZHDas80BxBpYca2YcVmtdApjJRmA05ImYz1qDkYaB9q
DgPcb52dox/6mWuqcZePv0bNzF/bbgjQOTLsb69jQXlNm1N85RZn/yISE9TP51HP
+Xz0QTwWFwuHOLcibR45oDdoTLbzBAlUxjvVsQ4WPQtciguosINM+cI4YoCaAmAg
ExAF37v2tMCaoWSSK+62UztUcjchx9KLdpB1lQxnI2SRAcyZKTWi7/aRSKpyM6VJ
vtG0vI7AtqFp7m3nmf9C
=bNZV
-----END PGP SIGNATURE-----
--l76fUT7nc3MelDdI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091207194350.GB88840>