From owner-freebsd-bugs@freebsd.org Wed Dec 30 00:02:13 2015 Return-Path: Delivered-To: freebsd-bugs@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 770F7A55659 for ; Wed, 30 Dec 2015 00:02:13 +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 50CEA1DAE for ; Wed, 30 Dec 2015 00:02:13 +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 tBU02Dcr001458 for ; Wed, 30 Dec 2015 00:02:13 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 205706] Watchdog timeout on em driver under heavy traffic on a bridge configuration Date: Wed, 30 Dec 2015 00:02:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avilamarquezalvaro2015@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2015 00:02:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205706 Bug ID: 205706 Summary: Watchdog timeout on em driver under heavy traffic on a bridge configuration Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: avilamarquezalvaro2015@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org The em driver hangs with following error: em1: Watchdog timeout Queue[0]-- resetting Interface is RUNNING and ACTIVE em1: TX Queue 0 ------ em1: hw tdh =3D 379, hw tdt =3D 315 em1: Tx Queue Status =3D -2147483648 em1: TX descriptors avail =3D 64 em1: Tx Descriptors avail failure =3D 816926 em1: RX Queue 0 ------ em1: hw rdh =3D 149, hw rdt =3D 145 em1: RX discarded packets =3D 0 em1: RX Next to Check =3D 146 em1: RX Next to Refresh =3D 145 em1: link state changed to DOWN em1: link state changed to UP This is in a machine with dual Intel Gigabit NICs set up as a bridge with 11-CURRENT-amd64-20151217 base r292413. I suspect this will also happen if = only one of the NICs uses em driver. This happens under heavy traffic conditions (>=3D 10MiBytes/sec in both directions of the bridge) after 1-4 hours. Once the watchdog timeouts, the = link won't pass any more packets, it will detect cable disconn/conn. ifconfig down/ifconfig up won't help at all, a reboot is necessary. I tried the what is suggested here: bug #200221 (ifconfig -tso -vlanhwtso in both intfs) the watchdog doesn't timeout anymore but after a similar period= of time the link becomes unusable (a ping loses ~ 90% packets). This was also tested on 10.2-CURRENT with identical results Thanks --=20 You are receiving this mail because: You are the assignee for the bug.=