From owner-freebsd-net@freebsd.org  Thu Mar 16 06:40:52 2017
Return-Path: <owner-freebsd-net@freebsd.org>
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 917F2D0EF52
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Thu, 16 Mar 2017 06:40:52 +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 7A4E71A93
 for <freebsd-net@FreeBSD.org>; Thu, 16 Mar 2017 06:40:52 +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 v2G6eqjC002564
 for <freebsd-net@FreeBSD.org>; Thu, 16 Mar 2017 06:40:52 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 217721] axge(4) hangs while link goes offline
Date: Thu, 16 Mar 2017 06:40:52 +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: 11.0-RELEASE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: lozovoy.ep+bugsfreebsd@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-217721-2472-A9DC7JMCgd@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217721-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-217721-2472@https.bugs.freebsd.org/bugzilla/>
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-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Mar 2017 06:40:52 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217721

--- Comment #4 from Eugene Lozovoy <lozovoy.ep+bugsfreebsd@gmail.com> ---
(In reply to Pyun YongHyeon from comment #3)

>Wouldn't you're able to send packets again if you wait some more
>time(i.e. link establishment time + time taken to empty queued
>packets)?
No, I waited ~10 minutes, but only ifconfig down && ifconfig up solved "No
buffer space available" problem.

> However, given that link DOWN is not frequent event, I guess
> current behavior would be slightly better than just dropping
> packets.
I'm using axge card to share network with home pc. So, link goes DOWN every
night, and every morning I get "No buffer space available". My axge include=
d in
bridge, but bug reproducing with and without bridge.

--=20
You are receiving this mail because:
You are the assignee for the bug.=