From: David Marchand <david.marchand@redhat.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: dev@dpdk.org, Aaron Conole <aconole@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH] maintainers: update email address
Date: Thu, 21 Sep 2023 13:41:53 +0200 [thread overview]
Message-ID: <CAJFAV8yfHR-c712GCbP=JsFdrsHiYdMSTvsbA1bYffBjoiCOKQ@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUA8jJrTY0a3zVML8h0ddqufvYvZMnjzvsvEhc-YpJ1m1w@mail.gmail.com>
On Wed, Sep 20, 2023 at 5:39 PM Patrick Robb <probb@iol.unh.edu> wrote:
>
> Recheck-request: iol-unit-amd64-testing
>
> A maintainers file change should not cause eal_flags_misc_autotest to fail, so I'm queuing a retest for this series.
I agree ;-).
About this failure here, I had a look at the logs: this is something
new and I noticed the same failure on a patch of mine too this week.
I see that a secondary process crashes and some log about a failing
rte_memzone_free().
"""
EAL: Memzone is not allocated
"""
which may indicative of a double free() in some cleanup or a race
between secondary/primary process or a rare-to-reach branch of the
code....
I don't have time to look into it, so simply mentionning what I saw if
someone wants to investigate.
--
David Marchand
next prev parent reply other threads:[~2023-09-21 11:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 3:44 Chenbo Xia
2023-09-20 7:08 ` Maxime Coquelin
2023-09-20 15:39 ` Patrick Robb
2023-09-21 11:41 ` David Marchand [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-20 8:51 Chenbo Xia
2023-10-20 9:04 ` Maxime Coquelin
2023-10-20 10:54 ` David Marchand
2022-09-21 13:41 Ferruh Yigit
2022-09-28 12:12 ` Thomas Monjalon
2022-04-21 15:20 Konstantin Ananyev
2022-04-21 16:04 ` Mcnamara, John
2022-05-10 9:07 ` Thomas Monjalon
2022-04-11 18:05 Ferruh Yigit
2022-04-14 9:44 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJFAV8yfHR-c712GCbP=JsFdrsHiYdMSTvsbA1bYffBjoiCOKQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).