Hi Sahil,
Please see the bisection report below about a boot failure on
kontron-kbox-a-230-ls on linux-next.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
The kernel is hitting this issue:
[5.326403]
Hi Ray,
Please see the bisection report below about a boot failure on
rk3399-gru-kevin on linux-next.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
The boot log shows a kernel panic with a NULL pointer
On 02/03/2021 12:40, Greg Kroah-Hartman wrote:
> On Tue, Mar 02, 2021 at 11:38:36AM +0000, Guillaume Tucker wrote:
>> On 01/03/2021 19:37, Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 5.10.20 release.
>>> There are 661
On 02/03/2021 19:28, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.20 release.
> There are 657 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 01/03/2021 19:37, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.20 release.
> There are 661 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 24/02/2021 08:52, Marc Zyngier wrote:
> On Tue, 23 Feb 2021 21:03:52 +,
> Guillaume Tucker wrote:
>>
>> On 23/02/2021 14:18, Marc Zyngier wrote:
>>> Hi Guillaume,
>>>
>>> On Tue, 23 Feb 2021 09:46:30 +,
>>> Guillaume Tuc
On 23/02/2021 14:18, Marc Zyngier wrote:
> Hi Guillaume,
>
> On Tue, 23 Feb 2021 09:46:30 +,
> Guillaume Tucker wrote:
>>
>> Hello Marc,
>>
>> Please see the bisection report below about a boot failure on
>> meson-sm1-khadas-vim3l on mainline. It s
Hi Christoph,
Please see the bisection report below about a boot failure on
r8a77960-ulcb on next-20210222.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
The log shows a kernel panic, more details can be
Hello Marc,
Please see the bisection report below about a boot failure on
meson-sm1-khadas-vim3l on mainline. It seems to only be
affecting kernels built with CONFIG_ARM64_64K_PAGES=y.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org
oned commit.
>
> Once we have the linear map solution for framebuffer memory, this change
> can be cleaned away.
>
> [Big thank to Guillaume who reported and helped debugging/verification]
>
> Fixes: 25938c73cd79 ("iommu/tegra-smmu: Rework tegra_smmu_probe_device()"
On 18/02/2021 10:35, Nicolin Chen wrote:
> Hi Guillaume,
>
> Thank you for the test results! And sorry for my belated reply.
No worries :)
> On Thu, Feb 11, 2021 at 03:50:05PM +0000, Guillaume Tucker wrote:
>>> On Sat, Feb 06, 2021 at 01:40:13PM +0000, Guillaume Tuc
On 10/02/2021 08:20, Nicolin Chen wrote:
> Hi Guillaume,
>
> On Sat, Feb 06, 2021 at 01:40:13PM +, Guillaume Tucker wrote:
>>> It'd be nicer if I can get both logs of the vanilla kernel (failing)
>>> and the commit-reverted version (passing), each applying this pa
On 05/02/2021 09:45, Nicolin Chen wrote:
> Hi Guillaume,
>
> On Thu, Feb 04, 2021 at 09:24:23PM -0800, Nicolin Chen wrote:
>>> Please let us know if you need any help debugging this issue or
>>> to try a fix on this platform.
>>
>> Yes, I don't have any Tegra124 platform to run. It'd be very nice
On 05/02/2021 12:05, Ard Biesheuvel wrote:
> On Fri, 5 Feb 2021 at 09:21, Ard Biesheuvel wrote:
>>
>> On Thu, 4 Feb 2021 at 22:31, Guillaume Tucker
>> wrote:
>>>
>>> On 04/02/2021 18:23, Nick Desaulniers wrote:
>>>> On Thu, Feb
>>>
>>>> On Thu, 4 Feb 2021 at 16:53, Guillaume Tucker
>>>> wrote:
>>>>>
>>>>> On 04/02/2021 15:42, Ard Biesheuvel wrote:
>>>>>> On Thu, 4 Feb 2021 at 12:32, Guillaume Tucker
>>>>>> wrote:
>>&
On 04/02/2021 16:01, Ard Biesheuvel wrote:
> On Thu, 4 Feb 2021 at 16:53, Guillaume Tucker
> wrote:
>>
>> On 04/02/2021 15:42, Ard Biesheuvel wrote:
>>> On Thu, 4 Feb 2021 at 12:32, Guillaume Tucker
>>> wrote:
>>>>
>>>> On 04/02/2021 1
On 04/02/2021 15:42, Ard Biesheuvel wrote:
> On Thu, 4 Feb 2021 at 12:32, Guillaume Tucker
> wrote:
>>
>> On 04/02/2021 10:33, Guillaume Tucker wrote:
>>> On 04/02/2021 10:27, Ard Biesheuvel wrote:
>>>> On Thu, 4 Feb 2021 at 11:06, Russell King - ARM Linu
On 04/02/2021 10:33, Guillaume Tucker wrote:
> On 04/02/2021 10:27, Ard Biesheuvel wrote:
>> On Thu, 4 Feb 2021 at 11:06, Russell King - ARM Linux admin
>> wrote:
>>>
>>> On Thu, Feb 04, 2021 at 10:07:58AM +0100, Ard Biesheuvel wrote:
>>>> On Thu, 4 Fe
Hi Nicolin,
A regression was detected by kernelci.org in IGT's drm_read tests
on mainline, it was first seen on 17th December 2020. You can
find some details here:
https://kernelci.org/test/case/id/600b82dc1e3208f123d3dffc/
Then an automated bisection was run and it landed on this
patch
On 04/02/2021 10:27, Ard Biesheuvel wrote:
> On Thu, 4 Feb 2021 at 11:06, Russell King - ARM Linux admin
> wrote:
>>
>> On Thu, Feb 04, 2021 at 10:07:58AM +0100, Ard Biesheuvel wrote:
>>> On Thu, 4 Feb 2021 at 09:43, Guillaume Tucker
>>> wrote:
&g
Hi Samuel,
Please see the bisection report below about a boot failure on
sun50i-h5-libretech-all-h3-cc with next-20210203.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
The kernel is most likely crashing
Hi Ard,
Please see the bisection report below about a boot failure on
rk3288 with next-20210203. It was also bisected on
imx6q-var-dt6customboard with next-20210202.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks
Hi Saravana,
Please see the bisection report below about the clk-mt8173-mm and
mtk-mmsys drivers failing to probe on mt8173-elm-hana with
next-20210111.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
Some
Hi Vincent,
Please see the bisection report below about a boot failure on
rk3328-rock64 with the pwmg/integ branch.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
There's nothing in the serial console log,
On 12/01/2021 10:53, Guillaume Tucker wrote:
> On 05/01/2021 09:13, Mike Rapoport wrote:
>> On Sun, Jan 03, 2021 at 03:09:14PM -0500, Andrea Arcangeli wrote:
>>> Hello Mike,
>>>
>>> On Sun, Jan 03, 2021 at 03:47:53PM +0200, Mike Rapoport wrote:
>>>&g
On 05/01/2021 09:13, Mike Rapoport wrote:
> On Sun, Jan 03, 2021 at 03:09:14PM -0500, Andrea Arcangeli wrote:
>> Hello Mike,
>>
>> On Sun, Jan 03, 2021 at 03:47:53PM +0200, Mike Rapoport wrote:
>>> Thanks for the logs, it seems that implicitly adding reserved regions to
>>> memblock.memory wasn't
On 13/12/2020 08:23, Mike Rapoport wrote:
> Hi Guillaume,
>
> On Fri, Dec 11, 2020 at 09:53:46PM +, Guillaume Tucker wrote:
>> Hi Mike,
>>
>> Please see the bisection report below about a boot failure on
>> rk3288 with next-20201210.
>>
>> Reports
Hi Ard,
Please see the bisection report below about a boot failure on
ox820-cloudengines-pogoplug-series-3. There was also a bisection
yesterday with next-20201216 which landed on the same commit, on
the same platform and also with oxnas_v6_defconfig. I'm not
aware of any other platform on
On 16/12/2020 12:41, Linus Walleij wrote:
> On Wed, Dec 16, 2020 at 11:10 AM Guillaume Tucker
> wrote:
>
>>> It seems we need to teach the core to ignore the name (empty string).
>>
>> OK great, I see you've sent a patch for that. I'll check if we
>> can c
On 15/12/2020 12:20, Linus Walleij wrote:
> On Mon, Dec 14, 2020 at 11:28 PM Guillaume Tucker
> wrote:
>
>> Please see the bisection report below about the pinctrl driver
>> failing to probe on the arm64 mt8173-elm-hana platform.
>
> That's an excellent, helpf
Hi Linus,
Please see the bisection report below about the pinctrl driver
failing to probe on the arm64 mt8173-elm-hana platform.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
This is the error message:
[
Hi Mike,
Please see the bisection report below about a boot failure on
rk3288 with next-20201210.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
There's nothing in the serial console log, probably because
der features.
>
> Fixes: b33340e33acd ("drm/meson: dw-hdmi: Ensure that clocks are enabled
> before touching the TOP registers")
> Reported-by: Guillaume Tucker
Although I am triaging kernelci bisections, it was initially
found thanks to our friendly bot. So if you're OK w
Hi Marc,
On 19/11/2020 11:58, Marc Zyngier wrote:
> On 2020-11-19 10:26, Neil Armstrong wrote:
>> On 19/11/2020 11:20, Marc Zyngier wrote:
>>> On 2020-11-19 08:50, Guillaume Tucker wrote:
>>>> Please see the automated bisection report below about some kernel
Please see the automated bisection report below about some kernel
errors on meson-gxbb-p200.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org, however this one
looks valid.
The bisection started with next-20201118 but the errors are
;> On Fri, 13 Nov 2020 at 17:15, Ard Biesheuvel wrote:
>>>>>
>>>>> On Fri, 13 Nov 2020 at 16:58, Russell King - ARM Linux admin
>>>>> wrote:
>>>>>>
>>>>>> On Fri, Nov 13, 2020 at 03:43:27PM +, Guillaume Tucker wrote:
>>>
On 13/11/2020 10:35, Ard Biesheuvel wrote:
> On Fri, 13 Nov 2020 at 11:31, Guillaume Tucker
> wrote:
>>
>> Hi Ard,
>>
>> Please see the bisection report below about a boot failure on
>> RPi-2b.
>>
>> Reports aren't automatically sent to the publi
Hi Ard,
Please see the bisection report below about a boot failure on
RPi-2b.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
There's nothing in the serial console log, probably because it's
crashing too early
ith a real-time clock.
Tested on rk3288-rock2-square, which has an IRQ configured for the
RTC. As a result, wakeup was enabled during driver initialisation.
Fixes: dcaf03849352 ("rtc: add hym8563 rtc-driver")
Reported-by: kernelci.org bot
Signed-off-by: Guillaume Tucker
---
Notes:
On 05/11/2020 22:09, Alexandre Belloni wrote:
> On 05/11/2020 22:01:10+0000, Guillaume Tucker wrote:
>> Enable wakeup by default in the hym8563 driver to match the behaviour
>> implemented by the majority of RTC drivers. As per the description of
>> device_init_wakeup(),
real-time clock.
Fixes: dcaf03849352 ("rtc: add hym8563 rtc-driver")
Reported-by: kernelci.org bot
Signed-off-by: Guillaume Tucker
---
drivers/rtc/rtc-hym8563.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-hym8563.c b/drivers/rtc/rtc-hym8563.
On 12/10/2020 15:40, Willy Tarreau wrote:
> On Mon, Oct 12, 2020 at 04:32:12PM +0200, Borislav Petkov wrote:
>> On Mon, Oct 12, 2020 at 11:22:10AM +0100, Guillaume Tucker wrote:
>>> However, it was found while adding some x86 Chromebooks[1] to
>>> KernelCI that x86_64_
On 12/10/2020 04:58, Willy Tarreau wrote:
> Hi Enric,
>
> On Sun, Oct 11, 2020 at 07:05:55PM +0200, Enric Balletbo i Serra wrote:
>> For arm64 (i.e : arm64_defconfig):
>> 1. Someone renames CONFIG_A to CONFIG_AB, sends a patch, and as he did a
>> grep, the patch modifies all the defconfigs.
On 30/09/2020 09:05, Guillaume Tucker wrote:
> Please see the bisection report below about a regression in
> v4l2-compliance on vivid.
>
> Reports aren't automatically sent to the public while we're
> trialing new bisection features on kernelci.org but this one
> looks valid
Please see the bisection report below about a regression in
v4l2-compliance on vivid.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
The full results for v4l2-compliance on vivid for
Hi Marc,
On 24/09/2020 14:09, Guillaume Tucker wrote:
> On 24/09/2020 10:29, Marc Zyngier wrote:
>> Hi Guillaume,
>>
>> On Thu, 24 Sep 2020 10:00:09 +0100,
>> Guillaume Tucker wrote:
>>>
>>> Hi Marc,
>>>
>>> On 01/09/2020 15:43,
On 24/09/2020 14:34, Fabio Estevam wrote:
> Hi Guillaume,
>
> On Thu, Sep 24, 2020 at 6:01 AM Guillaume Tucker
> wrote:
>
>> This appears to be causing a NULL pointer dereference on
>> beaglebone-black, it got bisected automatically several times.
>> None of th
On 24/09/2020 10:29, Marc Zyngier wrote:
> Hi Guillaume,
>
> On Thu, 24 Sep 2020 10:00:09 +0100,
> Guillaume Tucker wrote:
>>
>> Hi Marc,
>>
>> On 01/09/2020 15:43, Marc Zyngier wrote:
>>> Let's switch the arm code to the core accounti
Hi Marc,
On 01/09/2020 15:43, Marc Zyngier wrote:
> Let's switch the arm code to the core accounting, which already
> does everything we need.
>
> Reviewed-by: Valentin Schneider
> Signed-off-by: Marc Zyngier
> ---
> arch/arm/include/asm/hardirq.h | 17 -
>
On 16/09/2020 17:30, Mike Kravetz wrote:
> On 9/16/20 2:14 AM, Song Bao Hua (Barry Song) wrote:
-Original Message-
From: Mike Kravetz [mailto:mike.krav...@oracle.com]
Sent: Wednesday, September 16, 2020 8:57 AM
To: linux...@kvack.org; linux-kernel@vger.kernel.org;
On 01/09/2020 16:25, Krzysztof Kozlowski wrote:
> On Tue, 1 Sep 2020 at 16:42, Guillaume Tucker
> wrote:
>>
>> On 01/09/2020 14:51, Krzysztof Kozlowski wrote:
>>> On Tue, 1 Sep 2020 at 15:45, Krzysztof Kozlowski wrote:
>>>>
>>>> On Tue
On 01/09/2020 14:51, Krzysztof Kozlowski wrote:
> On Tue, 1 Sep 2020 at 15:45, Krzysztof Kozlowski wrote:
>>
>> On Tue, 1 Sep 2020 at 15:34, Guillaume Tucker
>> wrote:
>>>
>>> Hi Krzysztof, Russell,
>>>
>>> On 10/08/2020 13:22, Guilla
Hi Krzysztof, Russell,
On 10/08/2020 13:22, Guillaume Tucker wrote:
> The L310_AUX_CTRL_NS_LOCKDOWN flag is set during the L2C enable
> sequence. There is no need to set it in the default register value,
> this was done before support for it was implemented in the code. It
>
Please see the bisection report below about a boot failure.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
The log doesn't appear to be showing anything from the kernel, so
it's likely to be crashing very
Hi,
Please see the bisection report below about a driver probe
regression with rockchip-pcie.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
It seems to be due to this error:
<6>[ 16.842128]
On 29/07/2020 17:22, Guillaume Tucker wrote:
> On 29/07/2020 15:18, Russell King - ARM Linux admin wrote:
>> On Wed, Jul 29, 2020 at 02:47:32PM +0100, Guillaume Tucker wrote:
>>> The L310_PREFETCH_CTRL register bits 28 and 29 to enable data and
>>> instruction pre
On 03/08/2020 14:13, Krzysztof Kozlowski wrote:
> On Wed, Jul 29, 2020 at 02:47:33PM +0100, Guillaume Tucker wrote:
>> Use the standard l2c2x0 device tree bindings to enable data and
>> instruction prefetch on exynos4210 and exynos4412 and clear the
>> respective bits in th
On 03/08/2020 15:22, Russell King - ARM Linux admin wrote:
> On Mon, Aug 03, 2020 at 03:34:39PM +0200, Krzysztof Kozlowski wrote:
>> On Wed, Jul 29, 2020 at 02:47:31PM +0100, Guillaume Tucker wrote:
>>> The L220_AUX_CTRL_NS_LOCKDOWN flag is set during the L2C enable
>>>
the default l2c_aux_val, and
add it to the l2c_aux_mask to print an alert message if it was already
set before the kernel initialisation.
Signed-off-by: Guillaume Tucker
---
Notes:
v2: fix flag name L310_AUX_CTRL_NS_LOCKDOWN
arch/arm/mach-exynos/exynos.c | 4 ++--
1 file changed, 2 insertions
restoring the aux control register
later on. For this reason, set these bits in both registers during
initialisation according to the devicetree property values.
Fixes: ec3bd0e68a67 ("ARM: 8391/1: l2c: add options to overwrite prefetching
behavior")
Signed-off-by: Guillaume Tucker
now be cleared as a result.
Signed-off-by: Guillaume Tucker
---
Notes:
v2: split patch to include devicetree changes only
arch/arm/boot/dts/exynos4210.dtsi | 2 ++
arch/arm/boot/dts/exynos4412.dtsi | 2 ++
2 files changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4210.dtsi
b
Clear the L310_AUX_CTRL_DATA_PREFETCH and L310_AUX_CTRL_INSTR_PREFETCH
bits in the l2c_aux_val defaults for Exynos since they can now be set
using the standard l2c2x0 devicetree bindings.
Signed-off-by: Guillaume Tucker
---
Notes:
v2: split patch to only clear exynos platform register bits
On 29/07/2020 15:18, Russell King - ARM Linux admin wrote:
> On Wed, Jul 29, 2020 at 02:47:32PM +0100, Guillaume Tucker wrote:
>> The L310_PREFETCH_CTRL register bits 28 and 29 to enable data and
>> instruction prefetch respectively can also be accessed via the
>> L
the default l2c_aux_val, and
add it to the l2c_aux_mask to print an alert message if it was already
set before the kernel initialisation.
Signed-off-by: Guillaume Tucker
---
arch/arm/mach-exynos/exynos.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-exynos
restoring the aux control register
later on. For this reason, set these bits in both registers during
initialisation according to the DT attributes.
Fixes: ec3bd0e68a67 ("ARM: 8391/1: l2c: add options to overwrite prefetching
behavior")
Signed-off-by: Guillaume Tucker
---
arch/arm/mm/
Use the standard l2c2x0 device tree bindings to enable data and
instruction prefetch on exynos4210 and exynos4412 and clear the
respective bits in the default l2c_aux_val. No other Exynos platform
relying on this default register value appears to be using the l2x0
cache.
Signed-off-by: Guillaume
Hi André,
Sorry for the delay, I missed the thread on this issue.
On 03/07/2020 11:49, André Przywara wrote:
> On 03/07/2020 06:38, kernelci.org bot wrote:
>
> Hi Guillaume,
>
> is this report legit? The situation didn't change from Monday, I just
> repeated the test with mainline compared to
On 06/07/2020 13:49, Sudeep Holla wrote:
> Hi,
>
> On Sun, Jul 05, 2020 at 07:12:58PM -0700, kernelci.org bot wrote:
>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>> * This automated bisection report was sent to you on the basis *
>> * that you may be involved with the
On 09/07/2020 10:17, Enric Balletbo i Serra wrote:
> Hi,
>
> On 8/7/20 22:32, Guenter Roeck wrote:
>> On 7/8/20 11:59 AM, kernelci.org bot wrote:
>>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>>> * This automated bisection report was sent to you on the basis *
>>> * that
On 26/06/2020 20:11, kernelci.org bot wrote:
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * This automated bisection report was sent to you on the basis *
> * that you may be involved with the breaking commit it has *
> * found. No manual investigation has been done
ccordingly in the v4l-utils git
> repo.
I see, thanks. It's getting updated today.
Guillaume
> On 26/06/2020 08:56, Guillaume Tucker wrote:
>> Please see the bisection report below about a regression in
>> v4l2-compliance with uvcvideo:
>>
>> [ 25.495039] uvcvide
Please see the bisection report below about a regression in
v4l2-compliance with uvcvideo:
[ 25.495039] uvcvideo: Failed to query (SET_CUR) UVC control 10 on unit 2:
-32 (exp. 2).
fail: v4l2-test-buffers.cpp(680): check_0(reqbufs.reserved,
sizeof(reqbufs.reserved))
On 25/06/2020 06:24, kernelci.org bot wrote:
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * This automated bisection report was sent to you on the basis *
> * that you may be involved with the breaking commit it has *
> * found. No manual investigation has been done
oo random to ever
cause a bisection to succeed, I get this report which landed a
commit that I made, one week after enabling public bisection
email reports again. It must be trying to tell me something :)
Guillaume
> Breaking commit found:
>
> -------
On 18/06/2020 15:09, Miquel Raynal wrote:
> Hi Guillaume,
>
> Miquel Raynal wrote on Thu, 18 Jun 2020
> 15:23:24 +0200:
>
>> Hi Guillaume,
>>
>> Guillaume Tucker wrote on Thu, 18 Jun
>> 2020 13:28:05 +0100:
>>
>>> Please see the bisect
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:
On 02/04/2020 14:11, Russell King - ARM Linux admin wrote:
> On Thu, Apr 02, 2020 at 02:03:52PM +0100, Russell King - ARM Linux admin
> wrote:
>> On Thu, Apr 02, 2020 at 01:13:24PM +0100, Guillaume Tucker wrote:
>>> On 01/04/2020 17:31, Russell King - ARM Linux admin wrote
.
Reported-by: "kernelci.org bot"
Signed-off-by: Guillaume Tucker
---
arch/arm/mach-exynos/exynos.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c
index 7a8d1555db40..36c3785a 100644
--- a/arch/arm/mach
Please see the bisection report below about a kernel Oops.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
Guillaume
On 23/05/2020 18:46, kernelci.org bot wrote:
> * * * * * * * * * * * * * * * * * * * * * *
Please see the bisection report below about a boot failure.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
Unfortunately there isn't anything in the kernel log, it's
probably crashing very early on. The
On 12/05/2020 16:16, Joerg Roedel wrote:
> Hi Guillaume,
>
> thanks for the report!
>
> On Tue, May 12, 2020 at 07:05:13AM +0100, Guillaume Tucker wrote:
>>> Summary:
>>> Start: 4b20e7462caa6 Add linux-next specific files for 20200511
>>> Pla
As kernelci.org is expanding its functional testing
capabilities, the concept of boot testing is now being
deprecated.
Next Monday 18th May, the web dashboard on https://kernelci.org
will be updated to primarily show functional test results
rather than boot results. The Boots tab will still be
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:
Please see the bisection report below about a boot failure.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
It appears to be due to the fact that the network interface is
failing to get brought up:
[
Please see the bisection report below about a kernel Oops.
Reports aren't automatically sent to the public while we're
trialing new bisection features on kernelci.org but this one
looks valid.
The log shows a kernel NULL pointer dereference:
On 02/10/2019 18:26, Masahiro Yamada wrote:
> On Thu, Oct 3, 2019 at 2:24 AM David Miller wrote:
>>
>> From: Guillaume Tucker
>> Date: Wed, 2 Oct 2019 18:21:31 +0100
>>
>>> It seems like this isn't the case on the Raspberry Pi 2b with
>>> bcm283
On 02/10/2019 11:05, kernelci.org bot wrote:
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * This automated bisection report was sent to you on the basis *
> * that you may be involved with the breaking commit it has *
> * found. No manual investigation has been done
ke")
Signed-off-by: Guillaume Tucker
Cc: Jon Hunter
---
Notes:
v2: use true rather than echo as per Jon Hunter's suggestion
scripts/kconfig/merge_config.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/kconfig/merge_config.sh b/scripts/kconfig/merge_config.s
On 02/09/2019 15:32, Jon Hunter wrote:
>
> On 02/09/2019 15:26, Guillaume Tucker wrote:
>> On 02/09/2019 15:21, Jon Hunter wrote:
>>>
>>> On 02/09/2019 15:14, Guillaume Tucker wrote:
>>>> + Jon Hunter who hit a similar issue
>>>
>>> T
On 02/09/2019 15:21, Jon Hunter wrote:
>
> On 02/09/2019 15:14, Guillaume Tucker wrote:
>> + Jon Hunter who hit a similar issue
>
> Thanks for adding me.
>
>> On 28/08/2019 21:19, Guillaume Tucker wrote:
>>> The merge_config.sh script verifies that all the co
On 02/09/2019 15:06, Jon Hunter wrote:
>
> On 19/08/2019 21:06, Mark Brown wrote:
>> When we execute make after merging the configurations we ignore any
>> errors it produces causing whatever is running merge_config.sh to be
>> unaware of any failures. This issue was not
+ Jon Hunter who hit a similar issue
On 28/08/2019 21:19, Guillaume Tucker wrote:
> The merge_config.sh script verifies that all the config options have
> their expected value in the resulting file and prints any issues as
> warnings. These checks aren't intended to be treated as err
ke")
Signed-off-by: Guillaume Tucker
---
scripts/kconfig/merge_config.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/kconfig/merge_config.sh b/scripts/kconfig/merge_config.sh
index d924c51d28b7..d673268d414b 100755
--- a/scripts/kconfig/merge_config.sh
+++ b/scripts/kco
On 15/08/2019 17:00, Stephen Boyd wrote:
> I found some more cases where the init structure is referenced from
> within the clk_hw struct after clk_registration is called. I suspect the
> rtc driver fix is useful to avoid crashes on Allwinner devices, reported
> by kernel-ci.
Please feel free to
org
Signed-off-by: Guillaume Tucker
---
drivers/media/platform/vivid/vivid-ctrls.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/vivid/vivid-ctrls.c
b/drivers/media/platform/vivid/vivid-ctrls.c
index 3e916c8befb7..7a52f585cab7 100644
--- a/drivers/medi
Hi Martin,
On 18/06/2019 21:58, Martin Blumenstingl wrote:
> Hi Guillaume,
>
> On Tue, Jun 18, 2019 at 10:53 PM Guillaume Tucker
> wrote:
>>
>> On 18/06/2019 21:42, Martin Blumenstingl wrote:
>>> On Tue, Jun 18, 2019 at 6:53 PM Kevin Hilman wrote:
>>
On 18/06/2019 21:42, Martin Blumenstingl wrote:
> On Tue, Jun 18, 2019 at 6:53 PM Kevin Hilman wrote:
> [...]
>> This seems to have broken on several sunxi SoCs, but also a MIPS SoC
>> (pistachio_marduk):
>>
>>
On 30/05/2019 16:53, Takashi Iwai wrote:
> On Thu, 30 May 2019 11:16:22 +0200,
> kernelci.org bot wrote:
>>
>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>> * This automated bisection report was sent to you on the basis *
>> * that you may be involved with the breaking
Hi Geert,
On 28/05/2019 08:45, Geert Uytterhoeven wrote:
> Hi Guillaume,
>
> On Tue, May 28, 2019 at 9:13 AM Guillaume Tucker
> wrote:
>> On 28/05/2019 00:38, kernelci.org bot wrote:
>>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>>&g
Hi Linus,
On 28/05/2019 00:38, kernelci.org bot wrote:
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * This automated bisection report was sent to you on the basis *
> * that you may be involved with the breaking commit it has *
> * found. No manual investigation
1 - 100 of 217 matches
Mail list logo
