Date: Tue, 07 Nov 2006 14:52:51 -0700 From: Scott Long <scottl@samsco.org> To: Jack Vogel <jfvogel@gmail.com> Cc: Clayton Milos <clay@milos.co.za>, freebsd-stable@freebsd.org, ke han <ke.han@redstarling.com> Subject: Re: em driver testing Message-ID: <45510033.7010102@samsco.org> In-Reply-To: <2a41acea0611071304n4fae1751ic462a58b45825bf2@mail.gmail.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> <2a41acea0611071304n4fae1751ic462a58b45825bf2@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jack Vogel wrote: > On 11/7/06, Clayton Milos <clay@milos.co.za> 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. > > > I'm not sure what it is, but the fact that a variety of nic drivers > are having this > same problem indicates that something changed in the if_timer and its > caller, someone knowing that subsystem would be better qualified to > say what. > > The other drivers should do the same thing that em did, and stop using > the net layer timer :) > > Jack I think it's more that the if_em driver watchdog was insulating the if_xl driver. Once the if_em component was removed, the if_xl driver was the next in line to be a victim. So yes, like you say, all of the drivers need to be fixed. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45510033.7010102>