From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D6745A0C49; Wed, 16 Jun 2021 11:37:46 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 555FD4067A; Wed, 16 Jun 2021 11:37:46 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 7D98640140 for ; Wed, 16 Jun 2021 11:37:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1623836264; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Q6ZTElKMCkPurvme5eitu1LmnjpH+ZYpeKfXF+PzjM4=; b=DoF1NBbcQ5VMDPnhMTL6qGwZKXJsY9tzHTx7cn05Bgnfvxxa688OR7PgpZPsOIM6aJCPzf FbycStYmmVdRhMCRj4h0IJQpODbEiasslIOYV0zr16r8SYSBlbomd6eutukMkpt0LAykxO suFakgI1FP5YRlaV/EfDLmsetxDaTmY= Received: from mail-vk1-f199.google.com (mail-vk1-f199.google.com [209.85.221.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-314-ABxHncgZOLWGEseGZ1T2KQ-1; Wed, 16 Jun 2021 05:37:41 -0400 X-MC-Unique: ABxHncgZOLWGEseGZ1T2KQ-1 Received: by mail-vk1-f199.google.com with SMTP id y75-20020a1f324e0000b029021ed2c3abb3so465044vky.10 for ; Wed, 16 Jun 2021 02:37:41 -0700 (PDT) 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:content-transfer-encoding; bh=Q6ZTElKMCkPurvme5eitu1LmnjpH+ZYpeKfXF+PzjM4=; b=rIFRZ1mmjsU8+pcreA/UeVxhJuOC9uSPB9a/WQeQS2aIzhyLCNvBzko7InhuYzZ6Xg AY8E85AKpE8EZIbuszqHFwcy1ZTgYx2ldYrQn5pxhPUXTQnloSQj/iE4h+aUtssGSEhX gaz48kyUsxMvW1Lmg0Y3FNlyclh8rfCSszgi6s5hvUMbzDsKcgm7GqhXr5txu9hujDNY i+u4cQFftQakvMGCRF7NOPiw/maFHFTvlGwLCVLO9QrjbQBSOW2yosZx1eY593sI1zhG RpUqq0B6XDmEeMSA0566aDg1MRd4l8koyBBZjTBhRwcJCOJ6PKeiBGApD/CnYadjUhbk kRQA== X-Gm-Message-State: AOAM533uG9IK2ct8kPhuNv5Xd7emPTyqzEiHsTRiwMm+AT72FuLbTVZX h9pLhI+fg437pqhDD5zhabuIhCt8SMD7LHBl+tKjKSeJ+FcNEDCVemkmLCKeC8tKTxPVc7zBhAW HCiozafikmWXMryaYqXY= X-Received: by 2002:a67:fa43:: with SMTP id j3mr8591390vsq.17.1623836261159; Wed, 16 Jun 2021 02:37:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxqO/Xrq66H/MbfimWC6zDNbAUT/uHgRXX+jihWAoFvEmooISpAMN596Uuw5bqBViEP892uZGQdEKlJYZN6VSk= X-Received: by 2002:a67:fa43:: with SMTP id j3mr8591379vsq.17.1623836260988; Wed, 16 Jun 2021 02:37:40 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Wed, 16 Jun 2021 11:37:29 +0200 Message-ID: To: Owen Hilyard Cc: dev , dpdklab , Gaetan Rivet , Jerin Jacob Kollanukkaran , Aaron Conole Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] Memory leak in rte_pci_scan X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Tue, Jun 15, 2021 at 5:16 PM Owen Hilyard wrote: > > The issue may have been the interactive docker session I was running it i= n. The last few tests (150-157) were all taking until the timeout the lab u= ses for unit tests (2 hours since the timeout was multiplied by 10). I had = to leave for the day so I restarted it in a non-interactive container and i= t ran in 2 hours. If we were to just run the fast-tests suite, then it woul= d have taken 42 minutes to run. This is mostly due to timeouts in eal_flags= _c_opt_autotest, eal_flags_hpet_autotest, eal_flags_misc_autotest and multi= process_autotest, each taking 600 seconds. Finding out what caused these to= stall would bring the runtime down to 3 minutes. All of the failures shoul= d be ASAN-related. - The perf-tests testsuite is heavy and is probably not suited for per patchset runs. It may be worth running every once in a while but at the project/main branches level. - For the fast-tests testsuite, the default timeout should be 10s, not 600s= . See timeout_seconds_fast, https://git.dpdk.org/dpdk/tree/app/test/meson.build#n446 Odd that a 600s timeout has been applied to fast-tests in your run. How do you invoke meson? - There is an interesting trace that shows issues with starting secondary processes in this environment. EAL: Detected 16 lcore(s) EAL: Detected 2 NUMA nodes EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/eal_flags_c_opt_autotest/mp_socket_264_50a7b93b648fa EAL: Selected IOVA mode 'PA' EAL: VFIO support initialized EAL: Cannot get a virtual area at requested address: 0x7f1a8f400000 (got 0x7f19dc1fe000) EAL: Cannot reserve 17179869184 bytes at [0x7f1a8f400000] - please use '--base-virtaddr' option EAL: Cannot preallocate VA space for hugepage memory EAL: FATAL: Cannot init memory EAL: Cannot init memory EAL: Cannot destroy local memory map EAL: Could not release memory subsystem data It seems like there are multiple dpdk processes running in // in this environment. Any idea of what is happening on your system at the moment you tried to run this test? --=20 David Marchand