From owner-freebsd-stable@FreeBSD.ORG Wed Jan 18 02:28:50 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78C0016A423 for ; Wed, 18 Jan 2006 02:28:50 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89ABB43D49 for ; Wed, 18 Jan 2006 02:28:49 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.60 (FreeBSD)) (envelope-from ) id 1Ez33m-000BuW-61; Wed, 18 Jan 2006 10:28:30 +0800 Message-Id: <7.0.0.16.2.20060118102336.03fbcef8@micom.mng.net> X-Mailer: QUALCOMM Windows Eudora Version 7.0.0.16 Date: Wed, 18 Jan 2006 10:28:43 +0800 To: pyunyh@gmail.com From: Ganbold In-Reply-To: <20060118015515.GB39792@rndsoft.co.kr> References: <7.0.0.16.2.20060118090616.04209af8@micom.mng.net> <20060118015515.GB39792@rndsoft.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-stable@FreeBSD.org Subject: Re: fxp0: device timeout and sk0: watchdog timeout problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jan 2006 02:28:50 -0000 At 09:55 AM 1/18/2006, you wrote: > > inet 127.0.0.1 netmask 0xff000000 > > > > I used new if_sk codes from Pyun YongHyeon but after 2 days I got > > same problem device timeout. > > fxp is also timing out and I don't know why. > > Any idea? > > > >If sk(4) is the cause of problem fxp wouldn't be affected. I guess so. But fxp also times out almost at same time as sk does. >Of course it's possible for sk(4) to corrupt kernel memory structure >but the possibility is low. While fixing sk(4) I pushed sk(4) to the >limit on sparc64. I never met such timeouts. > >atm I have no clue. How about updated sk(4)? >http://people.freebsd.org/~yongari/sk/if_sk.c >http://people.freebsd.org/~yongari/sk/if_skreg.h Is it new update? Because I used your update dated on Jan 12 2006. Is it newer than that? >Disabling sk(4) remedy your issue? There is another on-board pcn NIC, I will try if problem exists with sk driver. Ganbold. >-- >Regards, >Pyun YongHyeon