From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Yoshio Furuyama <ytc-mb-yfuruyama7@kioxia.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
kernelci-results@groups.io,
Boris Brezillon <bbrezillon@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, Stefan Agner <stefan@agner.ch>,
Boris Brezillon <boris.brezillon@collabora.com>,
linux-mtd@lists.infradead.org, linux-next@vger.kernel.org,
Richard Weinberger <richard@nod.at>,
Thomas Gleixner <tglx@linutronix.de>,
Mason Yang <masonccyang@mxic.com.tw>,
Enrico Weigelt <info@metux.net>,
Allison Randal <allison@lohutok.net>
Subject: Re: next/master bisection: baseline.login on ox820-cloudengines-pogoplug-series-3
Date: Thu, 18 Jun 2020 15:23:45 +0100 [thread overview]
Message-ID: <0c00fe0b-c38b-3d69-8f93-3fe8c3675113@collabora.com> (raw)
In-Reply-To: <20200618160925.6f77b1d1@xps13>
On 18/06/2020 15:09, Miquel Raynal wrote:
> Hi Guillaume,
>
> Miquel Raynal <miquel.raynal@bootlin.com> wrote on Thu, 18 Jun 2020
> 15:23:24 +0200:
>
>> Hi Guillaume,
>>
>> Guillaume Tucker <guillaume.tucker@collabora.com> wrote on Thu, 18 Jun
>> 2020 13:28:05 +0100:
>>
>>> Please see the bisection report below about a kernel panic.
>>>
>>> Reports aren't automatically sent to the public while we're
>>> trialing new bisection features on kernelci.org but this one
>>> looks valid.
>>>
>>> See the kernel Oops due to a NULL pointer followed by a panic:
>>>
>>> https://storage.kernelci.org/next/master/next-20200618/arm/oxnas_v6_defconfig/gcc-8/lab-baylibre/baseline-ox820-cloudengines-pogoplug-series-3.html#L504
>>
>> Thanks for the report, I will not be able to manage it before Monday,
>> but I'll try to take care of it early next week.
>
> Actually Boris saw the issue, I just updated nand/next, it should be
> part of tomorrow's linux-next. Could you please report if it fixes your
> boot?
Sure, will check tomorrow. Thanks for the update.
We may also consider adding the nand/next branch to kernelci.org
and catch issues earlier. We can discuss that separately.
Guillaume
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-06-18 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5eeb5bf7.1c69fb81.4f6e3.8979@mx.google.com>
2020-06-18 12:28 ` next/master bisection: baseline.login on ox820-cloudengines-pogoplug-series-3 Guillaume Tucker
2020-06-18 13:23 ` Miquel Raynal
2020-06-18 14:09 ` Miquel Raynal
2020-06-18 14:23 ` Guillaume Tucker [this message]
2020-06-18 14:33 ` Boris Brezillon
2020-06-18 14:36 ` next/master bisection: baseline.login on ox820-cloudengines-pogoplug-series-3N Miquel Raynal
2020-06-18 14:59 ` Guillaume Tucker
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=0c00fe0b-c38b-3d69-8f93-3fe8c3675113@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=allison@lohutok.net \
--cc=bbrezillon@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=info@metux.net \
--cc=kernelci-results@groups.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=masonccyang@mxic.com.tw \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=s.hauer@pengutronix.de \
--cc=stefan@agner.ch \
--cc=tglx@linutronix.de \
--cc=vigneshr@ti.com \
--cc=ytc-mb-yfuruyama7@kioxia.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).