5.10.168-rc1 review

Hi Greg and Florian,

Quoted 24 lines · Florian Fainelli

Quoted 9 lines · Greg Kroah-Hartman

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.

The whole patch series can be found in one patch at:

Quoted 8 lines

      https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.168-rc1.gz

or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
and the diffstat can be found below.

thanks,

greg k-h

There is a regression coming from:

nvmem: core: fix registration vs use race

Quoted 8 lines

which causes the following to happen for MTD devices:

[    6.031640] kobject_add_internal failed for mtd0 with -EEXIST, don't
try to register things with the same name in the same directory.
[    7.846965] spi-nor: probe of spi0.0 failed with error -17

attached is a full log with the call trace. This does not happen with v6.2-rc8 where the MTD partitions are successfully registered.qfprom

Like said above,

[    5.965191] kobject_add_internal failed for qfprom0 with -EEXIST,
don't try to register things with the same name in the same directory.
[    5.969110] qcom,qfprom: probe of 5c000.qfprom failed with error -17

Following kernel crash noticed on arm64 Qcom dragonboard 410c device.

We will bisect this problem and get back to you soon.

Reported-by Linux Kernel Functional Testing <[email protected]>

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd030]
[    0.000000] Linux version 5.10.168-rc1 (tuxmake@tuxmake)
(aarch64-linux-gnu-gcc (Debian 11.3.0-11) 11.3.0, GNU ld (GNU Binutils
for Debian) 2.40) #1 SMP PREEMPT @1676300748
[    0.000000] Machine model: Qualcomm Technologies, Inc. APQ 8016 SBC
..
[    5.808975] usbhid: USB HID core driver
[    5.827592] genirq: irq_chip msmgpio did not update eff. affinity
mask of irq 75
[    5.845725] sysfs: cannot create duplicate filename
'/devices/platform/soc/5c000.qfprom/qfprom0'
[    5.845994] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.10.168-rc1 #1
[    5.853735] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[    5.860077] Call trace:
[    5.866760]  dump_backtrace+0x0/0x1f0
[    5.868952]  show_stack+0x20/0x30
[    5.872766]  dump_stack+0x110/0x160
[    5.876068]  sysfs_warn_dup+0x6c/0x90
[    5.879371]  sysfs_create_dir_ns+0xf0/0x110
[    5.883201]  kobject_add_internal+0xa0/0x324
[    5.887195]  kobject_add+0x94/0x10c
[    5.891693]  device_add+0xfc/0x780
[    5.894902]  nvmem_register+0x6fc/0x930
[    5.898383]  devm_nvmem_register+0x4c/0x94
[    5.902121]  qfprom_probe+0x1e0/0x29c
[    5.906279]  platform_drv_probe+0x5c/0xb4
[    5.910021]  really_probe+0xf8/0x52c
[    5.914004]  driver_probe_device+0xfc/0x170
[    5.917663]  device_driver_attach+0xd0/0xe0
[    5.921567]  __driver_attach+0xd4/0x194
[    5.925729]  bus_for_each_dev+0x78/0xdc
[    5.929546]  driver_attach+0x2c/0x40
[    5.933361]  bus_add_driver+0x154/0x254
[    5.937183]  driver_register+0x80/0x13c
[    5.940745]  __platform_driver_register+0x50/0x5c
[    5.944583]  qfprom_driver_init+0x24/0x30
[    5.949428]  do_one_initcall+0x8c/0x470
[    5.953419]  kernel_init_freeable+0x320/0x38c
[    5.957077]  kernel_init+0x1c/0x128
[    5.961570]  ret_from_fork+0x10/0x30
[    5.965191] kobject_add_internal failed for qfprom0 with -EEXIST,
don't try to register things with the same name in the same directory.
[    5.969110] qcom,qfprom: probe of 5c000.qfprom failed with error -17
[    6.000014] netem: version 1.3
[    6.000346] ipip: IPv4 and MPLS over IPv4 tunneling driver
[    6.005040] gre: GRE over IPv4 demultiplexor driver
[    6.007652] ip_gre: GRE over IPv4 tunneling driver
[    6.018597] IPv4 over IPsec tunneling driver
[    6.024506] NET: Registered protocol family 10
[    6.031635] Segment Routing with IPv6
[    6.036627] ip6_gre: GRE over IPv6 tunneling driver
[    6.039047] NET: Registered protocol family 17
[    6.042070] 8021q: 802.1Q VLAN Support v1.8
[    6.045837] 9pnet: Installing 9P2000 support
[    6.049608] Key type dns_resolver registered
[    6.055585] registered taskstats version 1
[    6.057828] Loading compiled-in X.509 certificates
[    6.393191] debugfs: Directory '4a9000.thermal-sensor' with parent

