From owner-freebsd-questions@FreeBSD.ORG Thu Dec 1 17:31:36 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA3C316A41F for ; Thu, 1 Dec 2005 17:31:36 +0000 (GMT) (envelope-from hans@nieser.net) Received: from smtp-vbr7.xs4all.nl (smtp-vbr7.xs4all.nl [194.109.24.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F7E143D64 for ; Thu, 1 Dec 2005 17:31:35 +0000 (GMT) (envelope-from hans@nieser.net) Received: from [192.168.1.10] (nieser.net [194.109.160.131]) by smtp-vbr7.xs4all.nl (8.13.3/8.13.3) with ESMTP id jB1HVXA6083757 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Dec 2005 18:31:33 +0100 (CET) (envelope-from hans@nieser.net) Message-ID: <438F3375.208@nieser.net> Date: Thu, 01 Dec 2005 18:31:33 +0100 From: Hans Nieser User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Ferdinand Haselbacher (jr.)" , freebsd-questions@freebsd.org References: <4369EA5D.3040703@vdsoft.org> <200511281220.59548.bernhard.fischer@fh-stpoelten.ac.at> <438CEC64.40405@xs4all.nl> <200511291922.25238.nb_root@videotron.ca> <20051130123409.GA4200@Hellrazor.bigfatflat> In-Reply-To: <20051130123409.GA4200@Hellrazor.bigfatflat> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Subject: Re: sk0: watchdog timeout X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2005 17:31:36 -0000 Ferdinand Haselbacher (jr.) wrote: > On Tue, Nov 29, 2005 at 07:22:17PM -0500, Nicolas Blais wrote: > >>>That's great. But as I said, there's nothing I can configure on my >>>switch's side. >> >>Anyway, you and I aren't the only ones with the same problem, under the same >>circonstances. My forcing of the TX/RX mode does speed up recovery, but >>doesn't fix the actual issue. >> >>The driver has a bug somewhere. Although I'm not talented enough in driver >>programming, but someone with skills could probably fix this. >> > > Maybe the driver has a bug somewhere, but i also think that this marvell > chips have some design flaws, iam using one on my A8V and it 's giving me > problems in WinXp (although i didn't use it for a while), Linux (seems to > work better now in 2.6.14-mm1, but still connection losses) and freebsd too. I can confirm that I got pretty much the same thing happening in Windows XP Professional SP2. There was a driver update for the Marvel Yukon NIC in Windows XP sometime ago which made it even worse and made the whole machine crash under heavy load (and my Windows XP is generally rock solid). I will be installing Gentoo soon and if it's still happening there with that skge (not sure if that's what it was called) driver, then I guess it's got to be something with the hardware. It's a bit of a shame that my other on-board nvidia NIC (nforce 4 chipset) doesn't really work well with the nve driver either. Two on-board NICs and I still need to go out and buy a 'real' one ;(