From owner-freebsd-stable@FreeBSD.ORG  Fri Feb  7 16:22:31 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 7448288A
 for <freebsd-stable@freebsd.org>; Fri,  7 Feb 2014 16:22:31 +0000 (UTC)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com
 [IPv6:2001:470:88e6:3::232])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2FEA31E20
 for <freebsd-stable@freebsd.org>; Fri,  7 Feb 2014 16:22:30 +0000 (UTC)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com
 [IPv6:2001:470:88e6:3::239]) (authenticated bits=128)
 by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s17GMStN062270;
 Fri, 7 Feb 2014 11:22:28 -0500 (EST)
 (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201402071622.s17GMStN062270@maildrop2.v6ds.occnc.com>
To: pyunyh@gmail.com
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: Any news about "msk0 watchdog timeout" regression in 10-RELEASE?
In-reply-to: Your message of "Fri, 07 Feb 2014 14:10:40 +0900."
 <20140207051040.GB1369@michelle.cdnetworks.com>
Date: Fri, 07 Feb 2014 11:22:28 -0500
Cc: freebsd-stable@freebsd.org, Vitaly Magerya <vmagerya@gmail.com>,
 curtis@ipv6.occnc.com
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Feb 2014 16:22:31 -0000


In message <20140207051040.GB1369@michelle.cdnetworks.com>
Yonghyeon PYUN writes:
 
> On Sat, Jan 25, 2014 at 09:50:50PM +0200, Vitaly Magerya wrote:
> > On 01/25/14 21:35, Curtis Villamizar wrote:
> > > When I'm no longer quite so swamped I'll look at this again.  It seems
> > > we are the only two reporting this problem.
> > 
> > To everyone reading this list: if you have an msk(4) NIC that doesn't
> > work on 10-RELEASE, now is the time to speak up.
> > 
> > > Please send lines of these form from dmesg:
> > > 
> > >   mskc0: <Marvell Yukon 88E8057 Gigabit Ethernet> port 0xe800-0xe8ff
> > >   mem 0xfebfc000-0xfebfffff irq 19 at deviceD 0.0 on pci2
> > > 
> > >   msk0: <Marvell Technology Group Ltd. Yukon Ultra 2 Id 0xba Rev 0x00>
> > >   on mskc0
> > > 
> > > That may indicate we have very similar chips.  If not, this msk
> > > problem may be more widespread.
> > 
> > Mine goes like this:
> > 
> >   mskc0: <Marvell Yukon 88E8040 Fast Ethernet> port 0x2000-0x20ff
> >   mem 0xf0200000-0xf0203fff irq 18 at device 0.0 on pci9
> > 
> >   msk0: <Marvell Technology Group Ltd. Yukon FE+ Id 0xb8 Rev 0x00>
> >   on mskc0
> > 
> > Pretty different chips it seems.
>  
> Please try r261577.


Just update sys/dev/msk, or do I need more than that?

Curtis