From owner-freebsd-bugs@FreeBSD.ORG Tue Feb 14 19:20:13 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 353CB1065675 for ; Tue, 14 Feb 2012 19:20:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 11C1E8FC1F for ; Tue, 14 Feb 2012 19:20:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q1EJKCuL031534 for ; Tue, 14 Feb 2012 19:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q1EJKCsI031533; Tue, 14 Feb 2012 19:20:12 GMT (envelope-from gnats) Resent-Date: Tue, 14 Feb 2012 19:20:12 GMT Resent-Message-Id: <201202141920.q1EJKCsI031533@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Monthadar Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D1F01065677 for ; Tue, 14 Feb 2012 19:17:17 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 6C39C8FC24 for ; Tue, 14 Feb 2012 19:17:17 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q1EJHH6e089582 for ; Tue, 14 Feb 2012 19:17:17 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q1EJHHN3089581; Tue, 14 Feb 2012 19:17:17 GMT (envelope-from nobody) Message-Id: <201202141917.q1EJHHN3089581@red.freebsd.org> Date: Tue, 14 Feb 2012 19:17:17 GMT From: Monthadar To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: kern/165149: [ath][net80211] Ping with data length more than iv_fragthreshold X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2012 19:20:13 -0000 >Number: 165149 >Category: kern >Synopsis: [ath][net80211] Ping with data length more than iv_fragthreshold >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Feb 14 19:20:12 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Monthadar >Release: Current >Organization: >Environment: mips:mipseb >Description: If I lower iv_fragthreshold to IEEE80211_FRAG_MIN and then ping with a data size that makes net80211 frame larger than threshold the frame is never sent. Freebsd seems to be stuck somewhere cause the ping program never print anything, quiting ping does show that packets have been sent but that is not true. Ping without -s option works. After a while (not sure when or how) I get these print out on console: # ping -s8192 192.168.5.12 PING 192.168.5.12 (192.168.5.12): 8192 data bytes arge0: Failed to allocate buffer ath0: ath_rx_proc: no mbuf! ath0: ath_rx_proc: no mbuf! ath0: ath_rx_proc: no mbuf! ath0: ath_rx_proc: no mbuf! ath0: ath_rx_proc: no mbuf! ath0: ath_rx_proc: no mbuf! ath0: ath_rx_proc: no mbuf! I tried with -s1024 and -s193 no frame sent, -s192 works fine. >How-To-Repeat: change (ieee80211_var.h): #define IEEE80211_FRAG_DEFAULT IEEE80211_FRAG_MAX to: #define IEEE80211_FRAG_DEFAULT IEEE80211_FRAG_MIN Then you need two ath wifi setup as STA and AP. Then: # ping -c 1 192.168.5.12 PING 192.168.5.12 (192.168.5.12): 56 data bytes 64 bytes from 192.168.5.12: icmp_seq=0 ttl=64 time=61.260 ms --- 192.168.5.12 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 61.260/61.260/61.260/0.000 ms # # ping -s8192 192.168.5.12 PING 192.168.5.12 (192.168.5.12): 8192 data bytes ^C --- 192.168.5.12 ping statistics --- 134 packets transmitted, 0 packets received, 100.0% packet loss RSPRO-MESH-11# ping -s8192 192.168.5.12 PING 192.168.5.12 (192.168.5.12): 8192 data bytes arge0: Failed to allocate buffer ath0: ath_rx_proc: no mbuf! ath0: ath_rx_proc: no mbuf! ath0: ath_rx_proc: no mbuf! ath0: ath_rx_proc: no mbuf! ath0: ath_rx_proc: no mbuf! >Fix: unknown >Release-Note: >Audit-Trail: >Unformatted: