[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200618163341.12f7c996@collabora.com>
Date: Thu, 18 Jun 2020 16:33:41 +0200
From: Boris Brezillon <boris.brezillon@...labora.com>
To: Guillaume Tucker <guillaume.tucker@...labora.com>
Cc: Miquel Raynal <miquel.raynal@...tlin.com>,
Boris Brezillon <bbrezillon@...nel.org>,
Vignesh Raghavendra <vigneshr@...com>,
Yoshio Furuyama <ytc-mb-yfuruyama7@...xia.com>,
Allison Randal <allison@...utok.net>,
Sascha Hauer <s.hauer@...gutronix.de>,
kernelci-results@...ups.io, Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, Stefan Agner <stefan@...er.ch>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-mtd@...ts.infradead.org, Richard Weinberger <richard@....at>,
Enrico Weigelt <info@...ux.net>,
Mason Yang <masonccyang@...c.com.tw>,
linux-next@...r.kernel.org
Subject: Re: next/master bisection: baseline.login on
ox820-cloudengines-pogoplug-series-3
On Thu, 18 Jun 2020 15:23:45 +0100
Guillaume Tucker <guillaume.tucker@...labora.com> wrote:
> On 18/06/2020 15:09, Miquel Raynal wrote:
> > Hi Guillaume,
> >
> > Miquel Raynal <miquel.raynal@...tlin.com> wrote on Thu, 18 Jun 2020
> > 15:23:24 +0200:
> >
> >> Hi Guillaume,
> >>
> >> Guillaume Tucker <guillaume.tucker@...labora.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.
If you're testing linux-next that shouldn't help us much (nand/next is
pulled in linux-next already), but maybe it's just about making the
bisection easier for kernelci (less commits to inspect), in which case
that's probably a good idea. You might also want to add mtd/next,
spi-nor/next and cfi/next so the entire MTD subsystem gets tested.
Powered by blists - more mailing lists