'tsens' already present!

please refer following link for more details on boot and test logs,
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.10.y/build/v5.10.167-140-g65fa84413c15/testrun/14762346/suite/log-parser-test/test/check-kernel-exception/log
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.10.y/build/v5.10.167-140-g65fa84413c15/testrun/14762346/suite/log-parser-test/test/check-kernel-exception/details/

metadata:
git_ref: linux-5.10.y
git_repo: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
git_sha: 65fa84413c15ee131ad4b76077c48f0603d1d8ec
git_describe: v5.10.167-140-g65fa84413c15
kernel_version: 5.10.168-rc1
kernel-config:
https://storage.tuxsuite.com/public/linaro/lkft/builds/2LglWCZtZStAHvQWoY1YTAIT2ws/config
build-url: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc/-/pipelines/776087062
artifact-location:
https://storage.tuxsuite.com/public/linaro/lkft/builds/2LglWCZtZStAHvQWoY1YTAIT2ws
toolchain: gcc-11

--
Linaro LKFT
https://lkft.linaro.org

Quoted 2 lines

--
Florian

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.

The whole patch series can be found in one patch at:

	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.168-rc1.gz

or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
and the diffstat can be found below.

thanks,

greg k-h

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.

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.

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.

Quoted 5 lines · Greg Kroah-Hartman

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.

Quoted 3 lines

Responses should be made by Wed, 15 Feb 2023 14:46:51 +0000. Anything received after that time might be too late.

We don't know the reason/cause yet, but Chromebooks with arm64 CPU no longer boot with this merge applied to chromeos-5.10. We'll revert the nvmem patches and try again. If that doesn't help we'll need to bisect which will take some time.

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.

Quoted 8 lines · Greg Kroah-Hartman

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.

Seen with several x86_64 boot tests during reboot:

