From owner-freebsd-current@FreeBSD.ORG  Wed Dec 24 05:42:18 2008
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id AAEE71065673
	for <current@freebsd.org>; Wed, 24 Dec 2008 05:42:18 +0000 (UTC)
	(envelope-from ianf@clue.co.za)
Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net
	[41.161.16.135])
	by mx1.freebsd.org (Postfix) with ESMTP id 48E488FC1D
	for <current@freebsd.org>; Wed, 24 Dec 2008 05:42:17 +0000 (UTC)
	(envelope-from ianf@clue.co.za)
Received: from [41.241.101.159] (helo=clue.co.za)
	by inbound01.jnb1.gp-online.net with esmtpsa
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63)
	(envelope-from <ianf@clue.co.za>)
	id 1LFMVb-0002WS-95; Wed, 24 Dec 2008 07:42:15 +0200
Received: from localhost ([127.0.0.1] helo=clue.co.za)
	by clue.co.za with esmtp (Exim 4.69 (FreeBSD))
	(envelope-from <ianf@clue.co.za>)
	id 1LFMVU-0001fB-Mz; Wed, 24 Dec 2008 07:42:08 +0200
To: pyunyh@gmail.com
From: Ian FREISLICH <ianf@clue.co.za>
In-Reply-To: <20081224021016.GF95088@cdnetworks.co.kr> 
References: <20081224021016.GF95088@cdnetworks.co.kr>
	<E1LF7Oc-000Djt-C1@clue.co.za> 
X-Attribution: BOFH
Date: Wed, 24 Dec 2008 07:42:08 +0200
Message-Id: <E1LFMVU-0001fB-Mz@clue.co.za>
Cc: current@freebsd.org
Subject: Re: msk(4) stops working. 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Dec 2008 05:42:18 -0000

Pyun YongHyeon wrote:
> On Tue, Dec 23, 2008 at 03:33:40PM +0200, Ian Freislich wrote:
>  > Hi
>  > 
>  > My msk0 (Marvell Yukon 88E8053 Gigabit Ethernet) will stop working
>  > and never recover after a burst in activity.  It produces the
>  > following messages:
>  > 
>  > Dec 23 15:24:16 apple kernel: msk0: watchdog timeout
>  > Dec 23 15:24:16 apple kernel: msk0: link state changed to DOWN
>  > Dec 23 15:24:19 apple kernel: msk0: link state changed to UP
>  > Dec 23 15:24:29 apple kernel: msk0: watchdog timeout (missed Tx interrupts
) -- recovering
>  > 
>  > pciconf -lvc:
>  > 
>  > mskc0@pci0:2:0:0:       class=0x020000 card=0x532111ab chip=0x436211ab rev
=0x22 hdr=0x00
>  >     vendor     = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
>  >     device     = '88E8053 Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Con
troller'
>  >     class      = network
>  >     subclass   = ethernet
>  >     cap 01[48] = powerspec 2  supports D0 D1 D2 D3  current D0
>  >     cap 03[50] = VPD
>  >     cap 05[5c] = MSI supports 2 messages, 64 bit enabled with 2 messages
>  >     cap 10[e0] = PCI-Express 1 legacy endpoint
>  > 
> 
> About 2-3 months ago I committed workaround for Yukon silicon bug.
> Do you use latest CURRENT?

Yes, this is on yesterday's sources.  It was better for a month or
so, but over the last month it's been really bad.  Now I can provoke
this condition in under 1 minute of uptime.

Ian

--
Ian Freislich