All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3][RFT]: kernel-yocto: v5.4 LTS kernel
Date: Sat, 1 Feb 2020 17:47:11 -0500	[thread overview]
Message-ID: <CADkTA4MYP_vkdjSb9-g=FdrELLGfrap2vOZjuYUdBcVoS5Uznw@mail.gmail.com> (raw)
In-Reply-To: <4789b1f1-8dc1-dead-1a19-d18f17c0d709@gmail.com>

On Fri, Jan 31, 2020 at 1:25 PM Khem Raj <raj.khem@gmail.com> wrote:
>
> On 1/29/20 4:48 AM, Bruce Ashfield wrote:
> > On Wed, Jan 29, 2020 at 2:31 AM Alexander Kanavin
> > <alex.kanavin@gmail.com> wrote:
> >>
> >> Can these issues be bisected? That's how the two kernel regressions (both found last year via ptests) were tracked down to specific commits.
> >>
> >
> > mips64 was already bisected, and reported upstream, not much help
> > there .. I've already reached out to some more hardcore mips folks for
> > more help, so hopefully that works :D
> >
> can you point to link where this thread is

It was on the mips-kernel mailing list, but thanks to our friends at
Cisco, I have a patch in hand for this issue now. They'll follow up to
the original thread on the kernel mailing list with the detailed
findings (also watch for it on the linux-yocto mailing list).

>
> > The musl one didn't bisect in my attempt(s), but in that config it is
> > an easy issue to trigger. I'm out of time to debug it for the next two
> > weeks, hence why I'm broadcasting to see if others want to take a
> > look.
> >
>
> As I saw, I do not see this with latest master-next

ok, cool. I'll queue the mips fix and re-test. Hopefully it has been
sorted out through the latest version bumps.

Bruce

>
> > Bruce
> >
> >> Alex
> >>
> >> On Tue, 28 Jan 2020 at 23:14, <bruce.ashfield@gmail.com> wrote:
> >>>
> >>> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >>>
> >>> Hi all,
> >>>
> >>> I just wanted to send these to the list, so everyone could see the
> >>> reference kernel that we are planning for the upcoming release.
> >>>
> >>> I have other patches to drop 4.19, 5.2 and make this the default
> >>> kernel for the various reference platforms as well, but I'm not
> >>> sending them, since we still have two outstanding issues:
> >>>
> >>> 1) mips64 init is segfaulting after / during some self tests.
> >>>
> >>>     https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/1520/steps/8/logs/step6c
> >>>
> >>> 2) x86 musl is getting a gpf on many commands:
> >>>
> >>>     https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/1501/steps/8/logs/step1c
> >>>
> >>> I've looked into both, and don't have any great ideas on how to debug
> >>> or fix them.
> >>>
> >>> So if anyone has ideas, or wants to poke at these, feel free to follow up.
> >>> But as of now, we still can't merge the v5.4 kernel as the reference due
> >>> to these remaining problems.
> >>>
> >>> Bruce
> >>>
> >>>
> >>> The following changes since commit ca3993cc4b13d4e661228cee6fb9448adfd0a4ba:
> >>>
> >>>    bitbake: tests/fetch: Allow wget upgrade tests to run against a local server (2020-01-22 15:56:39 +0000)
> >>>
> >>> are available in the Git repository at:
> >>>
> >>>    git://git.pokylinux.org/poky-contrib zedd/kernel-oe
> >>>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-oe
> >>>
> >>> Bruce Ashfield (3):
> >>>    linux-yocto: introduce 5.4 recipes
> >>>    kern-tools: update Kconfiglib to latest (for 5.4+ kernel)
> >>>    kernel-devsrc: update to v5.4+
> >>>
> >>>   .../kern-tools/kern-tools-native_git.bb       |  2 +-
> >>>   meta/recipes-kernel/linux/kernel-devsrc.bb    |  8 +--
> >>>   .../linux/linux-yocto-rt_5.4.bb               | 44 +++++++++++++++
> >>>   .../linux/linux-yocto-tiny_5.4.bb             | 32 +++++++++++
> >>>   meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 54 +++++++++++++++++++
> >>>   5 files changed, 136 insertions(+), 4 deletions(-)
> >>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
> >>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
> >>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_5.4.bb
> >>>
> >>> --
> >>> 2.19.1
> >>>
> >>> --
> >>> _______________________________________________
> >>> Openembedded-core mailing list
> >>> Openembedded-core@lists.openembedded.org
> >>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
> >
> >
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


  reply	other threads:[~2020-02-01 22:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28 22:14 [PATCH 0/3][RFT]: kernel-yocto: v5.4 LTS kernel bruce.ashfield
2020-01-28 22:14 ` [PATCH 1/3] linux-yocto: introduce 5.4 recipes bruce.ashfield
2020-01-30 15:18   ` Khem Raj
2020-02-03 16:42     ` Martin Jansa
2020-02-03 16:45       ` Khem Raj
2020-02-03 17:11         ` Bruce Ashfield
2020-02-03 17:37           ` Martin Jansa
2020-02-03 17:51             ` Bruce Ashfield
2020-02-03 21:33               ` Bruce Ashfield
2020-02-03 17:32         ` Martin Jansa
2020-02-03 17:37           ` Khem Raj
2020-02-03 17:33       ` [PATCH] kernel.bbclass: set LD in KERNEL_CONFIG_COMMAND to fix 5.4+ builds when gold is enabled Martin Jansa
2020-01-28 22:14 ` [PATCH 2/3] kern-tools: update Kconfiglib to latest (for 5.4+ kernel) bruce.ashfield
2020-01-28 22:14 ` [PATCH 3/3] kernel-devsrc: update to v5.4+ bruce.ashfield
2020-01-29  1:58 ` [PATCH 0/3][RFT]: kernel-yocto: v5.4 LTS kernel Khem Raj
2020-01-31  5:34   ` Khem Raj
2020-01-29  7:31 ` Alexander Kanavin
2020-01-29 12:48   ` Bruce Ashfield
2020-01-31 18:25     ` Khem Raj
2020-02-01 22:47       ` Bruce Ashfield [this message]
2020-02-03  7:33         ` Bruce Ashfield
2020-02-03 18:02 ` ✗ patchtest: failure for : kernel-yocto: v5.4 LTS kernel (rev2) Patchwork

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='CADkTA4MYP_vkdjSb9-g=FdrELLGfrap2vOZjuYUdBcVoS5Uznw@mail.gmail.com' \
    --to=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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 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.