From: Stephen Hemminger <stephen@networkplumber.org>
To: Luca Boccassi <luca.boccassi@gmail.com>
Cc: David Marchand <david.marchand@redhat.com>,
dev@dpdk.org, roretzla@linux.microsoft.com
Subject: Re: [PATCH v2] Revert "eal/unix: fix thread creation"
Date: Thu, 31 Oct 2024 13:46:20 -0700 [thread overview]
Message-ID: <20241031134620.39aea352@hermes.local> (raw)
In-Reply-To: <CAMw=ZnST9pcMxVk-C_MS2M1LehNEmEcGjS+=joKcQNsZ8Pg7_w@mail.gmail.com>
On Thu, 31 Oct 2024 14:05:16 +0000
Luca Boccassi <luca.boccassi@gmail.com> wrote:
> On Thu, 31 Oct 2024 at 13:04, David Marchand <david.marchand@redhat.com> wrote:
> >
> > On Thu, Oct 31, 2024 at 1:58 PM Luca Boccassi <luca.boccassi@gmail.com> wrote:
> > >
> > > On Thu, 31 Oct 2024 at 12:52, David Marchand <david.marchand@redhat.com> wrote:
> > > >
> > > > On Thu, Oct 31, 2024 at 1:47 PM David Marchand
> > > > <david.marchand@redhat.com> wrote:
> > > > > Could you share a backtrace when hitting this deadlock?
> > > >
> > > > If the backtrace is not possible, running with
> > > > --log-level=lib.eal:debug may help.
> > >
> > > I cannot get backtraces. This runs via "meson test", how can that
> > > option be passed in?
> >
> > # meson test -C build-debian --suite fast-tests --verbose -t 5
> > --test-args=--log-level=lib.eal:debug
>
> https://paste.debian.net/1334095/
Could not repro this on Raspberry Pi 5. Main branch builds and runs
next prev parent reply other threads:[~2024-10-31 20:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 19:08 [PATCH] " luca.boccassi
2024-10-30 19:52 ` Stephen Hemminger
2024-10-30 20:31 ` Luca Boccassi
2024-10-30 20:30 ` [PATCH v2] " luca.boccassi
2024-10-31 12:47 ` David Marchand
2024-10-31 12:52 ` David Marchand
2024-10-31 12:58 ` Luca Boccassi
2024-10-31 13:03 ` David Marchand
2024-10-31 14:05 ` Luca Boccassi
2024-10-31 20:46 ` Stephen Hemminger [this message]
2024-11-02 10:09 ` David Marchand
2024-11-04 17:59 ` David Marchand
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=20241031134620.39aea352@hermes.local \
--to=stephen@networkplumber.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=luca.boccassi@gmail.com \
--cc=roretzla@linux.microsoft.com \
/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).