From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 832A3C432C3 for ; Wed, 20 Nov 2019 06:33:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 567CB2245B for ; Wed, 20 Nov 2019 06:33:01 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="tfNz7klY" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727385AbfKTGdA (ORCPT ); Wed, 20 Nov 2019 01:33:00 -0500 Received: from mail-lf1-f65.google.com ([209.85.167.65]:36515 "EHLO mail-lf1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727165AbfKTGdA (ORCPT ); Wed, 20 Nov 2019 01:33:00 -0500 Received: by mail-lf1-f65.google.com with SMTP id f16so88567lfm.3 for ; Tue, 19 Nov 2019 22:32:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0IDyZkbtbPsofExaZyTr8bo/i/DLYlCIy4Kxh6/p4mo=; b=tfNz7klYGx3/T8c/sG3BjN25uSxe9r0/EiM8wWNnfr0XrpRrPVflDF7GX21w1R5Rcb seQ0VJ3+VODqSed608N/TyIVMsp/wPpgQai7Gk58ncg+kkfjVKPQznBExpdD73Qslv1c O+oh0On/RETmcjQgkeWTCjJMKBTewfUMwFIAIO9OuRHjevxDYN98rcTBwQjXVMf/T86t Ea4E2vw3fN6iH+2fv2QsmT+GFNpCW1hpp2qhOTsZ6J9PyPmQ7mOWsA4Z89fB149Htpnj HjGNIe5fuKJhfQIPZPj3U+Cw5WeRV2CjvnaPD/adgHoKH7nm2uaeC3ZYciGzdfKJI/NY Q7lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0IDyZkbtbPsofExaZyTr8bo/i/DLYlCIy4Kxh6/p4mo=; b=cvbEKODcQiUMn7F78VcdEZ6+zkpingLZSvYFzywCIo/c5bx0CGZyvQ3q1gV57/Cpm0 KEZV6cAajI/TdvwG8oi8N5qMpkxDn9YJX8MmeVcijJMoUNvkxpt8nS2PbQobj1lNaLE5 xtIZoA56C7EfXWM6BN5yz6BKgnBWvL4ZWQaTyGqMGaFFkPauBwrnw0gNDFyCDBOcjWJQ 6ZAAoBIwghPVhqDsy97CBANhcAhZXLMa4z4b4BQ2Ah3KuwVKgE6UCe0YHLME45HSohra 9ByPZNZVXtfF7cBdqGNGcOQLCeHL+qb5wOB/+Iip5gjOM6+aWUXc/3ug0On6dC8+usoX He3g== X-Gm-Message-State: APjAAAXO6lmrimOGreoF45exC9FY0eb/yQu0Zi6oAZZ5YpN3LWeYih7f 0WjUar58LYKga9NZ1xxCnaxX4UacPzxXOLEbVcZ6pQ== X-Google-Smtp-Source: APXvYqz+AxPaUH+ftNhZvRr23V9kyQUIFJmZ7VGaL5adTq+g4kgW6LhOkHBcQsm6DP9hz+9mmT3nRpJLhMOX4KYgza0= X-Received: by 2002:ac2:4831:: with SMTP id 17mr1310851lft.67.1574231577791; Tue, 19 Nov 2019 22:32:57 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Naresh Kamboju Date: Wed, 20 Nov 2019 12:02:45 +0530 Message-ID: Subject: Re: selftest/net: so_txtime.sh fails intermittently - read Resource temporarily unavailable To: Willem de Bruijn Cc: "open list:KERNEL SELFTEST FRAMEWORK" , Netdev , Shuah Khan , Anders Roxell , lkft-triage@lists.linaro.org, "David S. Miller" Content-Type: text/plain; charset="UTF-8" Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Fri, 15 Nov 2019 at 21:52, Willem de Bruijn wrote: > > On Thu, Nov 14, 2019 at 3:47 AM Naresh Kamboju > This appears to have been flaky from the start, particularly on qemu_arm. This is because of emulating 2 CPU. I am gonna change this to emulate 4 CPU for qemu_arm. > > Looking at a few runs.. > > failing runs exceeds bounds: > https://lkft.validation.linaro.org/scheduler/job/1006586 ... > delay29722: expected20000_(us) # > # ./so_txtime exceeds variance (2000 us) > " > These are easy to suppress, by just increasing cfg_variance_us and > optionally also increasing the delivery time scale. Alright ! The variance is 2000. static int cfg_variance_us = 2000 > Naresh, when you mention "multiple boards" are there specific > microarchitectural details of the hosts that I should take into > account aside from the qemu-arm virtualized environment itself? The easy to reproduce way is running 32-bit kernel and rootfs on x86_64 machine. arm32 bit beagleboard x15 device. qemu-arm command line, qemu-system-aarch64 -cpu host,aarch64=off -machine virt-2.10,accel=kvm -nographic -net nic,model=virtio,macaddr=BA:DD:AD:CC:09:02 -net tap -m 2048 -monitor none -kernel zImage --append "console=ttyAMA0 root=/dev/vda rw" -drive format=raw,file=rpb-console-image-lkft-am57xx-evm-20191112073604-644.rootfs.ext4,if=virtio -m 4096 -smp 2 -nographic > Very nice dashboard, btw! Thanks for your valuable feedback. Great to hear this :-) - Naresh