[   13.465146] ------------[ cut here ]------------
[   13.465644] list_del corruption. prev->next should be ffff9836448a5008, but was ffff9836448a2010
ILLOPC: ffffffffae597813: 0f 0b
[   13.466452] WARNING: CPU: 0 PID: 302 at lib/list_debug.c:59 __list_del_entry_valid+0xb3/0xe0
[   13.466710] Modules linked in:
[   13.467103] CPU: 0 PID: 302 Comm: init Not tainted 5.10.168-rc1+ #1
[   13.467281] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
[   13.467545] RIP: 0010:__list_del_entry_valid+0xb3/0xe0
[   13.468234] Code: cc cc cc 4c 89 c2 48 c7 c7 f8 c6 82 af e8 ad c9 8e 00 0f 0b 31 c0 c3 cc cc cc cc 4c 89 c2 48 c7 c7 30 c7 82 af e8 95 c9 8e 00 <0f> 0b 31 c0 c3 cc cc cc cc 4c 89 c6 48 c7 c7 70 c7 82 af e8 7d c9 [   13.468694] RSP: 0018:ffff9f160017bde0 EFLAGS: 00000282
[   13.469076] RAX: 0000000000000000 RBX: ffff9836448a5008 RCX: 0000000000000006
[   13.469297] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffae0e03dd
[   13.469494] RBP: ffff98364482c2f0 R08: 0000000000000001 R09: 0000000000000001
[   13.469699] R10: 0000000000000001 R11: ffffffffafa6f3e0 R12: ffff9836448a5000
[   13.469974] R13: ffff9836448a3910 R14: 00000000fee1dead R15: 0000000000000000
[   13.470122] FS:  00007ff4118d7b28(0000) GS:ffff98365f600000(0000) knlGS:0000000000000000
[   13.470230] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   13.470311] CR2: 00007fd877982830 CR3: 0000000005218000 CR4: 00000000001506f0
[   13.470438] Call Trace:
[   13.470532]  device_shutdown+0xae/0x1c0
[   13.470610]  __do_sys_reboot.cold+0x2f/0x5b
[   13.470675]  ? __lock_acquire+0x5bd/0x2640
[   13.470777]  ? lock_acquire+0xc6/0x2b0
[   13.470934]  ? lockdep_hardirqs_on_prepare+0xdc/0x1a0
[   13.471015]  ? syscall_enter_from_user_mode+0x1d/0x50
[   13.471101]  do_syscall_64+0x33/0x40
[   13.471162]  entry_SYSCALL_64_after_hwframe+0x61/0xc6
[   13.471313] RIP: 0033:0x7ff411860aa6
[   13.471437] Code: ff 5a c3 48 63 ff b8 bb 00 00 00 0f 05 48 89 c7 e9 95 e9 ff ff 48 63 d7 bf ad de e1 fe 50 be 69 19 12 28 b8 a9 00 00 00 0f 05 <48> 89 c7 e8 78 e9 ff ff 5a c3 49 89 ca 50 48 63 d2 4d 63 c0 b8 d8 [   13.471627] RSP: 002b:00007ffd01d415e0 EFLAGS: 00000246 ORIG_RAX: 00000000000000a9
[   13.471741] RAX: ffffffffffffffda RBX: 000000000000000f RCX: 00007ff411860aa6
[   13.471899] RDX: 0000000001234567 RSI: 0000000028121969 RDI: 00000000fee1dead
[   13.472008] RBP: 0000000001234567 R08: 0000000000000000 R09: 0000000000000000
[   13.472099] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
[   13.472185] R13: 00007ffd01d417a8 R14: 00007ff4118d7b28 R15: 0000000000000000
[   13.472384] irq event stamp: 479
[   13.472453] hardirqs last  enabled at (487): [<ffffffffae0e03dd>] console_unlock+0x4dd/0x5e0
[   13.472560] hardirqs last disabled at (494): [<ffffffffae0e0334>] console_unlock+0x434/0x5e0
[   13.472666] softirqs last  enabled at (242): [<ffffffffaf000fe2>] asm_call_irq_on_stack+0x12/0x20
[   13.472775] softirqs last disabled at (237): [<ffffffffaf000fe2>] asm_call_irq_on_stack+0x12/0x20
[   13.472964] ---[ end trace 34290884cd36b277 ]---

Currently bisecting.

Reverting the nvmem patches fixed this problem.

Quoted 2 lines · Guenter Roeck

Reverting the nvmem patches fixed this problem.

But upstream is fine?

Quoted 54 lines · Guenter Roeck

Quoted 8 lines · Greg Kroah-Hartman

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.

Seen with several x86_64 boot tests during reboot:

