Message-ID: <9165173c-2171-4d71-a575-e3e7aebe8ccd@roeck-us.net>
Date: Mon, 23 Dec 2024 04:15:57 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Fabio Estevam <festevam@...x.de>,
	Linus Walleij <linus.walleij@...aro.org>,
	Waiman Long <longman@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: Linux 6.13-rc4

On Sun, Dec 22, 2024 at 01:27:59PM -0800, Linus Torvalds wrote:
> So this definitely is looking a bit smaller than most rc4s, and I
> expect (and hope) that rc5 will be absolutely tiny because you should
> all already be relaxing over the xmas holidays.
> 
> But hey, if somebody is out there keeping the lights on, please do
> keep testing. Nothing particularly exciting happened last week, but
> appended is the obligatory shortlog for people who want to get an
> overview of the details.
> 

Build results:
	total: 161 pass: 161 fail: 0
Qemu test results:
	total: 544 pass: 529 fail: 15
Failed tests:
	arm:imx25-pdk:imx_v4_v5_defconfig:nonand:mem128:net=default:imx25-pdk:initrd
	arm:imx25-pdk:imx_v4_v5_defconfig:nonand:sd:mem128:net=default:imx25-pdk:ext2
	arm:imx25-pdk:imx_v4_v5_defconfig:nonand:usb0:mem128:net=default:imx25-pdk:ext2
	arm:imx25-pdk:imx_v4_v5_defconfig:nonand:usb1:mem128:net=default:imx25-pdk:ext2
	arm:mcimx6ul-evk:imx_v6_v7_defconfig:nodrm:mem256:net=nic:net=nic:imx6ul-14x14-evk:initrd
	arm:mcimx6ul-evk:imx_v6_v7_defconfig:nodrm:sd:mem256:net=nic:net=nic:imx6ul-14x14-evk:ext2
	arm:mcimx6ul-evk:imx_v6_v7_defconfig:nodrm:usb0:mem256:net=nic:net=nic:imx6ul-14x14-evk:ext2
	arm:mcimx6ul-evk:imx_v6_v7_defconfig:nodrm:usb1:mem256:net=nic:net=nic:imx6ul-14x14-evk:ext2
	arm:mcimx7d-sabre:imx_v6_v7_defconfig:nodrm:smp2:mem256:net=nic:imx7d-sdb:initrd
	arm:mcimx7d-sabre:imx_v6_v7_defconfig:nodrm:smp2:usb1:mem256:net=nic:imx7d-sdb:ext2
	arm:mcimx7d-sabre:imx_v6_v7_defconfig:nodrm:smp2:sd:mem256:net=nic:imx7d-sdb:ext2
	arm:sabrelite:imx_v6_v7_defconfig:nodrm:mem256:net=default:imx6dl-sabrelite:initrd
	arm:sabrelite:imx_v6_v7_defconfig:nodrm:mmc,b300:mem256:net=default:imx6dl-sabrelite:ext2
	arm:sabrelite:imx_v6_v7_defconfig:nodrm:usb0:mem256:net=default:imx6dl-sabrelite:ext2
	arm:sabrelite:imx_v6_v7_defconfig:nodrm:usb1:mem256:net=default:imx6dl-sabrelite:ext2
Unit test results:
	pass: 467022 fail: 0

Good news is that the allyesconfig builds now pass. However, imx images
still fail to boot, and

[ BUG: Invalid wait context ]

is still reported when booting sparc64 images.

Fixes are:

a2878100c96e ARM: imx: Re-introduce the PINCTRL selection
801330b9aa3c locking/lockdep: Enforce PROVE_RAW_LOCK_NESTING only if ARCH_SUPPORTS_RT

available in my fixes branch at
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git (fetch).
I attached the detailed description below for reference and copied the authors
and maintainers.

Guenter

---
commit a2878100c96e3ff5eeeb64d0536ec94498773c58
Author:     Fabio Estevam <festevam@...x.de>
AuthorDate: Wed Nov 27 16:06:05 2024 -0300
Commit:     Guenter Roeck <linux@...ck-us.net>
CommitDate: Sun Dec 22 13:55:10 2024 -0800

    ARM: imx: Re-introduce the PINCTRL selection
    
    Since commit 17d210018914 ("ARM: imx: Allow user to disable pinctrl"),
    the CONFIG_PINCTRL option is no longer implicitly selected, causing
    several i.MX SoC pinctrl drivers no longer getting selected by default.
    
    This causes boot regressions on the ARMv4, ARMv5, ARMv6 and ARMv7
    i.MX SoCs.
    
    Fix it by selecting CONFIG_PINCTRL as before.
    
    This defeats the purpose of 7d210018914 ("ARM: imx: Allow user to disable
    pinctrl"), but it is the less invasive fix for the boot regressions.
    
    The attempt to build Layerscape without pinctrl can still be explored
    later as suggested by Arnd:
    
    "Overall, my best advice here is still to not change the way
    i.MX pinctrl works at all, but just fix Layerscape to not depend
    on i.MX. The reason for the 'select' here is clearly that the
    i.MX machines would fail to boot without pinctrl, and changing
    that because of Layerscape seems backwards."
    
    Fixes: 17d210018914 ("ARM: imx: Allow user to disable pinctrl")
    Reported-by: Guenter Roeck <linux@...ck-us.net>
    Closes: https://lore.kernel.org/linux-arm-kernel/49ff070a-ce67-42d7-84ec-8b54fd7e9742@roeck-us.net/
    Signed-off-by: Fabio Estevam <festevam@...x.de>
    Acked-by: Arnd Bergmann <arnd@...db.de>
    Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
    Tested-by: Guenter Roeck <linux@...ck-us.net>
    Link: https://lore.kernel.org/20241127190605.1367157-1-festevam@gmail.com
    Signed-off-by: Linus Walleij <linus.walleij@...aro.org>
    Signed-off-by: Guenter Roeck <linux@...ck-us.net>

commit 801330b9aa3ca0a8dbf1ad277dc0b95623d89aeb
Author:     Waiman Long <longman@...hat.com>
AuthorDate: Wed Nov 27 21:00:09 2024 -0500
Commit:     Guenter Roeck <linux@...ck-us.net>
CommitDate: Sun Dec 22 13:55:10 2024 -0800

    locking/lockdep: Enforce PROVE_RAW_LOCK_NESTING only if ARCH_SUPPORTS_RT
    
    Relax the rule to set PROVE_RAW_LOCK_NESTING by default only for arches
    that supports PREEMPT_RT.  For arches that do not support PREEMPT_RT,
    they will not be forced to address unimportant raw lock nesting issues
    when they want to enable PROVE_LOCKING.  They do have the option
    to enable it to look for these raw locking nesting problems if they
    choose to.
    
    Suggested-by: Guenter Roeck <linux@...ck-us.net>
    Signed-off-by: Waiman Long <longman@...hat.com>
    Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org>
    Tested-by: Guenter Roeck <linux@...ck-us.net>
    Link: https://lore.kernel.org/r/20241128020009.83347-1-longman@redhat.com
    Signed-off-by: Guenter Roeck <linux@...ck-us.net>

Powered by blists - more mailing lists