From owner-freebsd-net@freebsd.org Wed Sep 2 19:16:40 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 333AF9C9CEC for ; Wed, 2 Sep 2015 19:16:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 067EF694 for ; Wed, 2 Sep 2015 19:16:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t82JGdm5081758 for ; Wed, 2 Sep 2015 19:16:39 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 200221] em0 watchdog timeout under load Date: Wed, 02 Sep 2015 19:16:40 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: IntelNetworking, needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: anthony@ury.org.uk X-Bugzilla-Status: In Progress X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Sep 2015 19:16:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200221 --- Comment #18 from anthony@ury.org.uk --- Unfortunately, the server experienced a watchdog timeout this morning : Sep 2 07:39:49 urybsod kernel: em0: Watchdog timeout Queue[0]-- resetting Sep 2 07:39:49 urybsod kernel: Interface is RUNNING and ACTIVE Sep 2 07:39:49 urybsod kernel: em0: TX Queue 0 ------ Sep 2 07:39:49 urybsod kernel: em0: hw tdh = 247, hw tdt = 495 Sep 2 07:39:49 urybsod kernel: em0: Tx Queue Status = -2147483648 Sep 2 07:39:49 urybsod kernel: em0: TX descriptors avail = 771 Sep 2 07:39:49 urybsod kernel: em0: Tx Descriptors avail failure = 237 Sep 2 07:39:49 urybsod kernel: em0: RX Queue 0 ------ Sep 2 07:39:49 urybsod kernel: em0: hw rdh = 344, hw rdt = 343 Sep 2 07:39:49 urybsod kernel: em0: RX discarded packets = 0 Sep 2 07:39:49 urybsod kernel: em0: RX Next to Check = 344 Sep 2 07:39:49 urybsod kernel: em0: RX Next to Refresh = 343 Sep 2 07:39:49 urybsod kernel: em0: Link is Down Sep 2 07:39:49 urybsod kernel: em0: link state changed to DOWN Sep 2 07:39:53 urybsod kernel: em0: Link is up 1000 Mbps Full Duplex Sep 2 07:39:53 urybsod kernel: em0: link state changed to UP Sep 2 07:39:53 urybsod devd: Executing '/etc/rc.d/dhclient quietstart em0' So these patches appear to be improving stability, as this is the only occurrence in 13 days of uptime, compared to nearly every day previously. I should reiterate what state this kernel is in : sys/dev/e1000 is at 10-STABLE@HEAD with CURRENT@286381, CURRENT@285879 patched. This required some manual patching. Diff of e1000 to 10-STABLE attached. Merged r274043 and r274704 from 10-STABLE. I've not yet encountered a panic, but I'll apply 287330 to be on the safe side. -- You are receiving this mail because: You are the assignee for the bug.