[   13.465146] ------------[ cut here ]------------
[   13.465644] list_del corruption. prev->next should be ffff9836448a5008, but was ffff9836448a2010
ILLOPC: ffffffffae597813: 0f 0b
[   13.466452] WARNING: CPU: 0 PID: 302 at lib/list_debug.c:59 __list_del_entry_valid+0xb3/0xe0
[   13.466710] Modules linked in:
[   13.467103] CPU: 0 PID: 302 Comm: init Not tainted 5.10.168-rc1+ #1
[   13.467281] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
[   13.467545] RIP: 0010:__list_del_entry_valid+0xb3/0xe0
[   13.468234] Code: cc cc cc 4c 89 c2 48 c7 c7 f8 c6 82 af e8 ad c9 8e 00 0f 0b 31 c0 c3 cc cc cc cc 4c 89 c2 48 c7 c7 30 c7 82 af e8 95 c9 8e 00 <0f> 0b 31 c0 c3 cc cc cc cc 4c 89 c6 48 c7 c7 70 c7 82 af e8 7d c9 [   13.468694] RSP: 0018:ffff9f160017bde0 EFLAGS: 00000282
[   13.469076] RAX: 0000000000000000 RBX: ffff9836448a5008 RCX: 0000000000000006
[   13.469297] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffae0e03dd
[   13.469494] RBP: ffff98364482c2f0 R08: 0000000000000001 R09: 0000000000000001
[   13.469699] R10: 0000000000000001 R11: ffffffffafa6f3e0 R12: ffff9836448a5000
[   13.469974] R13: ffff9836448a3910 R14: 00000000fee1dead R15: 0000000000000000
[   13.470122] FS:  00007ff4118d7b28(0000) GS:ffff98365f600000(0000) knlGS:0000000000000000
[   13.470230] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   13.470311] CR2: 00007fd877982830 CR3: 0000000005218000 CR4: 00000000001506f0
[   13.470438] Call Trace:
[   13.470532]  device_shutdown+0xae/0x1c0
[   13.470610]  __do_sys_reboot.cold+0x2f/0x5b
[   13.470675]  ? __lock_acquire+0x5bd/0x2640
[   13.470777]  ? lock_acquire+0xc6/0x2b0
[   13.470934]  ? lockdep_hardirqs_on_prepare+0xdc/0x1a0
[   13.471015]  ? syscall_enter_from_user_mode+0x1d/0x50
[   13.471101]  do_syscall_64+0x33/0x40
[   13.471162]  entry_SYSCALL_64_after_hwframe+0x61/0xc6
[   13.471313] RIP: 0033:0x7ff411860aa6
[   13.471437] Code: ff 5a c3 48 63 ff b8 bb 00 00 00 0f 05 48 89 c7 e9 95 e9 ff ff 48 63 d7 bf ad de e1 fe 50 be 69 19 12 28 b8 a9 00 00 00 0f 05 <48> 89 c7 e8 78 e9 ff ff 5a c3 49 89 ca 50 48 63 d2 4d 63 c0 b8 d8 [   13.471627] RSP: 002b:00007ffd01d415e0 EFLAGS: 00000246 ORIG_RAX: 00000000000000a9
[   13.471741] RAX: ffffffffffffffda RBX: 000000000000000f RCX: 00007ff411860aa6
[   13.471899] RDX: 0000000001234567 RSI: 0000000028121969 RDI: 00000000fee1dead
[   13.472008] RBP: 0000000001234567 R08: 0000000000000000 R09: 0000000000000000
[   13.472099] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
[   13.472185] R13: 00007ffd01d417a8 R14: 00007ff4118d7b28 R15: 0000000000000000
[   13.472384] irq event stamp: 479
[   13.472453] hardirqs last  enabled at (487): [<ffffffffae0e03dd>] console_unlock+0x4dd/0x5e0
[   13.472560] hardirqs last disabled at (494): [<ffffffffae0e0334>] console_unlock+0x434/0x5e0
[   13.472666] softirqs last  enabled at (242): [<ffffffffaf000fe2>] asm_call_irq_on_stack+0x12/0x20
[   13.472775] softirqs last disabled at (237): [<ffffffffaf000fe2>] asm_call_irq_on_stack+0x12/0x20
[   13.472964] ---[ end trace 34290884cd36b277 ]---

Quoted 2 lines

Currently bisecting.

Reverting the nvmem patches fixed this problem.

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.

The whole patch series can be found in one patch at:

	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.168-rc1.gz

or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
and the diffstat can be found below.

Hi Greg,

Quoted 5 lines · Greg Kroah-Hartman

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.

Quoted 8 lines

Responses should be made by Wed, 15 Feb 2023 14:46:51 +0000. Anything received after that time might be too late.

