From owner-freebsd-arm@freebsd.org Sun Jun 11 14:23:36 2017 Return-Path: Delivered-To: freebsd-arm@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 230A2D881EE for ; Sun, 11 Jun 2017 14:23:36 +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 119C16729E for ; Sun, 11 Jun 2017 14:23:36 +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 v5BENZZj014052 for ; Sun, 11 Jun 2017 14:23:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 219927] awg0 stops working after a long output under ssh Date: Sun, 11 Jun 2017 14:23:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hlh@restart.be X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-arm@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 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-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jun 2017 14:23:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219927 Bug ID: 219927 Summary: awg0 stops working after a long output under ssh Product: Base System Version: CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: hlh@restart.be Environment: pine64+ 2GB FreeBSD norquay.restart.bel 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r318945M: = Sat Jun 10 11:47:44 CEST 2017=20=20=20=20 root@norquay.restart.bel:/usr/obj/usr/src/sys/NORQUAY arm64 If I connect from a wireless computer (FreeBSD 11.1-PRERELEASE #0 r318860) = and run a command with a big output (eg `find /`) the awg0 stops working quickly (under 20 seconds of output). If I do the same with telnet from the same computer, the output is much lon= ger but awg0 stops working. If I do the same from a wired computer then I must run `find /` 2 or 3 times before awg0 stops working. I can rsync through ssh 12GB without problem in both directions (from and to the pine64 and the wireless computer). I have a `tcpdump -w ssh.data port 22`. (8.3 MB) I can connect with a serial console to the pine64 after awg0 stop working. ifconfig awg0 down ifconfig awg0 up don't restore the connectivity. I must reboot to restore connectvity. Henri --=20 You are receiving this mail because: You are the assignee for the bug.=