Date: Thu, 19 Jan 2006 16:16:13 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Ganbold <ganbold@micom.mng.net> Cc: freebsd-stable@FreeBSD.org Subject: Re: fxp0: device timeout and sk0: watchdog timeout problems Message-ID: <20060119071613.GB44245@rndsoft.co.kr> In-Reply-To: <7.0.0.16.2.20060119141302.04354d70@micom.mng.net> References: <7.0.0.16.2.20060118090616.04209af8@micom.mng.net> <20060118015515.GB39792@rndsoft.co.kr> <7.0.0.16.2.20060118102336.03fbcef8@micom.mng.net> <20060118023646.GA40276@rndsoft.co.kr> <7.0.0.16.2.20060119141302.04354d70@micom.mng.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 19, 2006 at 02:14:13PM +0800, Ganbold wrote: > I have same problem even after updating the sk code to the latest: > > Jan 19 12:58:53 gw kernel: fxp0: device timeout > Jan 19 12:59:10 gw kernel: sk0: watchdog timeout > Jan 19 12:59:10 gw kernel: sk0: link state changed to DOWN > Jan 19 12:59:20 gw kernel: fxp0: device timeout > Jan 19 12:59:52 gw kernel: fxp0: device timeout > Jan 19 13:00:23 gw kernel: fxp0: device timeout > Jan 19 13:00:29 gw kernel: sk0: watchdog timeout > Jan 19 13:00:52 gw kernel: fxp0: device timeout > Jan 19 13:01:05 gw kernel: sk0: watchdog timeout > Does interface down and up help your situation? It would be great to know what mwchan is used if your application was blocked. Would you try another onboard NIC with fxp to narrow down the issue? Since it's hard to reproduce the problem on my system I need more information. Would you show me more information for your network configuration and how to reproduce it? -- Regards, Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060119071613.GB44245>