The whole patch series can be found in one patch at:

	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.168-rc1.gz

or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
and the diffstat can be found below.

Not pinpointed the exact cause, but booting 5.10.168-rc1 here on a x86_64 system:

[    0.853375] rtc_cmos 00:03: RTC can wake from S4
[    0.854150] rtc_cmos 00:03: registered as rtc0
[    0.854694] rtc_cmos 00:03: setting system clock to 2023-02-14T19:44:16 UTC (1676403856)
[    0.855555] list_add double add: new=ffff90df87f15810, prev=ffff90df87f15810, next=ffff90df80145420.
[    0.856513] ------------[ cut here ]------------
[    0.857023] kernel BUG at lib/list_debug.c:33!
[    0.857519] invalid opcode: 0000 [#1] SMP NOPTI
[    0.858024] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.168-rc1+ #1
[    0.858713] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
[    0.859562] RIP: 0010:__list_add_valid.cold+0x23/0x5b
[    0.860112] Code: 01 00 e9 5c c9 bb ff 48 c7 c7 e8 35 52 ac e8 94 10 ff ff 0f 0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 e8 36 52 ac e8 7d 10 ff ff <0f> 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 90 36 52 ac e8 66 10 ff
[    0.860502] RSP: 0018:ffffa8db40013a78 EFLAGS: 00010246
[    0.860502] RAX: 0000000000000058 RBX: ffff90dfefaf4c00 RCX: ffffffffac8b3648
[    0.860502] RDX: 0000000000000000 RSI: 00000000ffffefff RDI: 0000000000000246
[    0.860502] RBP: ffff90df87f15808 R08: 0000000000000000 R09: ffffa8db400138a0
[    0.860502] R10: ffffa8db40013898 R11: ffffffffac8cb688 R12: ffff90df80145420
[    0.860502] R13: ffff90df87f15810 R14: ffff90df87f15810 R15: 0000000000000000
[    0.860502] FS:  0000000000000000(0000) GS:ffff90dffbc00000(0000) knlGS:0000000000000000
[    0.860502] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    0.860502] CR2: 0000000000000000 CR3: 000000016ee0a000 CR4: 0000000000350ef0
[    0.860502] Call Trace:
[    0.860502]  kobject_add_internal+0x7e/0x2d0
[    0.860502]  ? rpm_idle+0x1d/0x310
[    0.860502]  kobject_add+0x7e/0xb0
[    0.860502]  ? _cond_resched+0x16/0x50
[    0.860502]  device_add+0x118/0x840
[    0.860502]  nvmem_register+0x547/0x720
[    0.860502]  ? nvmem_unregister+0x40/0x40
[    0.860502]  devm_nvmem_register+0x3b/0x80
[    0.860502]  rtc_nvmem_register+0x33/0xe0
[    0.860502]  cmos_do_probe+0x3cc/0x5d0
[    0.860502]  ? cmos_validate_alarm+0x1c0/0x1c0
[    0.860502]  ? rtc_handler+0xd0/0xd0
[    0.860502]  ? cmos_do_probe+0x5d0/0x5d0
[    0.860502]  pnp_device_probe+0xb3/0x150
[    0.860502]  really_probe+0x222/0x480
[    0.860502]  driver_probe_device+0xe5/0x150
[    0.860502]  device_driver_attach+0xa9/0xb0
[    0.860502]  __driver_attach+0xa7/0x150
[    0.860502]  ? device_driver_attach+0xb0/0xb0
[    0.860502]  bus_for_each_dev+0x78/0xc0
[    0.860502]  bus_add_driver+0x13a/0x200
[    0.860502]  driver_register+0x8b/0xe0
[    0.860502]  ? rtc_dev_init+0x34/0x34
[    0.860502]  cmos_init+0x13/0x74
[    0.860502]  do_one_initcall+0x44/0x1d0
[    0.860502]  kernel_init_freeable+0x21e/0x280
[    0.860502]  ? rest_init+0xb4/0xb4
[    0.860502]  kernel_init+0xa/0x10c
[    0.860502]  ret_from_fork+0x22/0x30
[    0.860502] Modules linked in:
[    0.881782] ---[ end trace 15ab58632cc3d5c4 ]---
[    0.882291] RIP: 0010:__list_add_valid.cold+0x23/0x5b
[    0.882839] Code: 01 00 e9 5c c9 bb ff 48 c7 c7 e8 35 52 ac e8 94 10 ff ff 0f 0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 e8 36 52 ac e8 7d 10 ff ff <0f> 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 90 36 52 ac e8 66 10 ff
[    0.884708] RSP: 0018:ffffa8db40013a78 EFLAGS: 00010246
[    0.885274] RAX: 0000000000000058 RBX: ffff90dfefaf4c00 RCX: ffffffffac8b3648
[    0.886021] RDX: 0000000000000000 RSI: 00000000ffffefff RDI: 0000000000000246
[    0.886767] RBP: ffff90df87f15808 R08: 0000000000000000 R09: ffffa8db400138a0

