From: Mark Brown <broonie@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Alexandre Courbot <gnurou@gmail.com>,
Jiri Slaby <jslaby@suse.com>, Arnd Bergmann <arnd@arndb.de>,
kernel-build-reports@lists.linaro.org,
linux-next@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org
Subject: Re: next boot: 564 boots: 59 failed, 448 passed with 57 offline (next-20160107)
Date: Fri, 8 Jan 2016 02:47:55 +0000 [thread overview]
Message-ID: <20160108024755.GK6588@sirena.org.uk> (raw)
In-Reply-To: <20160107185739.GA29951@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
On Thu, Jan 07, 2016 at 10:57:39AM -0800, Greg Kroah-Hartman wrote:
> On Thu, Jan 07, 2016 at 05:28:10PM +0100, Thierry Reding wrote:
> > On Thu, Jan 07, 2016 at 03:59:58PM +0000, Mark Brown wrote:
> > I think this is merely waiting to be picked up into the tty tree. I
> > suspect the reason why there's output in the first place is because
> > of earlyprintk. I've seen recent linux-next work properly, with the
> > serial console hanging at some point (fbcon shows login prompt). If
> > I apply the above patch things are back to normal.
> I'll go queue that up later, but how is this suddenly showing up in
> -next? The tty tree has been pretty quiet for a while now..
There were some memory management issues which broke booting on almost
all ARM platforms for most of this week so nothing else was really
visible and relatively few -next builds over the Christmas vacation (as
one would expect).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: next boot: 564 boots: 59 failed, 448 passed with 57 offline (next-20160107)
Date: Fri, 8 Jan 2016 02:47:55 +0000 [thread overview]
Message-ID: <20160108024755.GK6588@sirena.org.uk> (raw)
In-Reply-To: <20160107185739.GA29951@kroah.com>
On Thu, Jan 07, 2016 at 10:57:39AM -0800, Greg Kroah-Hartman wrote:
> On Thu, Jan 07, 2016 at 05:28:10PM +0100, Thierry Reding wrote:
> > On Thu, Jan 07, 2016 at 03:59:58PM +0000, Mark Brown wrote:
> > I think this is merely waiting to be picked up into the tty tree. I
> > suspect the reason why there's output in the first place is because
> > of earlyprintk. I've seen recent linux-next work properly, with the
> > serial console hanging at some point (fbcon shows login prompt). If
> > I apply the above patch things are back to normal.
> I'll go queue that up later, but how is this suddenly showing up in
> -next? The tty tree has been pretty quiet for a while now..
There were some memory management issues which broke booting on almost
all ARM platforms for most of this week so nothing else was really
visible and relatively few -next builds over the Christmas vacation (as
one would expect).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160108/e4e9f71c/attachment-0001.sig>
next prev parent reply other threads:[~2016-01-08 2:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <568e8740.01941c0a.31072.ffffb67b@mx.google.com>
[not found] ` <568e8740.01941c0a.31072.ffffb67b-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org>
2016-01-07 15:59 ` next boot: 564 boots: 59 failed, 448 passed with 57 offline (next-20160107) Mark Brown
2016-01-07 15:59 ` Mark Brown
2016-01-07 16:28 ` Thierry Reding
2016-01-07 16:28 ` Thierry Reding
2016-01-07 16:56 ` Mark Brown
2016-01-07 16:56 ` Mark Brown
2016-01-07 18:57 ` Greg Kroah-Hartman
2016-01-07 18:57 ` Greg Kroah-Hartman
2016-01-08 2:47 ` Mark Brown [this message]
2016-01-08 2:47 ` Mark Brown
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=20160108024755.GK6588@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=gnurou@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@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.