From owner-freebsd-current@FreeBSD.ORG Wed Dec 24 15:44:42 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D8A6106564A for ; Wed, 24 Dec 2008 15:44:42 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 0AC218FC08 for ; Wed, 24 Dec 2008 15:44:42 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 898D01EF7EC; Wed, 24 Dec 2008 10:44:41 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Wed, 24 Dec 2008 10:44:41 -0500 X-Sasl-enc: ItFmb3dXJ9JpjXdzAPc9oNFnvHb+ZMCBOsXNipeN4xCe 1230133481 Received: from anglepoise.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id B7EC3472B6; Wed, 24 Dec 2008 10:44:40 -0500 (EST) Message-ID: <495258E7.5070309@incunabulum.net> Date: Wed, 24 Dec 2008 15:44:39 +0000 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.18 (X11/20081204) MIME-Version: 1.0 To: pyunyh@gmail.com References: <20070520174124.GA14987@Athena.infor.org> In-Reply-To: <20070520174124.GA14987@Athena.infor.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: msk watchdog timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Dec 2008 15:44:42 -0000 Hi, I just observed a similar issue with the onboard msk0 on my ASUS Vintage AH-1. The symptoms occurred in the last hour, when attempting to download the 7.1-RC1-i386-dvd1.iso.gz from ftp.plig.net mirror. It is triggered when the data rate of the wget job hit around 890 KiB/sec. Let me know if you need a PR raised for this. uname -a: %%% FreeBSD anglepoise.lon.incunabulum.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Wed Dec 3 17:03:33 GMT 2008 root@anglepoise.lon.incunabulum.net:/home/obj/usr/src/sys/ANGLEPOISE7 amd64 %%% dmesg output from syslog: %%% Dec 24 15:08:05 anglepoise kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering Dec 24 15:09:32 anglepoise kernel: msk0: watchdog timeout Dec 24 15:09:32 anglepoise kernel: msk0: link state changed to DOWN Dec 24 15:09:34 anglepoise kernel: msk0: link state changed to UP Dec 24 15:09:46 anglepoise kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering Dec 24 15:10:08 anglepoise kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering Dec 24 15:10:32 anglepoise kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering Dec 24 15:11:03 anglepoise kernel: msk0: watchdog timeout Dec 24 15:11:03 anglepoise kernel: msk0: link state changed to DOWN Dec 24 15:11:05 anglepoise kernel: msk0: link state changed to UP Dec 24 15:12:10 anglepoise kernel: msk0: watchdog timeout Dec 24 15:12:10 anglepoise kernel: msk0: link state changed to DOWN Dec 24 15:12:12 anglepoise kernel: msk0: link state changed to UP Dec 24 15:12:20 anglepoise kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering Dec 24 15:12:58 anglepoise last message repeated 3 times Dec 24 15:14:28 anglepoise last message repeated 12 times Dec 24 15:14:29 anglepoise kernel: msk0: link state changed to DOWN Dec 24 15:14:31 anglepoise kernel: msk0: link state changed to UP Dec 24 15:14:39 anglepoise kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering Dec 24 15:15:06 anglepoise last message repeated 3 times Dec 24 15:15:21 anglepoise kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering Dec 24 15:18:27 anglepoise dhclient[339]: connection closed Dec 24 15:18:27 anglepoise dhclient[339]: exiting. Dec 24 15:18:33 anglepoise kernel: msk0: link state changed to DOWN Dec 24 15:18:35 anglepoise kernel: msk0: link state changed to UP Dec 24 15:18:35 anglepoise kernel: msk0: link state changed to DOWN Dec 24 15:18:37 anglepoise kernel: msk0: link state changed to UP Dec 24 15:18:46 anglepoise kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering Dec 24 15:18:49 anglepoise kernel: msk0: link state changed to DOWN Dec 24 15:18:51 anglepoise kernel: msk0: link state changed to UP Dec 24 15:19:00 anglepoise kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering Dec 24 15:19:38 anglepoise last message repeated 4 times Dec 24 15:19:47 anglepoise kernel: msk0: watchdog timeout (missed Tx interrupts) Dec 24 15:18:46 anglepoise kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering Dec 24 15:18:49 anglepoise kernel: msk0: link state changed to DOWN Dec 24 15:18:51 anglepoise kernel: msk0: link state changed to UP Dec 24 15:19:00 anglepoise kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering Dec 24 15:19:38 anglepoise last message repeated 4 times Dec 24 15:19:47 anglepoise kernel: msk0: watchdog timeout (missed Tx interrupts) -- recovering Dec 24 15:25:48 anglepoise last message repeated 6 times Dec 24 15:28:04 anglepoise kernel: msk0: promiscuous mode enabled Dec 24 15:28:56 anglepoise kernel: msk0: promiscuous mode disabled Dec 24 15:29:41 anglepoise sudo: bms : TTY=ttyp4 ; PWD=/home/bms ; USER=roo t ; COMMAND=/sbin/reboot Dec 24 15:29:41 anglepoise reboot: rebooted by bms Dec 24 15:29:41 anglepoise syslogd: exiting on signal 15 %%% The DHCP lease is lost, msk0 appears to stop receiving traffic. I *did* re-patch the cable on my switch around this point in time, and it's possible this triggered the condition. Perhaps this is a receive DMA descriptor problem, or a PHY interrupt problem? I confirmed that neither the cabling itself nor other network infrastructure were responsible. thanks BMS