Date: Wed, 25 Jan 2006 11:27:35 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Ganbold <ganbold@micom.mng.net> Cc: freebsd-stable@FreeBSD.org Subject: Re: Marvell/SysKonnect YukonII source code available Message-ID: <20060125022735.GB11296@rndsoft.co.kr> In-Reply-To: <7.0.0.16.2.20060125101216.048f01c8@micom.mng.net> References: <43D5FF19.7090903@freebsd.org> <20060125015511.GA11296@rndsoft.co.kr> <7.0.0.16.2.20060125101216.048f01c8@micom.mng.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 25, 2006 at 10:15:11AM +0800, Ganbold wrote: > At 09:55 AM 1/25/2006, you wrote: > >Btw, new sk(4) is availabe at the following URL. Due to lack of > >documentation it doesn't support YukonII yet. > >http://people.freebsd.org/~yongari/sk/if_sk.c > >http://people.freebsd.org/~yongari/sk/if_skreg.h > > Pyun, > > I'm confused, I got drivers dated back Jan 19, however above are dated Jan > 17. > And I'm still getting: > > Jan 24 15:30:40 gw kernel: sk0: watchdog timeout > Jan 24 15:30:40 gw kernel: fxp0: device timeout > > errors. > > Ganbold > Did you use expeimental code in http://people.freebsd.org/~yongari/sk/sk_test/ ? If the driver still emit "watchdong timeout" I have no idea atm. I've never met such errors but I suffered from mbuf cluster leak on CURRENT. I believe the leak comes from kernel not sk(4) as it also happens em(4) on i386 SMP. When you see the error would you check mbuf status with netstat(1)? -- Regards, Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060125022735.GB11296>