From owner-freebsd-net@freebsd.org Wed Jul 15 12:21:50 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 E35559A2711 for ; Wed, 15 Jul 2015 12:21:50 +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 B58D31214 for ; Wed, 15 Jul 2015 12:21:50 +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 t6FCLogP070772 for ; Wed, 15 Jul 2015 12:21:50 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, 15 Jul 2015 12:21:50 +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 X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: anthony@ury.org.uk X-Bugzilla-Status: New 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, 15 Jul 2015 12:21:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200221 --- Comment #10 from anthony@ury.org.uk --- Now using sys/dev/e1000@283959 from 10-STABLE (rest of the kernel 10.1-RELEASE as before), I'm seeing watchdog timeouts again, with tso4 enabled. Again, this only seems to happen at a point of high network load (nightly backup over NFS). I'll try disabling tso4 on this revision but failing that, will go back to e1000@269196. There is slightly more detail in messages now, though: Jul 8 07:31:58 urybsod kernel: em0: Watchdog timeout Queue[0]-- resetting Jul 8 07:31:58 urybsod kernel: Interface is RUNNING and ACTIVE Jul 8 07:31:58 urybsod kernel: em0: TX Queue 0 ------ Jul 8 07:31:58 urybsod kernel: em0: hw tdh = 909, hw tdt = 1015 Jul 8 07:31:58 urybsod kernel: em0: Tx Queue Status = -2147483648 Jul 8 07:31:58 urybsod kernel: em0: TX descriptors avail = 914 Jul 8 07:31:58 urybsod kernel: em0: Tx Descriptors avail failure = 114 Jul 8 07:31:58 urybsod kernel: em0: RX Queue 0 ------ Jul 8 07:31:58 urybsod kernel: em0: hw rdh = 959, hw rdt = 958 Jul 8 07:31:58 urybsod kernel: em0: RX discarded packets = 0 Jul 8 07:31:58 urybsod kernel: em0: RX Next to Check = 959 Jul 8 07:31:58 urybsod kernel: em0: RX Next to Refresh = 958 Jul 8 07:31:58 urybsod kernel: em0: Link is Down Jul 8 07:31:58 urybsod kernel: em0: link state changed to DOWN Jul 8 07:32:01 urybsod kernel: em0: Link is up 1000 Mbps Full Duplex Jul 8 07:32:01 urybsod kernel: em0: link state changed to UP Jul 8 07:32:01 urybsod devd: Executing '/etc/rc.d/dhclient quietstart em0' -- You are receiving this mail because: You are the assignee for the bug.