dc0 collisions in -current

From: Mike Silbersack (silby_at_silby.com)
Date: 12/29/03

  • Next message: Stefan Walter: "pcm(4) stopped working for <Intel ICH4 (82801DB)>" 
    Date: Mon, 29 Dec 2003 14:23:51 -0600 (CST)
To: Ryan Sommers <ryans@gamersimpact.com>

    I haven't read the thread in question through completely, but I just want
    to make you guys aware that -current's if_dc has a bug where it will
    report _false_ collisions on many network cards.

    Example from one of my systems:

    dc0 1500 <Link#2> 00:20:78:0f:a0:a6 10307782 0 15428017 0 827213
    dc0 1500 10.1.1/24 10.1.1.6 10304908 - 15428012 - -

    However, I am not aware of it producing any output error messages, so that
    may be a real problem.

    Also, "dc0: TX underrun -- increasing TX threshold" is normal, you will
    see that message a few times once you start putting the system under
    network load until it finds a good TX threshold. Nothing to worry about
    there.

    So, as I said, I did not read the entire thread, so I'm not sure if a real
    problem is occuring for you guys or not; just make sure that you aren't
    chasing a ghost.

    Mike "Silby" Silbersack
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Stefan Walter: "pcm(4) stopped working for <Intel ICH4 (82801DB)>"