Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
From: Sudip Mukherjee (Codethink)
Date: Tue Feb 14 2023 - 06:06:35 EST
Hi Greg,
On Mon, Feb 13, 2023 at 03:49:05PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.168 release.
> There are 139 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 should be made by Wed, 15 Feb 2023 14:46:51 +0000.
> Anything received after that time might be too late.
Build test (gcc version 11.3.1 20230210):
mips: 63 configs -> no failure
arm: 104 configs -> no failure
arm64: 3 configs -> no failure
x86_64: 4 configs -> no failure
alpha allmodconfig -> no failure
powerpc allmodconfig -> no failure
riscv allmodconfig -> no failure
s390 allmodconfig -> no failure
xtensa allmodconfig -> no failure
Boot test:
x86_64: Booted on qemu. New warning. [1]
[ 0.768162] sysfs: cannot create duplicate filename '/devices/pnp0/00:05/cmos_nvram0'
[ 0.768167] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.168-rc1 #1
[ 0.768168] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a-rebuilt.opensuse.org 04/01/2014
[ 0.768170] Call Trace:
[ 0.768184] dump_stack+0x72/0x92
[ 0.768187] sysfs_warn_dup.cold+0x17/0x2a
[ 0.768191] sysfs_create_dir_ns+0xbc/0xd0
[ 0.768194] kobject_add_internal+0xb4/0x300
[ 0.768195] kobject_add+0x81/0xb0
[ 0.768198] ? klist_children_get+0x1a/0x30
[ 0.768200] device_add+0xdc/0x820
[ 0.768203] ? acpi_fwnode_property_present+0x5a/0x70
[ 0.768206] nvmem_register+0x4d6/0x7e0
[ 0.768208] devm_nvmem_register+0x3f/0x80
[ 0.768211] rtc_nvmem_register+0x38/0xe0
[ 0.768213] cmos_do_probe+0x56b/0x610
[ 0.768215] ? cmos_set_alarm_callback+0xd0/0xd0
[ 0.768216] ? rtc_handler+0xe0/0xe0
[ 0.768218] cmos_pnp_probe+0x74/0xa0
[ 0.768220] pnp_device_probe+0xc2/0x170
[ 0.768222] ? cmos_do_probe+0x610/0x610
[ 0.768223] really_probe+0x28a/0x470
[ 0.768225] driver_probe_device+0xec/0x160
[ 0.768227] device_driver_attach+0xb3/0xc0
[ 0.768229] ? device_driver_attach+0xc0/0xc0
[ 0.768230] __driver_attach+0xae/0x160
[ 0.768232] ? device_driver_attach+0xc0/0xc0
[ 0.768234] bus_for_each_dev+0x7c/0xc0
[ 0.768235] driver_attach+0x1e/0x30
[ 0.768237] bus_add_driver+0x148/0x210
[ 0.768239] driver_register+0x8f/0xf0
[ 0.768241] ? rtc_dev_init+0x39/0x39
[ 0.768243] pnp_register_driver+0x20/0x30
[ 0.768244] cmos_init+0x16/0x7d
[ 0.768245] ? rtc_dev_init+0x39/0x39
[ 0.768249] do_one_initcall+0x4a/0x1e0
[ 0.768251] kernel_init_freeable+0x22a/0x281
[ 0.768254] ? rest_init+0xbe/0xbe
[ 0.768255] kernel_init+0xe/0x112
[ 0.768257] ret_from_fork+0x22/0x30
[ 0.768259] kobject_add_internal failed for cmos_nvram0 with -EEXIST, don't try to register things with the same name in the same directory.
arm64: Booted on rpi4b (4GB model). No regression. [2]
Regression:
x86_64: Boot failed on my test laptop with a panic. Will try a bisect later today.
[1]. https://openqa.qa.codethink.co.uk/tests/2856
[2]. https://openqa.qa.codethink.co.uk/tests/2857
Tested-by: Sudip Mukherjee <sudip.mukherjee@xxxxxxxxxxxxxxx>
--
Regards
Sudip