Date: Fri, 5 May 2006 20:26:54 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Wilko Bulte <wb@freebie.xs4all.nl> Cc: freebsd-stable@freebsd.org, Miles Lubin <mlubin@junker.org> Subject: Re: sk0: watchdog timeout Message-ID: <20060505202511.S54242@maildrop.int.zabbadoz.net> In-Reply-To: <20060505192954.GA8995@freebie.xs4all.nl> References: <20060505124058.N25705@junker.org> <20060505192954.GA8995@freebie.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 5 May 2006, Wilko Bulte wrote: > 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: <Marvell Gigabit Ethernet> port 0xa000-0xa0ff mem >> 0xfbb00000-0xfbb03fff ir >> q 17 at device 10.0 on pci0 >> skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) >> sk0: <Marvell Semiconductor, Inc. Yukon> 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 The updated driver has been in HEAD for some days and the problem should be fixed there thanks to Pyun. See last commits to src/sys/dev/sk/* -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060505202511.S54242>