Date: Tue, 07 Nov 2006 15:59:43 -0700 From: Scott Long <scottl@samsco.org> To: Mike Jakubik <mikej@rogers.com> Cc: Clayton Milos <clay@milos.co.za>, freebsd-stable@freebsd.org, Jack Vogel <jfvogel@gmail.com>, ke han <ke.han@redstarling.com> Subject: Re: em driver testing Message-ID: <45510FDF.201@samsco.org> In-Reply-To: <4550FE11.2060002@rogers.com> References: <68011C68-0962-4946-88E1-F36EE7C707DA@redstarling.com><20061106221219.GA66676@hugo10.ka.punkt.de><041201c701f9$37b2aed0$9603a8c0@claylaptop> <2a41acea0611061614n478efe77y82c0ebc2e1b01e19@mail.gmail.com> <001601c702af$9d355940$9603a8c0@claylaptop> <4550FE11.2060002@rogers.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Jakubik wrote: > Clayton Milos wrote: > >> Hi Jack >> >> >> I patched the driver and re-compiled the kernel and userland. >> >> All appears well with the em driver now. No more errors on it. >> I am getting watchdog timeouts on the xl driver now though. It was >> happenning before at the same time as the em ones. Now I've passed a >> lot of traffic on the em interface but the xl interface gets watchdog >> errors. The em interface still works fine but the xl one is no usable >> after this. > > > Has it not been established by someone that the problem is in freebsd > (scheduler iirc) and not the drivers themselves? This along with the > bge/bce wtachdog timeouts seems to confirm that. > Mike, If you have insight into the bce driver, I would highly appreciate if you would share it. Scott (the guy who fixed bce)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45510FDF.201>