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 53E87A0C43; Wed, 16 Jun 2021 19:41:44 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3C60840683; Wed, 16 Jun 2021 19:41:44 +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 032674067A for ; Wed, 16 Jun 2021 19:41:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1623865302; 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=m7Obitg2QgkaB5Gpi28lq1yE+rlrvq/XgAALkTxtEFU=; b=TKXwk9E5kETEnPdMsOkNhCZhi8aQXD9IuUfy3grUAlagLK46bQl93TvWNpWE530fNkAWfZ /XwQJPhOWotljCU0D2pR1JCfoFx7ooJsO67CDOM8rUf0puwAvNPTOLwjqc+gkIky6L7HxL +b7AMY4JQynCiiLuKMUVtwXQkY/tiqA= Received: from mail-vk1-f197.google.com (mail-vk1-f197.google.com [209.85.221.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-6-K9KQzn0eOBqW0jLXswUJfQ-1; Wed, 16 Jun 2021 13:41:10 -0400 X-MC-Unique: K9KQzn0eOBqW0jLXswUJfQ-1 Received: by mail-vk1-f197.google.com with SMTP id p194-20020a1fa6cb0000b0290246aba8cd6eso410698vke.15 for ; Wed, 16 Jun 2021 10:41:10 -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=m7Obitg2QgkaB5Gpi28lq1yE+rlrvq/XgAALkTxtEFU=; b=i6Hjl9nSRXvHZz95xNrt7j5H84XEtEvxvCJJHcE4QVUKZoErtJXOpPQxOYEN4tcA2g 3j6OcD6CUq05N2uNRn9VkRf8F7301WA4HsLphyzHuZoDES2DWPSjoFNzif1vJpL6NJ5K e9CyBpV9FmqE9QPpcKL11AC9SPzRZ0oZGk/zrN7KwP3odYGgey42DyJithABhUcf9Op/ tSfgFzrCUqdeBEDJyV6ifLh26so/HwphLdM858UCGfaYOxHdtMMwL36swQ7SXd1dGGh0 iuDCIBmBUUbfeZ97cj5UQP08L+1lwizcCM0S4JemhWPmkVzAmHGOf/vYrHo3DEJIipOT TRAg== X-Gm-Message-State: AOAM532VNKVtLHfip5fNXGM824aZK/EmOZ60skcHuKo+LhEaQwxq4tjh 3aK3lBBiO3dYL90Cb3z9f9EXQ3Z7v0iUC424ly0IGhJqrOOB85anQ8cyR13LjFSpb01isDUSadp G+sD0mVULwo2VDjjP4Fg= X-Received: by 2002:ab0:2345:: with SMTP id h5mr819402uao.126.1623865269842; Wed, 16 Jun 2021 10:41:09 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzYisnmYIC1pPh+3dh4jUX5j9WZs/kcy0NDNT+T+WKFxAJKo5audgDpHjz8nsxuforcDHR1rZQLWEgYvviy4No= X-Received: by 2002:ab0:2345:: with SMTP id h5mr819373uao.126.1623865269650; Wed, 16 Jun 2021 10:41:09 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Wed, 16 Jun 2021 19:40:58 +0200 Message-ID: To: Owen Hilyard Cc: dev , dpdklab , Gaetan Rivet , Jerin Jacob Kollanukkaran , Aaron Conole , "Burakov, Anatoly" 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 Wed, Jun 16, 2021 at 6:27 PM Owen Hilyard wrote: >> - For the fast-tests testsuite, the default timeout should be 10s, not 6= 00s. >> 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? > > > # meson test -t 600 > > I copied the invocation from the production scripts for the community lab= and removed the --suite argument. 600? -t is for timeout multiplier. The default timeout for fast tests is 10s and the logs in a previous mail show 600s for timeout, so I would expect a 60 multiplier. > >> 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? > > > I ran this on a VM that we keep in the same state as the production conta= iner runners. It is not attached to our Jenkins instance, and I was the onl= y logged-in user. I re-ran the test suite with and without ASAN, and it se= ems like this type of failure only happens when ASAN is active. The failing= tests are: eal_flags_a_opt_autotest, eal_flags_b_opt_autotest, eal_flags_c= _opt_autotest, eal_flags_main_opt_autotest, eal_flags_misc_autotest. I've a= ttached the log. ASAN seems to break some assumption on the default virtual base address used by the mp stuff. It might be a reason for the secondary process init failure. Still, we have probably a deadlock here, since the test should fail in a reasonable amount of time. My guess would be at some secondary process not releasing a lock and the primary ends up waiting on it. Here, a secondary process did not initialise correctly, but it tried to cleanup afterwards... per chance, do you have a crash reported in syslog? --=20 David Marchand