[    0.887518] R10: ffffa8db40013898 R11: ffffffffac8cb688 R12: ffff90df80145420
[    0.888266] R13: ffff90df87f15810 R14: ffff90df87f15810 R15: 0000000000000000
[    0.889454] FS:  0000000000000000(0000) GS:ffff90dffbc00000(0000) knlGS:0000000000000000
[    0.890295] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    0.890916] CR2: 0000000000000000 CR3: 000000016ee0a000 CR4: 0000000000350ef0
[    0.891670] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[    0.892493] Kernel Offset: 0x2a400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[    0.893451] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---

Quoted 78 lines · Salvatore Bonaccorso

Hi Greg,

Quoted 5 lines · Greg Kroah-Hartman

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.

Quoted 8 lines

Responses should be made by Wed, 15 Feb 2023 14:46:51 +0000. Anything received after that time might be too late.

The whole patch series can be found in one patch at:

	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.168-rc1.gz

or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
and the diffstat can be found below.

Not pinpointed the exact cause, but booting 5.10.168-rc1 here on a x86_64 system:

[    0.853375] rtc_cmos 00:03: RTC can wake from S4
[    0.854150] rtc_cmos 00:03: registered as rtc0
[    0.854694] rtc_cmos 00:03: setting system clock to 2023-02-14T19:44:16 UTC (1676403856)
[    0.855555] list_add double add: new=ffff90df87f15810, prev=ffff90df87f15810, next=ffff90df80145420.
[    0.856513] ------------[ cut here ]------------
[    0.857023] kernel BUG at lib/list_debug.c:33!
[    0.857519] invalid opcode: 0000 [#1] SMP NOPTI
[    0.858024] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.168-rc1+ #1
[    0.858713] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
[    0.859562] RIP: 0010:__list_add_valid.cold+0x23/0x5b
[    0.860112] Code: 01 00 e9 5c c9 bb ff 48 c7 c7 e8 35 52 ac e8 94 10 ff ff 0f 0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 e8 36 52 ac e8 7d 10 ff ff <0f> 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 90 36 52 ac e8 66 10 ff
[    0.860502] RSP: 0018:ffffa8db40013a78 EFLAGS: 00010246
[    0.860502] RAX: 0000000000000058 RBX: ffff90dfefaf4c00 RCX: ffffffffac8b3648
[    0.860502] RDX: 0000000000000000 RSI: 00000000ffffefff RDI: 0000000000000246
[    0.860502] RBP: ffff90df87f15808 R08: 0000000000000000 R09: ffffa8db400138a0
[    0.860502] R10: ffffa8db40013898 R11: ffffffffac8cb688 R12: ffff90df80145420
[    0.860502] R13: ffff90df87f15810 R14: ffff90df87f15810 R15: 0000000000000000
[    0.860502] FS:  0000000000000000(0000) GS:ffff90dffbc00000(0000) knlGS:0000000000000000
[    0.860502] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    0.860502] CR2: 0000000000000000 CR3: 000000016ee0a000 CR4: 0000000000350ef0
[    0.860502] Call Trace:
[    0.860502]  kobject_add_internal+0x7e/0x2d0
[    0.860502]  ? rpm_idle+0x1d/0x310
[    0.860502]  kobject_add+0x7e/0xb0
[    0.860502]  ? _cond_resched+0x16/0x50
[    0.860502]  device_add+0x118/0x840
[    0.860502]  nvmem_register+0x547/0x720
[    0.860502]  ? nvmem_unregister+0x40/0x40
[    0.860502]  devm_nvmem_register+0x3b/0x80
[    0.860502]  rtc_nvmem_register+0x33/0xe0
[    0.860502]  cmos_do_probe+0x3cc/0x5d0
[    0.860502]  ? cmos_validate_alarm+0x1c0/0x1c0
[    0.860502]  ? rtc_handler+0xd0/0xd0
[    0.860502]  ? cmos_do_probe+0x5d0/0x5d0
[    0.860502]  pnp_device_probe+0xb3/0x150
[    0.860502]  really_probe+0x222/0x480
[    0.860502]  driver_probe_device+0xe5/0x150
[    0.860502]  device_driver_attach+0xa9/0xb0
[    0.860502]  __driver_attach+0xa7/0x150
[    0.860502]  ? device_driver_attach+0xb0/0xb0
[    0.860502]  bus_for_each_dev+0x78/0xc0
[    0.860502]  bus_add_driver+0x13a/0x200
[    0.860502]  driver_register+0x8b/0xe0
[    0.860502]  ? rtc_dev_init+0x34/0x34
[    0.860502]  cmos_init+0x13/0x74
[    0.860502]  do_one_initcall+0x44/0x1d0
[    0.860502]  kernel_init_freeable+0x21e/0x280
[    0.860502]  ? rest_init+0xb4/0xb4
[    0.860502]  kernel_init+0xa/0x10c
[    0.860502]  ret_from_fork+0x22/0x30
[    0.860502] Modules linked in:
[    0.881782] ---[ end trace 15ab58632cc3d5c4 ]---
[    0.882291] RIP: 0010:__list_add_valid.cold+0x23/0x5b
[    0.882839] Code: 01 00 e9 5c c9 bb ff 48 c7 c7 e8 35 52 ac e8 94 10 ff ff 0f 0b 48 89 f2 4c 89 c1 48 89 fe 48 c7 c7 e8 36 52 ac e8 7d 10 ff ff <0f> 0b 48 89 d1 4c 89 c6 4c 89 ca 48 c7 c7 90 36 52 ac e8 66 10 ff
[    0.884708] RSP: 0018:ffffa8db40013a78 EFLAGS: 00010246
[    0.885274] RAX: 0000000000000058 RBX: ffff90dfefaf4c00 RCX: ffffffffac8b3648
[    0.886021] RDX: 0000000000000000 RSI: 00000000ffffefff RDI: 0000000000000246
[    0.886767] RBP: ffff90df87f15808 R08: 0000000000000000 R09: ffffa8db400138a0

Quoted 9 lines

[    0.887518] R10: ffffa8db40013898 R11: ffffffffac8cb688 R12: ffff90df80145420
[    0.888266] R13: ffff90df87f15810 R14: ffff90df87f15810 R15: 0000000000000000
[    0.889454] FS:  0000000000000000(0000) GS:ffff90dffbc00000(0000) knlGS:0000000000000000
[    0.890295] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    0.890916] CR2: 0000000000000000 CR3: 000000016ee0a000 CR4: 0000000000350ef0
[    0.891670] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[    0.892493] Kernel Offset: 0x2a400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[    0.893451] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---

This is caused by the bad nvmem patch in -rc1. -rc2 has the fix.

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.

The whole patch series can be found in one patch at:

	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.168-rc1.gz

or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y
and the diffstat can be found below.

thanks,

greg k-h

-------------