From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] qemux86/conf: TEST ONLY. Drop smp boot
Date: Sat, 10 Jun 2023 22:08:38 -0400 [thread overview]
Message-ID: <ZIUspsqML9XJtx7P@windriver.com> (raw)
In-Reply-To: <CADkTA4OGDBUgFhmeV9BkHoWv8aPu9Y6A2B2iPRBTEhB3ny0eSw@mail.gmail.com>
[Re: [PATCH 1/2] qemux86/conf: TEST ONLY. Drop smp boot] On 09/06/2023 (Fri 10:08) Bruce Ashfield wrote:
> On Fri, Jun 9, 2023 at 2:06???AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
[...]
> > FWIW, this patch didn't change much. With it applied we still see:
>
>
> ok. so at least we can rule out it being specific to secondary cpu startup.
I'll own some of that. I was looking forward in the dmesg where
secondary CPU init was, and ignoring looking backwards.
I have a new thought. I still could be completely off base. I updated
the case with my theory.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15138
Might totally be another wild goose chase. Who knows...
Paul.
--
next prev parent reply other threads:[~2023-06-11 2:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 19:39 [PATCH 1/2] qemux86/conf: TEST ONLY. Drop smp boot bruce.ashfield
2023-06-08 19:39 ` [PATCH 2/2] qemux86*: TEST only set preferred provider to linux-yocto-dev bruce.ashfield
2023-06-09 7:17 ` Richard Purdie
[not found] ` <1766EC6ECDD1A1C4.6460@lists.openembedded.org>
2023-06-09 7:19 ` [OE-core] " Richard Purdie
2023-06-09 14:10 ` Bruce Ashfield
2023-06-09 6:05 ` [PATCH 1/2] qemux86/conf: TEST ONLY. Drop smp boot Richard Purdie
2023-06-09 14:08 ` Bruce Ashfield
2023-06-11 2:08 ` Paul Gortmaker [this message]
2023-06-12 10:18 ` Richard Purdie
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=ZIUspsqML9XJtx7P@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.