From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Jason@zx2c4.com Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 97f50c70 for ; Sun, 6 Nov 2016 11:19:01 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 699d4ac4 for ; Sun, 6 Nov 2016 11:19:01 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 59a04aba (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Sun, 6 Nov 2016 11:19:00 +0000 (UTC) Received: by mail-lf0-f51.google.com with SMTP id t196so94103544lff.3 for ; Sun, 06 Nov 2016 03:20:36 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <25241985.20161106100258@vodka.home.kg> <1289478110.20161106110707@vodka.home.kg> From: "Jason A. Donenfeld" Date: Sun, 6 Nov 2016 12:20:34 +0100 Message-ID: To: k@vodka.home.kg Content-Type: text/plain; charset=UTF-8 Cc: WireGuard mailing list Subject: Re: [WireGuard] mips32 crash List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > <7>[13905.531148] wireguard: Sending handshake initiation to peer 1 (x.x.x.x:16) > <4>[13905.629622] ------------[ cut here ]------------ So you said the crash 100% occurs 100ms after sending handshake initiation. If related this could be because: a) The scheduler ticks come in 100ms intervals. In this case, the crash would be caused by something in sending the initiation. or b) The ping latency is 100ms. In this case, the crash would be caused by something in receiving the response. or c) Something else. I'm curious: when the crash happens, does the ARM box receive the handshake initiation message?