Date: Sat, 13 Nov 2010 22:53:08 -0500 From: Mike Tancsa <mike@sentex.net> To: Patrick Mahan <mahan@mahan.org> Cc: freebsd-net@freebsd.org Subject: Re: Debugging em(4) driver Message-ID: <4CDF5D24.5000801@sentex.net> In-Reply-To: <4CDF4AE6.5070507@mahan.org> References: <4CDF09BD.3050509@mahan.org> <AANLkTikiELuivohd7CYQ51rAsNur%2B1Kovqf%2B9Pq4X2M8@mail.gmail.com> <4CDF4AE6.5070507@mahan.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CDF5D24.5000801>