From owner-freebsd-wireless@freebsd.org Wed Nov 21 15:28:59 2018 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F5FE113BFC6 for ; Wed, 21 Nov 2018 15:28:59 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 062FD84B25 for ; Wed, 21 Nov 2018 15:28:59 +0000 (UTC) (envelope-from arcade@b1t.name) Received: by mailman.ysv.freebsd.org (Postfix) id BD610113BFC3; Wed, 21 Nov 2018 15:28:58 +0000 (UTC) Delivered-To: wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9AA27113BFC2 for ; Wed, 21 Nov 2018 15:28:58 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from limbo.b1t.name (limbo.b1t.name [78.25.32.206]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9C53484B20 for ; Wed, 21 Nov 2018 15:28:56 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from [172.29.1.147] (probe.42.lan [172.29.1.147]) by limbo.b1t.name (Postfix) with ESMTPSA id A821E87; Wed, 21 Nov 2018 17:28:46 +0200 (EET) Subject: Re: Atheros 9220 - losing connectivity To: Adrian Chadd Cc: "freebsd-wireless@freebsd.org" References: <421db909-9c41-15bf-5ee1-b91311185321@b1t.name> From: Volodymyr Kostyrko Message-ID: <104c69b4-ba9e-2ded-3e42-ff631b52087d@b1t.name> Date: Wed, 21 Nov 2018 17:28:28 +0200 User-Agent: Mozilla/5.0 (X11; DragonFly x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=b1t.name; s=dkim; t=1542814127; bh=Osrk8W0EDJugUF7Xp3Fv8gDaTebaY5f6EoF2g2ICA2Y=; h=Subject:To:Cc:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=qRx101eYbqnvy7o4gE2+iDEh757MHd1QvAbhtqT5TQUXp8Nxt7qJX3wD50ojzqyxJMmGFsfzV6SzoduUFAPDvojMJgh+Yu+3IJXl+5JxS0HjoJN/FybeEWFj395mwhdcSPfzXmli4Qv62iL2R0nUyAoMwJw3XCGtl5yabjBMD4M= X-Rspamd-Queue-Id: 062FD84B25 X-Spamd-Result: default: False [-8.07 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; FORGED_RECIPIENTS_FORWARDING(0.00)[]; FORWARDED(0.00)[wireless@mailman.ysv.freebsd.org]; SPF_FAIL_FORWARDING(0.00)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[b1t.name:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(0.00)[b1t.name,none]; RCVD_IN_DNSWL_MED(-0.20)[5.0.0.0.0.5.0.0.0.0.0.0.0.0.0.0.a.6.0.2.4.5.2.2.0.0.9.1.1.0.0.2.list.dnswl.org : 127.0.9.2]; DMARC_POLICY_ALLOW_WITH_FAILURES(-0.50)[]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(-3.68)[ip: (-9.87), ipnet: 2001:1900:2254::/48(-4.77), asn: 10310(-3.66), country: US(-0.09)]; MX_GOOD(-0.01)[cached: limbo.b1t.name]; ASN(0.00)[asn:10310, ipnet:2001:1900:2254::/48, country:US]; FORGED_RECIPIENTS(0.00)[adrianchadd@gmail.com ..,freebsd-wireless@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; R_SPF_FAIL(0.00)[-all]; R_DKIM_ALLOW(-0.20)[b1t.name]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_SHORT(-0.98)[-0.976,0] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2018 15:28:59 -0000 On 16.11.18 00:02, Adrian Chadd wrote: > ok, interesting. I'll see if I can reproduce it later next week. I haven't > changed much on the AR9220 HAL... Though I'm already not quite sure that's about wireless: Client side: 64 bytes from 172.29.1.1: icmp_seq=3484 ttl=64 time=6769.941 ms 64 bytes from 172.29.1.1: icmp_seq=3485 ttl=64 time=5759.887 ms 64 bytes from 172.29.1.1: icmp_seq=3486 ttl=64 time=4749.831 ms 64 bytes from 172.29.1.1: icmp_seq=3491 ttl=64 time=1079.225 ms ping: sendto: Network is down ping: sendto: Network is down 64 bytes from 172.29.1.1: icmp_seq=3543 ttl=64 time=3.459 ms 64 bytes from 172.29.1.1: icmp_seq=3544 ttl=64 time=0.765 ms 64 bytes from 172.29.1.1: icmp_seq=3545 ttl=64 time=0.764 ms Server side: 17:16:13.780615 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id 61963, seq 3484, length 64 17:16:13.780626 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, seq 3484, length 64 17:16:13.780665 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id 61963, seq 3485, length 64 17:16:13.780671 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, seq 3485, length 64 17:16:13.780798 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id 61963, seq 3486, length 64 17:16:13.780806 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, seq 3486, length 64 17:16:13.901127 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port 1209 unreachable, length 36 17:16:13.926867 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port 1209 unreachable, length 36 17:16:13.926901 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port 2265 unreachable, length 36 17:16:13.953174 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port 2265 unreachable, length 36 17:16:14.255022 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id 61963, seq 3491, length 64 17:16:14.255043 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, seq 3491, length 64 17:16:14.666831 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port 1549 unreachable, length 36 17:16:14.666847 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port 1191 unreachable, length 36 17:16:14.666853 IP 172.29.1.147 > 172.29.1.1: ICMP 172.29.1.147 udp port 1626 unreachable, length 36 17:16:15.268339 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id 61963, seq 3492, length 64 17:16:15.268376 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, seq 3492, length 64 17:16:16.292245 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id 61963, seq 3493, length 64 17:16:16.292265 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, seq 3493, length 64 17:16:17.326008 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id 61963, seq 3494, length 64 17:16:17.326050 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, seq 3494, length 64 17:16:18.306333 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id 61963, seq 3495, length 64 17:16:18.306349 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, seq 3495, length 64 17:16:19.305307 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id 61963, seq 3496, length 64 17:16:19.305341 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, seq 3496, length 64 17:16:20.316914 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id 61963, seq 3497, length 64 17:16:20.316951 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, seq 3497, length 64 17:16:21.358600 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id 61963, seq 3498, length 64 17:16:21.358627 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, seq 3498, length 64 17:16:22.667213 IP 172.29.1.147 > 172.29.1.1: ICMP echo request, id 61963, seq 3499, length 64 17:16:22.667240 IP 172.29.1.1 > 172.29.1.147: ICMP echo reply, id 61963, seq 3499, length 64 1. Everything works. 2. Packets 3487 - 3490 doesn't reach server. 3. Packet 3491 hits. 4. Packets 3492 - 3540 doesn't reach client. 5. I frob the client link. 6. 2 packets went nowhere while connection gets established. 7. Everything works. No bstuck increments in the process. -- Sphinx of black quartz judge my vow.