From owner-freebsd-current@FreeBSD.ORG Thu Jul 5 08:41:54 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0895D106566B for ; Thu, 5 Jul 2012 08:41:54 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mail.digiware.nl (mail.ip6.digiware.nl [IPv6:2001:4cb8:1:106::2]) by mx1.freebsd.org (Postfix) with ESMTP id 948908FC0A for ; Thu, 5 Jul 2012 08:41:53 +0000 (UTC) Received: from rack1.digiware.nl (localhost.digiware.nl [127.0.0.1]) by mail.digiware.nl (Postfix) with ESMTP id 4BAE815343E; Thu, 5 Jul 2012 10:41:52 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.nl Received: from mail.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hEqXXWcCQKvg; Thu, 5 Jul 2012 10:41:51 +0200 (CEST) Received: from [192.168.10.67] (opteron [192.168.10.67]) by mail.digiware.nl (Postfix) with ESMTP id 9B219153433; Thu, 5 Jul 2012 10:41:51 +0200 (CEST) Message-ID: <4FF5534F.7050106@digiware.nl> Date: Thu, 05 Jul 2012 10:41:51 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: pyunyh@gmail.com References: <4FF41610.10402@digiware.nl> <20120706002930.GA1466@michelle.cdnetworks.com> In-Reply-To: <20120706002930.GA1466@michelle.cdnetworks.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 05 Jul 2012 11:14:20 +0000 Cc: FreeBSD Current Subject: Re: sk0 link bouncing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2012 08:41:54 -0000 On 2012-07-06 2:29, YongHyeon PYUN wrote: > On Wed, Jul 04, 2012 at 12:08:16PM +0200, Willem Jan Withagen wrote: >> Hi, >> >> I've got tons of these since I stopped loading the port with traffic.... >> It seems to have a pretty steady 27 min interval. >> >> Jul 4 07:00:05 freetest kernel: sk0: link state changed to DOWN >> Jul 4 07:00:05 freetest kernel: sk0: link state changed to UP >> Jul 4 07:27:21 freetest kernel: sk0: link state changed to DOWN >> Jul 4 07:27:21 freetest kernel: sk0: link state changed to UP >> Jul 4 07:53:48 freetest kernel: sk0: link state changed to DOWN >> Jul 4 07:53:48 freetest kernel: sk0: link state changed to UP >> Jul 4 08:21:16 freetest kernel: sk0: link state changed to DOWN >> Jul 4 08:21:16 freetest kernel: sk0: link state changed to UP >> Jul 4 08:48:10 freetest kernel: sk0: link state changed to DOWN >> Jul 4 08:48:11 freetest kernel: sk0: link state changed to UP >> Jul 4 09:13:38 freetest kernel: sk0: link state changed to DOWN >> Jul 4 09:13:38 freetest kernel: sk0: link state changed to UP >> Jul 4 09:39:06 freetest kernel: sk0: link state changed to DOWN >> Jul 4 09:39:06 freetest kernel: sk0: link state changed to UP >> >> Very recent 10-current install with std GENERIC kernel. >> FreeBSD freetest.digiware.nl 10.0-CURRENT FreeBSD 10.0-CURRENT #1: Sat >> Jun 30 09:35:43 UTC 2012 >> root@freetest.digiware.nl:/usr/obj/usr/src/sys/GENERIC amd64 >> >> The port is connected to a basic netgear 10/100/1000 switch with nothing >> modified in the config of that port. >> Other connections do not seem to suffer from disconnecting. >> >> Used the server to 'zfs send' a 360G backup to, and then it did not do >> anything like this, the port just stayed up. >> >> Suggestions where of what to look for this? > > Probably you have to implement link state change handler for > Marvell controller(i.e. sk_marv_miibus_statchg()). Locking for > MII access should be revisited too. > Sorry, don't have spare time to do that. I think I understand you comments. But I do not have the knowledge to do this. :( The board also has an msk0, which I'm now trying. Thanx, --WjW