From owner-freebsd-stable@FreeBSD.ORG Fri May 5 19:30:19 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 8980416A47D for ; Fri, 5 May 2006 19:30:19 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr11.xs4all.nl (smtp-vbr11.xs4all.nl [194.109.24.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FC2843D7F for ; Fri, 5 May 2006 19:30:00 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr11.xs4all.nl (8.13.6/8.13.6) with ESMTP id k45JTsnP023932; Fri, 5 May 2006 21:29:59 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id k45JTscS009053; Fri, 5 May 2006 21:29:54 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id k45JTswA009052; Fri, 5 May 2006 21:29:54 +0200 (CEST) (envelope-from wb) Date: Fri, 5 May 2006 21:29:54 +0200 From: Wilko Bulte To: Miles Lubin Message-ID: <20060505192954.GA8995@freebie.xs4all.nl> References: <20060505124058.N25705@junker.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060505124058.N25705@junker.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: sk0: watchdog timeout 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: Fri, 05 May 2006 19:30:23 -0000 On Fri, May 05, 2006 at 01:03:55PM -0400, Miles Lubin wrote.. > My motherboard has a built-in ethernet port that is handled by the sk > driver. I'm running FreeBSD 6.1-RC on amd64. When the network card is > under high load, it often kills any current connections and leaves the > message "sk0: watchdog timeout" in dmesg. I've seen previous posts on this > issue, but the problem doesn't seem to be resolved. This issue makes these > network cards unusable in production environments. > > Relevent dmesg output: > skc0: port 0xa000-0xa0ff mem > 0xfbb00000-0xfbb03fff ir > q 17 at device 10.0 on pci0 > skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) > sk0: on skc0 I had a similar event last night, on a P4 on an Asus P4P800. The current driver is much less prone to this lockup problem than it used to be. In my case it does not have to be in a high-load situation, it appears to happen rather randomly (and *very* infrequently) FreeBSD freebie.xs4all.nl 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #2: Thu May 4 22:37:22 CEST 2006 skc0: <3Com 3C940 Gigabit Ethernet> port 0xe800-0xe8ff mem 0xf7ffc000-0xf7ffffff irq 22 at device 5.0 on pci2 skc0: 3Com Gigabit LOM (3C940) rev. (0x1) sk0: on skc0 sk0: Ethernet address: 00:0c:6e:4f:77:0c miibus0: on sk0 e1000phy0: on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto For the time being I stuck a em(4) in this machine, it is my primary server and I need to have it running for my work as re-builder for the Alpha platform :) Wilko -- Wilko Bulte wilko@FreeBSD.org