From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/7] kernel-yocto: conslidated pull request
Date: Fri, 01 Sep 2017 17:08:04 +0100 [thread overview]
Message-ID: <1504282084.2175.59.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1504207711.git.bruce.ashfield@windriver.com>
On Thu, 2017-08-31 at 15:30 -0400, Bruce Ashfield wrote:
> Now that 4.12 + headers are in the tree, this is the next (and
> possibly final)
> around of -stable updates for the active kernels.
>
> I've built and booted them on all four architectures. But as usual,
> this is a lot of combinations to confirm.
>
> The 4.12 update doesn't specifically address the kernel traces that
> RP has been seeing, but it also doesn't regress things here. I'd be
> interested to know if they help/hinder in the search to find the root
> cause.
>
> I'll of course continue to track it down myself.
>
> I also have some functionality fixes as well as configuration updates
> as part of this update.
I ran these on the autobuilder. We did see:
https://autobuilder.yocto.io/builders/nightly-ppc/builds/465
which is the latest 4.12 kernel and the latest qemu hanging with no
boot output (but the pid did appear).
So we're still seeing something odd with ppc occasionally. Why? Don't
know :(
Cheers,
Richard
next prev parent reply other threads:[~2017-09-01 16:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 19:30 [PATCH 0/7] kernel-yocto: conslidated pull request Bruce Ashfield
2017-08-31 19:30 ` [PATCH 1/7] linux-yocto/4.10: fix aufs build Bruce Ashfield
2017-09-01 1:27 ` Kevin Hao
2017-09-01 1:53 ` Bruce Ashfield
2017-08-31 19:30 ` [PATCH 2/7] linux-yoct/4.12: fix yaffs2 build Bruce Ashfield
2017-08-31 19:33 ` Bruce Ashfield
2017-08-31 19:31 ` [PATCH 3/7] linux-yocto/4.10/4.9: fix BRCMFMAC_PROTO_MSGBUF warning Bruce Ashfield
2017-08-31 19:31 ` [PATCH 4/7] linux-yocto/4.12: silence qeumarma9 config warnings Bruce Ashfield
2017-08-31 19:31 ` [PATCH 5/7] linux-yocto/4.12: update to v4.12.10 Bruce Ashfield
2017-08-31 19:31 ` [PATCH 6/7] linux-yocto/4.9: update to v4.9.46 Bruce Ashfield
2017-08-31 19:31 ` [PATCH 7/7] linux-yocto/4.4: update to v4.4.85 Bruce Ashfield
2017-09-01 16:08 ` Richard Purdie [this message]
2017-09-01 16:30 ` [PATCH 0/7] kernel-yocto: conslidated pull request Bruce Ashfield
2017-09-05 14:13 ` Richard Purdie
2017-09-05 14:24 ` Bruce Ashfield
2017-09-05 14:59 ` Richard Purdie
2017-09-05 15:03 ` Bruce Ashfield
2017-09-11 2:34 ` Bruce Ashfield
2017-09-13 13:27 ` Bruce Ashfield
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=1504282084.2175.59.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.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.