Debugging em(4) driver

[Jack Vogel]

The stats changed quite a bit for 8.1, they are much more informative now,
and they can be collected from anywhere not just the console.

I don't quite understand what you are trying to do, debug an em problem
or just debug a problematic situation by using em??

Mike is right, the driver in HEAD has some significant fixes and would be
the best thing to use.

Jack


On Sat, Nov 13, 2010 at 7:53 PM, Mike Tancsa <mike at sentex.net> wrote:

> On 11/13/2010 9:35 PM, Patrick Mahan wrote:
> >
> >
> > On 11/13/2010 02:27 PM, Ryan Stone wrote:
> >> It looks to me that you're getting a ton of input drops.  That's
> >> presumably the cause of your issue.  You can get the em driver to
> >> print debug information to the console by running:
> >>
> >> # sysctl dev.em.3.stats=1
> >> # sysctl.dev.em.3.debug=1
> >>
> >> The output should be available in dmesg and /var/log/messages
> >>
> >> Hopefully that can shed some light on the nature of the drops.
> >
> > Ryan,
> >
> > Thanks for the tip.  But I see I forgot to mention this was FreeBSD 8.0.
> > The em(4) driver is actually the one found in FreeBSD 8.1 as we needed
> > the AltQ fixes.
> >
>
> Try grabbing the em drivers from HEAD.  They fixed a few bugs for me.
> You should be able to grab all of /usr/src/sys/dev/e1000 from HEAD and
> drop it in to RELENG_8 and compile
>
>        ---Mike
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>