From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
Date: Tue, 14 Feb 2023 11:05:20 +0000 [thread overview]
Message-ID: <Y+tq8HvE2TjffLk9@debian> (raw)
In-Reply-To: <20230213144745.696901179@linuxfoundation.org>
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@codethink.co.uk>
--
Regards
Sudip
next prev parent reply other threads:[~2023-02-14 11:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 14:49 [PATCH 5.10 000/139] 5.10.168-rc1 review Greg Kroah-Hartman
2023-02-13 17:26 ` Pavel Machek
2023-02-13 19:50 ` Florian Fainelli
2023-02-14 6:20 ` Greg Kroah-Hartman
2023-02-14 13:20 ` Russell King (Oracle)
2023-02-14 14:53 ` Russell King (Oracle)
2023-02-14 15:09 ` Sasha Levin
2023-02-14 15:25 ` Russell King (Oracle)
2023-02-14 15:33 ` Sasha Levin
2023-02-14 15:39 ` Russell King (Oracle)
2023-02-14 9:16 ` Naresh Kamboju
2023-02-14 13:21 ` Naresh Kamboju
2023-02-13 23:33 ` Shuah Khan
2023-02-14 6:51 ` Guenter Roeck
2023-02-14 11:05 ` Sudip Mukherjee (Codethink) [this message]
2023-02-14 17:04 ` Guenter Roeck
2023-02-14 17:59 ` Guenter Roeck
2023-02-14 17:15 ` Guenter Roeck
2023-02-14 17:51 ` Guenter Roeck
2023-02-14 17:54 ` Linus Torvalds
2023-02-14 18:09 ` Guenter Roeck
2023-02-14 18:05 ` Greg Kroah-Hartman
2023-02-14 19:45 ` Salvatore Bonaccorso
2023-02-14 19:57 ` Guenter Roeck
2023-02-14 20:30 ` Salvatore Bonaccorso
2023-02-15 7:30 ` zhouzhixiu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+tq8HvE2TjffLk9@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox