From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from phicode.de ([136.243.147.240]) by ur; Sat Mar 12 12:59:21 EST 2016
Received: (qmail 4013 invoked from network); 12 Mar 2016 17:58:41 -0000
Received: from localhost (127.0.0.1)
  by localhost with SMTP; 12 Mar 2016 17:58:41 -0000
Date: Sat, 12 Mar 2016 18:58:41 +0100 (CET)
From: Julius Schmidt <aiju@phicode.de>
X-X-Sender: aiju@phi
To: 9front@9front.org
Subject: gping spinning
Message-ID: <alpine.LNX.2.00.1603121856590.6016@phi>
User-Agent: Alpine 2.00 (LNX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: self-healing map/reduce CMS reduce/map-scale layer 

I've seen the following happen a few times now:
ip/gping erroneously displaying 1s rtt and 100% packet loss, while 
consuming 100% cpu (when in reality the ping is normal with no packet 
loss)
I suspect this event may be triggered by a period of actually high packet 
loss and then it gets stuck in a loop somewhere.

Has anyone else seen this behaviour?