From owner-freebsd-stable@FreeBSD.ORG Mon May 8 07:41:34 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 296AA16A403 for ; Mon, 8 May 2006 07:41:34 +0000 (UTC) (envelope-from davidn@datalinktech.com.au) Received: from customer-domains.icp-qv1-irony8.iinet.net.au (customer-domains.icp-qv1-irony8.iinet.net.au [203.59.1.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6958743D45 for ; Mon, 8 May 2006 07:41:28 +0000 (GMT) (envelope-from davidn@datalinktech.com.au) Received: from 203-206-162-119.perm.iinet.net.au (HELO mail.datalinktech.com.au) ([203.206.162.119]) by customer-domains.icp-qv1-irony8.iinet.net.au with ESMTP; 08 May 2006 15:41:26 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.05,100,1146412800"; d="scan'208"; a="298816527:sNHT20672034" Received: from [192.168.4.232] ([192.168.4.232]) by mail.datalinktech.com.au with esmtp; Mon, 08 May 2006 17:41:23 +1000 id 00192A29.445EF623.00013165 Message-ID: <445EF61D.3060009@datalinktech.com.au> Date: Mon, 08 May 2006 17:41:17 +1000 From: David Nugent User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060406 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Gerhards References: <55123.193.138.135.19.1146922482.squirrel@sigma.interami.com> <1pqui3-v11.ln1@hmg.homeunix.net> In-Reply-To: <1pqui3-v11.ln1@hmg.homeunix.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: problem with sk? 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: Mon, 08 May 2006 07:41:34 -0000 Michael Gerhards wrote: >But by browsing through this list I found the thread "sk0: watchdog timeout" >and the problem described there is quite similiar to what I get here. So >perhaps this bug in the sk driver is also the cause for my trouble here?! > > Possibly (and even likely). It sounds like a very severe case of the same thing. I have been running a Marvell/Yukon 100mb adapter on FreeBSD RELENG_6 (the onboard NIC on an ASUS mb) and it does sometimes reset connections and dmesg shows the timeout maybe 2 or 3 times a day. The system is used in-house only and does not have high load (well, except for burst load when serving samba and NFS shared ${PORTSDIR}/distfiles, which overall works fine), so it is useable with the occasional but rarely noticeable glitch, like a connection pausing for 10-15 seconds then resuming. Currently running: FreeBSD 6.1-PRERELEASE #1: Thu Feb 23 09:03:11 EST 2006 ~ skc0: port 0xd400-0xd4ff mem 0xfeaf8000-0xfeafbfff irq 22 at device 5.0 on pci2 skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7) sk0: on skc0 I should mention that this is a vast improvement from a couple years ago under 5.0 and 5.1 it would attach the driver to the card but the interface was not functional at all. >Can I somehow use this patch for sk0 _without_ changing everything to >-current? Acutually, I wanted to stay to 6.1-RELEASE... > > Apparently the timeout problem is fixed in -CURRENT, and will be merged after 6.1-RELEASE. Enjoy. Tracking -STABLE is a Good Thing, IMHO, quite aside from the security updates, bugs which don't even affect you right now (but may do sometime) get fixed, and the -STABLE tag tends to be quite appropriate. I only ever used -RELEASE media for the initial install. A system I run at home was originally installed from FreeBSD 3.0-CURRENT, also now running a mid-Feb 6.1-PRERELEASE, upgraded from sources many many times over (build world+kernel takes just under 3 days). :-) Regards, David