* [PATCH 5.10 000/139] 5.10.168-rc1 review
@ 2023-02-13 14:49 Greg Kroah-Hartman
2023-02-13 17:26 ` Pavel Machek
` (8 more replies)
0 siblings, 9 replies; 26+ messages in thread
From: Greg Kroah-Hartman @ 2023-02-13 14:49 UTC (permalink / raw)
To: stable
Cc: Greg Kroah-Hartman, patches, linux-kernel, torvalds, akpm, linux,
shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow
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
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Linux 5.10.168-rc1
Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
nvmem: core: fix return value
David Chen <david.chen@nutanix.com>
Fix page corruption caused by racy check in __free_pages
Heiner Kallweit <hkallweit1@gmail.com>
arm64: dts: meson-axg: Make mmc host controller interrupts level-sensitive
Heiner Kallweit <hkallweit1@gmail.com>
arm64: dts: meson-g12-common: Make mmc host controller interrupts level-sensitive
Heiner Kallweit <hkallweit1@gmail.com>
arm64: dts: meson-gx: Make mmc host controller interrupts level-sensitive
Guo Ren <guoren@linux.alibaba.com>
riscv: Fixup race condition on PG_dcache_clean in flush_icache_pte
Xiubo Li <xiubli@redhat.com>
ceph: flush cap releases when the session is flushed
Prashant Malani <pmalani@chromium.org>
usb: typec: altmodes/displayport: Fix probe pin assign check
Mark Pearson <mpearson-lenovo@squebb.ca>
usb: core: add quirk for Alcor Link AK9563 smartcard reader
Anand Jain <anand.jain@oracle.com>
btrfs: free device in btrfs_close_devices for a single device filesystem
Alan Stern <stern@rowland.harvard.edu>
net: USB: Fix wrong-direction WARNING in plusb.c
ZhaoLong Wang <wangzhaolong1@huawei.com>
cifs: Fix use-after-free in rdata->read_into_pages()
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
pinctrl: intel: Restore the pins that used to be in Direct IRQ mode
Serge Semin <Sergey.Semin@baikalelectronics.ru>
spi: dw: Fix wrong FIFO level setting for long xfers
Maxim Korotkov <korotkov.maxim.s@gmail.com>
pinctrl: single: fix potential NULL dereference
Joel Stanley <joel@jms.id.au>
pinctrl: aspeed: Fix confusing types in return value
Dan Carpenter <error27@gmail.com>
ALSA: pci: lx6464es: fix a debug loop
Hangbin Liu <liuhangbin@gmail.com>
selftests: forwarding: lib: quote the sysctl values
Pietro Borrello <borrello@diag.uniroma1.it>
rds: rds_rm_zerocopy_callback() use list_first_entry()
Shay Drory <shayd@nvidia.com>
net/mlx5: fw_tracer, Zero consumer index when reloading the tracer
Shay Drory <shayd@nvidia.com>
net/mlx5: fw_tracer, Clear load bit when freeing string DBs buffers
Dragos Tatulea <dtatulea@nvidia.com>
net/mlx5e: IPoIB, Show unknown speed instead of error
Vladimir Oltean <vladimir.oltean@nxp.com>
net: mscc: ocelot: fix VCAP filters not matching on MAC with "protocol 802.1Q"
Anirudh Venkataramanan <anirudh.venkataramanan@intel.com>
ice: Do not use WQ_MEM_RECLAIM flag for workqueue
Herton R. Krzesinski <herton@redhat.com>
uapi: add missing ip/ipv6 header dependencies for linux/stddef.h
Neel Patel <neel.patel@amd.com>
ionic: clean interrupt before enabling queue to avoid credit race
Heiner Kallweit <hkallweit1@gmail.com>
net: phy: meson-gxl: use MMD access dummy stubs for GXL, internal PHY
Qi Zheng <zhengqi.arch@bytedance.com>
bonding: fix error checking in bond_debug_reregister()
Christian Hopps <chopps@chopps.org>
xfrm: fix bug with DSCP copy to v6 from v4 tunnel
Yang Yingliang <yangyingliang@huawei.com>
RDMA/usnic: use iommu_map_atomic() under spin_lock()
Dragos Tatulea <dtatulea@nvidia.com>
IB/IPoIB: Fix legacy IPoIB due to wrong number of queues
Eric Dumazet <edumazet@google.com>
xfrm/compat: prevent potential spectre v1 gadget in xfrm_xlate32_attr()
Dean Luick <dean.luick@cornelisnetworks.com>
IB/hfi1: Restore allocated resources on failed copyout
Anastasia Belova <abelova@astralinux.ru>
xfrm: compat: change expression for switch in xfrm_xlate64
Devid Antonio Filoni <devid.filoni@egluetechnologies.com>
can: j1939: do not wait 250 ms if the same addr was already claimed
Mark Brown <broonie@kernel.org>
of/address: Return an error when no valid dma-ranges are found
Shiju Jose <shiju.jose@huawei.com>
tracing: Fix poll() and select() do not work on per_cpu trace_pipe and trace_pipe_raw
Guillaume Pinot <texitoi@texitoi.eu>
ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book2 Pro 360
Artemii Karasev <karasev@ispras.ru>
ALSA: emux: Avoid potential array out-of-bound in snd_emux_xg_control()
Edson Juliano Drosdeck <edson.drosdeck@gmail.com>
ALSA: hda/realtek: Add Positivo N14KP6-TG
Alexander Potapenko <glider@google.com>
btrfs: zlib: zero-initialize zlib workspace
Josef Bacik <josef@toxicpanda.com>
btrfs: limit device extents to the device size
Mike Kravetz <mike.kravetz@oracle.com>
migrate: hugetlb: check for hugetlb shared PMD in node migration
Miaohe Lin <linmiaohe@huawei.com>
mm/migration: return errno when isolate_huge_page failed
Andreas Kemnade <andreas@kemnade.info>
iio:adc:twl6030: Enable measurement of VAC
Martin KaFai Lau <kafai@fb.com>
bpf: Do not reject when the stack read size is different from the tracked scalar size
Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
nvmem: core: fix registration vs use race
Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
nvmem: core: fix cleanup after dev_set_name()
Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
nvmem: core: remove nvmem_config wp_gpio
Gaosheng Cui <cuigaosheng1@huawei.com>
nvmem: core: add error handling for dev_set_name
Christophe Kerello <christophe.kerello@foss.st.com>
nvmem: core: Fix a conflict between MTD and NVMEM on wp-gpios property
Minsuk Kang <linuxlovemin@yonsei.ac.kr>
wifi: brcmfmac: Check the count value of channel spec to prevent out-of-bounds reads
Chao Yu <chao@kernel.org>
f2fs: fix to do sanity check on i_extra_isize in is_alive()
Dongliang Mu <dzm91@hust.edu.cn>
fbdev: smscufx: fix error handling code in ufx_usb_probe
Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
serial: 8250_dma: Fix DMA Rx rearm race
Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
serial: 8250_dma: Fix DMA Rx completion race
Michael Walle <michael@walle.cc>
nvmem: core: fix cell removal on error
Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
nvmem: core: initialise nvmem->id early
Rob Clark <robdclark@chromium.org>
drm/i915: Fix potential bit_17 double-free
Phillip Lougher <phillip@squashfs.org.uk>
Squashfs: fix handling and sanity checking of xattr_ids count
Longlong Xia <xialonglong1@huawei.com>
mm/swapfile: add cond_resched() in get_swap_pages()
Zheng Yongjun <zhengyongjun3@huawei.com>
fpga: stratix10-soc: Fix return value check in s10_ops_write_init()
Joerg Roedel <jroedel@suse.de>
x86/debug: Fix stack recursion caused by wrongly ordered DR7 accesses
Mike Kravetz <mike.kravetz@oracle.com>
mm: hugetlb: proc: check for hugetlb shared PMD in /proc/PID/smaps
Andreas Schwab <schwab@suse.de>
riscv: disable generation of unwind tables
Helge Deller <deller@gmx.de>
parisc: Wire up PTRACE_GETREGS/PTRACE_SETREGS for compat case
Helge Deller <deller@gmx.de>
parisc: Fix return code of pdc_iodc_print()
Johan Hovold <johan+linaro@kernel.org>
nvmem: qcom-spmi-sdam: fix module autoloading
Carlos Song <carlos.song@nxp.com>
iio: imu: fxos8700: fix MAGN sensor scale and unit
Carlos Song <carlos.song@nxp.com>
iio: imu: fxos8700: remove definition FXOS8700_CTRL_ODR_MIN
Carlos Song <carlos.song@nxp.com>
iio: imu: fxos8700: fix failed initialization ODR mode assignment
Carlos Song <carlos.song@nxp.com>
iio: imu: fxos8700: fix incorrect ODR mode readback
Carlos Song <carlos.song@nxp.com>
iio: imu: fxos8700: fix swapped ACCEL and MAGN channels readback
Carlos Song <carlos.song@nxp.com>
iio: imu: fxos8700: fix map label of channel type to MAGN sensor
Carlos Song <carlos.song@nxp.com>
iio: imu: fxos8700: fix IMU data bits returned to user space
Carlos Song <carlos.song@nxp.com>
iio: imu: fxos8700: fix incomplete ACCEL and MAGN channels readback
Carlos Song <carlos.song@nxp.com>
iio: imu: fxos8700: fix ACCEL measurement range selection
Andreas Kemnade <andreas@kemnade.info>
iio:adc:twl6030: Enable measurements of VUSB, VBAT and others
Xiongfeng Wang <wangxiongfeng2@huawei.com>
iio: adc: berlin2-adc: Add missing of_node_put() in error path
Dmitry Perchanov <dmitry.perchanov@intel.com>
iio: hid: fix the retval in accel_3d_capture_sample
Ard Biesheuvel <ardb@kernel.org>
efi: Accept version 2 of memory attributes table
Victor Shyba <victor1984@riseup.net>
ALSA: hda/realtek: Add Acer Predator PH315-54
Alexander Egorenkov <egorenar@linux.ibm.com>
watchdog: diag288_wdt: fix __diag288() inline assembly
Alexander Egorenkov <egorenar@linux.ibm.com>
watchdog: diag288_wdt: do not use stack buffers for hardware data
Natalia Petrova <n.petrova@fintech.ru>
net: qrtr: free memory on error path in radix_tree_insert()
Samuel Thibault <samuel.thibault@ens-lyon.org>
fbcon: Check font dimension limits
Werner Sembach <wse@tuxedocomputers.com>
Input: i8042 - add Clevo PCX0DX to i8042 quirk table
Werner Sembach <wse@tuxedocomputers.com>
Input: i8042 - add TUXEDO devices to i8042 quirk tables
Werner Sembach <wse@tuxedocomputers.com>
Input: i8042 - merge quirk tables
Werner Sembach <wse@tuxedocomputers.com>
Input: i8042 - move __initconst to fix code styling warning
George Kennedy <george.kennedy@oracle.com>
vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF
Udipto Goswami <quic_ugoswami@quicinc.com>
usb: gadget: f_fs: Fix unbalanced spinlock in __ffs_ep0_queue_wait
Neil Armstrong <neil.armstrong@linaro.org>
usb: dwc3: qcom: enable vbus override when in OTG dr-mode
Wesley Cheng <wcheng@codeaurora.org>
usb: dwc3: dwc3-qcom: Fix typo in the dwc3 vbus override API
Olivier Moysan <olivier.moysan@foss.st.com>
iio: adc: stm32-dfsdm: fill module aliases
Hyunwoo Kim <v4bel@theori.io>
net/x25: Fix to not accept on connected socket
Koba Ko <koba.ko@canonical.com>
platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table
Randy Dunlap <rdunlap@infradead.org>
i2c: rk3x: fix a bunch of kernel-doc warnings
Mike Christie <michael.christie@oracle.com>
scsi: iscsi_tcp: Fix UAF during login when accessing the shost ipaddress
Maurizio Lombardi <mlombard@redhat.com>
scsi: target: core: Fix warning on RT kernels
Stefan Wahren <stefan.wahren@i2se.com>
i2c: mxs: suppress probe-deferral error message
Magnus Karlsson <magnus.karlsson@intel.com>
qede: execute xdp_do_flush() before napi_complete_done()
Bhaskar Upadhaya <bupadhaya@marvell.com>
qede: add netpoll support for qede driver
Anton Gusev <aagusev@ispras.ru>
efi: fix potential NULL deref in efi_mem_reserve_persistent
Fedor Pchelkin <pchelkin@ispras.ru>
net: openvswitch: fix flow memory leak in ovs_flow_cmd_new
Parav Pandit <parav@nvidia.com>
virtio-net: Keep stop() to follow mirror sequence of open()
Andrei Gherzan <andrei.gherzan@canonical.com>
selftests: net: udpgso_bench_tx: Cater for pending datagrams zerocopy benchmarking
Andrei Gherzan <andrei.gherzan@canonical.com>
selftests: net: udpgso_bench: Fix racing bug between the rx/tx programs
Andrei Gherzan <andrei.gherzan@canonical.com>
selftests: net: udpgso_bench_rx/tx: Stop when wrong CLI args are provided
Andrei Gherzan <andrei.gherzan@canonical.com>
selftests: net: udpgso_bench_rx: Fix 'used uninitialized' compiler warning
Damien Le Moal <damien.lemoal@opensource.wdc.com>
ata: libata: Fix sata_down_spd_limit() when no link speed is reported
Ziyang Xuan <william.xuanziyang@huawei.com>
can: j1939: fix errant WARN_ON_ONCE in j1939_session_deactivate
Tom Rix <trix@redhat.com>
igc: return an error if the mac type is unknown in igc_ptp_systim_to_hwtstamp()
Chris Healy <healych@amazon.com>
net: phy: meson-gxl: Add generic dummy stubs for MMD register access
Fedor Pchelkin <pchelkin@ispras.ru>
squashfs: harden sanity check in squashfs_read_xattr_id_table
Florian Westphal <fw@strlen.de>
netfilter: br_netfilter: disable sabotage_in hook after first suppression
Hyunwoo Kim <v4bel@theori.io>
netrom: Fix use-after-free caused by accept on already connected socket
Andre Kalb <andre.kalb@sma.de>
net: phy: dp83822: Fix null pointer access on DP83825/DP83826 devices
Íñigo Huguet <ihuguet@redhat.com>
sfc: correctly advertise tunneled IPv6 segmentation
Magnus Karlsson <magnus.karlsson@intel.com>
virtio-net: execute xdp_do_flush() before napi_complete_done()
Al Viro <viro@zeniv.linux.org.uk>
fix "direction" argument of iov_iter_kvec()
Al Viro <viro@zeniv.linux.org.uk>
fix iov_iter_bvec() "direction" argument
Al Viro <viro@zeniv.linux.org.uk>
READ is "data destination", not source...
Al Viro <viro@zeniv.linux.org.uk>
WRITE is "data source", not destination...
Eric Auger <eric.auger@redhat.com>
vhost/net: Clear the pending messages when the backend is removed
Martin K. Petersen <martin.petersen@oracle.com>
scsi: Revert "scsi: core: map PQ=1, PDT=other values to SCSI_SCAN_TARGET_PRESENT"
Hans Verkuil <hverkuil-cisco@xs4all.nl>
drm/vc4: hdmi: make CEC adapter name unique
Pierluigi Passaro <pierluigi.p@variscite.com>
arm64: dts: imx8mm: Fix pad control for UART1_DTE_RX
Jakub Sitnicki <jakub@cloudflare.com>
bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener
Eduard Zingerman <eddyz87@gmail.com>
bpf: Fix to preserve reg parent/live fields when copying range info
Martin KaFai Lau <kafai@fb.com>
bpf: Support <8-byte scalar spill and refill
Christophe Leroy <christophe.leroy@csgroup.eu>
powerpc/bpf: Move common helpers into bpf_jit.h
Christophe Leroy <christophe.leroy@csgroup.eu>
powerpc/bpf: Change register numbering for bpf_set/is_seen_register()
Artemii Karasev <karasev@ispras.ru>
ALSA: hda/via: Avoid potential array out-of-bound in add_secret_dac_path()
Yonghong Song <yhs@fb.com>
bpf: Fix a possible task gone issue with bpf_send_signal[_thread]() helpers
Michael Ellerman <mpe@ellerman.id.au>
powerpc/imc-pmu: Revert nest_init_lock to being a mutex
Paul Chaignon <paul@isovalent.com>
bpf: Fix incorrect state pruning for <8B spill/fill
Yuan Can <yuancan@huawei.com>
bus: sunxi-rsb: Fix error handling in sunxi_rsb_init()
Takashi Sakamoto <o-takashi@sakamocchi.jp>
firewire: fix memory leak for payload of request subaction to IEC 61883-1 FCP region
-------------
Diffstat:
Makefile | 4 +-
arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 4 +-
arch/arm64/boot/dts/amlogic/meson-g12-common.dtsi | 6 +-
arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 6 +-
arch/arm64/boot/dts/freescale/imx8mm-pinfunc.h | 2 +-
arch/parisc/kernel/firmware.c | 5 +-
arch/parisc/kernel/ptrace.c | 15 +-
arch/powerpc/net/bpf_jit.h | 35 +
arch/powerpc/net/bpf_jit64.h | 19 -
arch/powerpc/net/bpf_jit_comp64.c | 28 +-
arch/powerpc/perf/imc-pmu.c | 14 +-
arch/riscv/Makefile | 3 +
arch/riscv/mm/cacheflush.c | 4 +-
arch/x86/include/asm/debugreg.h | 26 +-
drivers/ata/libata-core.c | 2 +-
drivers/bus/sunxi-rsb.c | 8 +-
drivers/firewire/core-cdev.c | 4 +-
drivers/firmware/efi/efi.c | 2 +
drivers/firmware/efi/memattr.c | 2 +-
drivers/fpga/stratix10-soc.c | 4 +-
drivers/fsi/fsi-sbefifo.c | 6 +-
drivers/gpu/drm/i915/gem/i915_gem_tiling.c | 9 +-
drivers/gpu/drm/vc4/vc4_hdmi.c | 3 +-
drivers/i2c/busses/i2c-mxs.c | 4 +-
drivers/i2c/busses/i2c-rk3x.c | 44 +-
drivers/iio/accel/hid-sensor-accel-3d.c | 1 +
drivers/iio/adc/berlin2-adc.c | 4 +-
drivers/iio/adc/stm32-dfsdm-adc.c | 1 +
drivers/iio/adc/twl6030-gpadc.c | 32 +
drivers/iio/imu/fxos8700_core.c | 111 +-
drivers/infiniband/hw/hfi1/file_ops.c | 7 +-
drivers/infiniband/hw/usnic/usnic_uiom.c | 8 +-
drivers/infiniband/ulp/ipoib/ipoib_main.c | 8 +
drivers/infiniband/ulp/rtrs/rtrs-clt.c | 2 +-
drivers/input/serio/i8042-x86ia64io.h | 1188 ++++++++++++--------
drivers/net/bonding/bond_debugfs.c | 2 +-
drivers/net/ethernet/intel/ice/ice_main.c | 2 +-
drivers/net/ethernet/intel/igc/igc_ptp.c | 14 +-
.../ethernet/mellanox/mlx5/core/diag/fw_tracer.c | 3 +-
.../ethernet/mellanox/mlx5/core/ipoib/ethtool.c | 13 +-
drivers/net/ethernet/mscc/ocelot_flower.c | 24 +-
drivers/net/ethernet/pensando/ionic/ionic_lif.c | 15 +-
drivers/net/ethernet/qlogic/qede/qede_fp.c | 10 +-
drivers/net/ethernet/sfc/efx.c | 5 +-
drivers/net/phy/dp83822.c | 6 +-
drivers/net/phy/meson-gxl.c | 4 +
drivers/net/usb/plusb.c | 4 +-
drivers/net/virtio_net.c | 8 +-
.../broadcom/brcm80211/brcmfmac/cfg80211.c | 17 +
drivers/nvmem/core.c | 45 +-
drivers/nvmem/qcom-spmi-sdam.c | 1 +
drivers/of/address.c | 21 +-
drivers/pinctrl/aspeed/pinctrl-aspeed.c | 2 +-
drivers/pinctrl/intel/pinctrl-intel.c | 16 +-
drivers/pinctrl/pinctrl-single.c | 2 +
drivers/platform/x86/dell-wmi.c | 3 +
drivers/scsi/iscsi_tcp.c | 9 +-
drivers/scsi/scsi_scan.c | 7 +-
drivers/spi/spi-dw-core.c | 2 +-
drivers/target/target_core_file.c | 4 +-
drivers/target/target_core_tmr.c | 4 +-
drivers/tty/serial/8250/8250_dma.c | 26 +-
drivers/tty/vt/vc_screen.c | 9 +-
drivers/usb/core/quirks.c | 3 +
drivers/usb/dwc3/dwc3-qcom.c | 10 +-
drivers/usb/gadget/function/f_fs.c | 4 +-
drivers/usb/typec/altmodes/displayport.c | 8 +-
drivers/vhost/net.c | 3 +
drivers/vhost/vhost.c | 3 +-
drivers/vhost/vhost.h | 1 +
drivers/video/fbdev/core/fbcon.c | 7 +-
drivers/video/fbdev/smscufx.c | 46 +-
drivers/watchdog/diag288_wdt.c | 15 +-
drivers/xen/pvcalls-back.c | 8 +-
fs/btrfs/volumes.c | 22 +-
fs/btrfs/zlib.c | 2 +-
fs/ceph/mds_client.c | 6 +
fs/cifs/file.c | 4 +-
fs/f2fs/gc.c | 18 +-
fs/proc/task_mmu.c | 4 +-
fs/squashfs/squashfs_fs.h | 2 +-
fs/squashfs/squashfs_fs_sb.h | 2 +-
fs/squashfs/xattr.h | 4 +-
fs/squashfs/xattr_id.c | 4 +-
include/linux/hugetlb.h | 19 +-
include/linux/nvmem-provider.h | 4 +-
include/linux/util_macros.h | 12 +
include/uapi/linux/ip.h | 1 +
include/uapi/linux/ipv6.h | 1 +
kernel/bpf/verifier.c | 102 +-
kernel/trace/bpf_trace.c | 3 +-
kernel/trace/trace.c | 3 -
mm/gup.c | 2 +-
mm/hugetlb.c | 6 +-
mm/memory-failure.c | 2 +-
mm/memory_hotplug.c | 2 +-
mm/mempolicy.c | 5 +-
mm/migrate.c | 7 +-
mm/page_alloc.c | 5 +-
mm/swapfile.c | 1 +
net/bridge/br_netfilter_hooks.c | 1 +
net/can/j1939/address-claim.c | 40 +
net/can/j1939/transport.c | 4 -
net/ipv4/tcp_bpf.c | 4 +-
net/netrom/af_netrom.c | 5 +
net/openvswitch/datapath.c | 12 +-
net/qrtr/ns.c | 5 +-
net/rds/message.c | 6 +-
net/x25/af_x25.c | 6 +
net/xfrm/xfrm_compat.c | 4 +-
net/xfrm/xfrm_input.c | 3 +-
sound/pci/hda/patch_realtek.c | 3 +
sound/pci/hda/patch_via.c | 3 +
sound/pci/lx6464es/lx_core.c | 11 +-
sound/synth/emux/emux_nrpn.c | 3 +
tools/testing/selftests/net/forwarding/lib.sh | 4 +-
tools/testing/selftests/net/udpgso_bench.sh | 24 +-
tools/testing/selftests/net/udpgso_bench_rx.c | 4 +-
tools/testing/selftests/net/udpgso_bench_tx.c | 36 +-
119 files changed, 1573 insertions(+), 855 deletions(-)
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
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
` (7 subsequent siblings)
8 siblings, 0 replies; 26+ messages in thread
From: Pavel Machek @ 2023-02-13 17:26 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
Hi!
> 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.
CIP testing did not find any problems here:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-5.10.y
Tested-by: Pavel Machek (CIP) <pavel@denx.de>
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
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 9:16 ` Naresh Kamboju
2023-02-13 23:33 ` Shuah Khan
` (6 subsequent siblings)
8 siblings, 2 replies; 26+ messages in thread
From: Florian Fainelli @ 2023-02-13 19:50 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable, rmk+kernel, Srinivas Kandagatla
Cc: patches, linux-kernel, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, sudipm.mukherjee, srw, rwarsow
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
On 2/13/23 06:49, 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.
>
> 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
There is a regression coming from:
nvmem: core: fix registration vs use race
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.
--
Florian
[-- Attachment #2: 72116b0-bselinux-rack-23.log --]
[-- Type: text/x-log, Size: 39819 bytes --]
boot stbirv-lnx-3:users/fainelli/510/vmlinuz-initrd-arm ""
sensors\rsleep 5\rping -c 2 192.168.1.254\rcat /sys/devices/platform/rdb/*/dpfe_*\rpml\rsensors\rsleep 5\rping -c 2 192.168.1.254\rcat /sys/devices/platform/rdb/*/dpfe_*\rpml -d\rsensors\rsleep 5\rping -c 2 192.168.1.254\rcat /sys/devices/platform/rdb/*/dpfe_*\r8-0E-CB-6D, ipaddr 192.168.1.28, mask 255.255.255.0
gateway 192.168.1.254, nameserver 192.168.1.254, domain igp.broadcom.net
DHCP server 192.168.1.254, DHCP server MAC B8-AC-6F-80-AF-7E
Loader:zimg Filesys:tftp Dev:(null) File:stbirv-lnx-3:users/fainelli/510/vmlinuz-initrd-arm Options:(null)
Reading 21815520 bytes from zImage...........
Closing network 'eth0'
RPMB: disabling host access prior to program run.
Starting program at 0x2080000 (DTB @ 0x7612000)
astrasl-lib: v1.12
SBL v4.2.2.0, Signing Tool v4.4.2.0, Profile 72116B0 ZD, Part ZD, Release build .. OK
SRR: 0x02000000@0xbe000000
AMS v2.16.4.0, Signing Tool v4.4.2.0, Profile 72116B0 ZD, Part ZD, DevOnly build .. OK
Boot Status SBL 0x00000005 AMS 0x00000005
Mon Install done
Starting AMS with no ASF
Setting params for Linux @ 0x2080000 (DTB @ 0x7612000)
Monitor virtual pstates off
TZ CPU Mask: 0xe, NW CPU Mask: 0xf
Starting mon at 0x6400000 (params @ 0x70607a8 0x0)
AMS version v1.82:v2.16.4 v1.82-13-g4841047e6ea1-dirty
(2022-12-21 15:45:00 fainelli@fainelli-desktop)
Libsec v2.16.4 git:v1.82-AMS_2_16_4_82
AMS: clk: ver={v4,rdb=35d145a,pl=5c356dc,xls=28-12,S=7fd0}, nclks=245, Pmap4(nc=5)^[[0m
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 5.10.167-1.2pre-g7221b85b7881 (ff944844@stbirv-lnx-3) (arm-linux-gcc (stbgcc-8.3-0.4-dirty) 8.3.0, GNU ld (stbgcc-8.3-0.4-dirty) 2.32) #2 SMP Mon Feb 13 11:30:53 PST 2023
[ 0.000000] CPU: ARMv7 Processor [420f1000] revision 0 (ARMv7), cr=30c5383d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: BCM972116SV
[ 0.000000] random: crng init done
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] Alloc: MEMC0: 0x0000000010800000-0x00000000bdc00000
[ 0.000000] Alloc: MEMC0: 0x0000000100000000-0x0000000104000000
[ 0.000000] cma: Reserved 16 MiB at 0x000000000f800000
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000000000000-0x00000000107fffff]
[ 0.000000] Normal empty
[ 0.000000] HighMem [mem 0x0000000010800000-0x000000013fffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x00000000107fffff]
[ 0.000000] node 0: [mem 0x0000000010800000-0x00000000bdbfffff]
[ 0.000000] node 0: [mem 0x00000000bdc00000-0x00000000bdffefff]
[ 0.000000] node 0: [mem 0x00000000bdfff000-0x00000000bfffffff]
[ 0.000000] node 0: [mem 0x0000000100000000-0x0000000103ffffff]
[ 0.000000] node 0: [mem 0x0000000104000000-0x000000013fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000013fffffff]
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.1 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: Trusted OS resident on physical CPU 0x0
[ 0.000000] psci: SMC Calling Convention v1.1
[ 0.000000] percpu: Embedded 20 pages/cpu s49548 r8192 d24180 u81920
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1048048
[ 0.000000] Kernel command line:
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] software IO TLB: mapped [mem 0x0000000009600000-0x000000000d600000] (64MB)
[ 0.000000] Memory: 4008192K/4194304K available (12288K kernel code, 1248K rwdata, 2776K rodata, 18432K init, 277K bss, 169728K reserved, 16384K cma-reserved, 3891196K highmem)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] ftrace: allocating 39073 entries in 115 pages
[ 0.000000] ftrace: allocated 115 pages with 5 groups
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU event tracing is enabled.
[ 0.000000] Rude variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] GIC: Using split EOI/Deactivate mode
[ 0.000000] arch_timer: cp15 timer(s) running at 27.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x63a1e71a3, max_idle_ns: 440795203123 ns
[ 0.000006] sched_clock: 56 bits at 27MHz, resolution 37ns, wraps every 4398046511093ns
[ 0.000015] Switching to timer-based delay loop, resolution 37ns
[ 0.000287] Console: colour dummy device 80x30
[ 0.000607] printk: console [tty0] enabled
[ 0.000647] Calibrating delay loop (skipped), value calculated using timer frequency.. 54.00 BogoMIPS (lpj=27000)
[ 0.000669] pid_max: default: 32768 minimum: 301
[ 0.000786] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.000798] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.001358] CPU: Testing write buffer coherency: ok
[ 0.001650] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.001941] Setting up static identity map for 0x200000 - 0x200060
[ 0.002033] rcu: Hierarchical SRCU implementation.
[ 0.002888] brcmstb: biuctrl: MCP: Enabling write pairing
[ 0.003001] smp: Bringing up secondary CPUs ...
[ 0.003955] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.004888] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.005756] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.005810] smp: Brought up 1 node, 4 CPUs
[ 0.005848] SMP: Total of 4 processors activated (216.00 BogoMIPS).
[ 0.005857] CPU: All CPU(s) started in HYP mode.
[ 0.005864] CPU: Virtualization extensions available.
[ 0.006906] devtmpfs: initialized
[ 0.009695] VFP support v0.3: implementor 42 architecture 3 part 10 variant 0 rev 0
[ 0.009887] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[ 0.009921] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[ 0.010533] pinctrl core: initialized pinctrl subsystem
[ 0.011653] NET: Registered protocol family 16
[ 0.012533] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.013506] thermal_sys: Registered thermal governor 'step_wise'
[ 0.013525] thermal_sys: Registered thermal governor 'user_space'
[ 0.014004] cpuidle: using governor menu
[ 0.014051] No ATAGs?
[ 0.014146] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.014158] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.014475] /rdb/syscon@f0202400: Broadcom Brahma-B15 readahead cache
[ 0.014880] Serial: AMBA PL011 UART driver
[ 0.037034] SCSI subsystem initialized
[ 0.037429] usbcore: registered new interface driver usbfs
[ 0.037496] usbcore: registered new interface driver hub
[ 0.037546] usbcore: registered new device driver usb
[ 0.037636] mc: Linux media interface: v0.10
[ 0.037680] videodev: Linux video capture interface: v2.00
[ 0.037717] pps_core: LinuxPPS API ver. 1 registered
[ 0.037727] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.037753] PTP clock support registered
[ 0.038341] arm-scmi brcm_scmi@0: SCMI Notifications - Core Enabled.
[ 0.054874] arm-scmi brcm_scmi@0: SCMI Protocol v1.0 'brcm-scmi:' Firmware version 0x1
[ 0.055398] Advanced Linux Sound Architecture Driver Initialized.
[ 0.056210] clocksource: Switched to clocksource arch_sys_counter
[ 0.639489] NET: Registered protocol family 2
[ 0.639612] IP idents hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.639894] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[ 0.639920] TCP established hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.639942] TCP bind hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 0.639966] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.640055] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.640074] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.640159] NET: Registered protocol family 1
[ 0.640529] RPC: Registered named UNIX socket transport module.
[ 0.640540] RPC: Registered udp transport module.
[ 0.640548] RPC: Registered tcp transport module.
[ 0.640555] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.641128] PCI: CLS 0 bytes, default 64
[ 3.992327] hw perfevents: no interrupt-affinity property for /pmu, guessing.
[ 3.992584] hw perfevents: enabled with armv7_cortex_a15_on_a53 PMU driver, 7 counters available
[ 3.993853] Initialise system trusted keyrings
[ 3.994035] workingset: timestamp_bits=30 max_order=20 bucket_order=0
[ 3.997079] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 3.997556] NFS: Registering the id_resolver key type
[ 3.997587] Key type id_resolver registered
[ 3.997594] Key type id_legacy registered
[ 3.997647] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 3.997658] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[ 3.997682] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 3.997853] fuse: init (API version 7.32)
[ 3.998562] Key type asymmetric registered
[ 3.998584] Asymmetric key parser 'x509' registered
[ 3.998621] bounce: pool size: 64 pages
[ 3.998655] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[ 3.998669] io scheduler mq-deadline registered
[ 3.998677] io scheduler kyber registered
[ 3.999394] irq_brcmstb_l2: registered L2 intc (/rdb/interrupt-controller@f0403000, parent irq: 44)
[ 3.999516] irq_brcmstb_l2: registered L2 intc (/rdb/interrupt-controller@f0201000, parent irq: 45)
[ 3.999585] irq_brcmstb_l2: registered L2 intc (/rdb/interrupt-controller@f0201a00, parent irq: 46)
[ 3.999660] irq_brcmstb_l2: registered L2 intc (/rdb/interrupt-controller@f0410640, parent irq: 47)
[ 3.999732] irq_brcmstb_l2: registered L2 intc (/rdb/interrupt-controller@f04d1200, parent irq: 48)
[ 3.999815] irq_brcmstb_l2: registered L2 intc (/rdb/interrupt-controller@f041a600, parent irq: 49)
[ 3.999969] irq_brcmstb_l2: registered L2 intc (/rdb/interrupt-controller@f040a500, parent irq: 52)
[ 4.000040] irq_brcmstb_l2: registered L2 intc (/rdb/interrupt-controller@f041a400, parent irq: 53)
[ 4.000108] irq_brcmstb_l2: registered L2 intc (/rdb/interrupt-controller@f040a540, parent irq: 54)
[ 4.000177] irq_brcmstb_l2: registered L2 intc (/rdb/interrupt-controller@f041a440, parent irq: 55)
[ 4.000294] irq_brcmstb_l2: registered L2 intc (/rdb/interrupt-controller@f0419000, parent irq: 56)
[ 4.000743] brcm-gisb-arb f0400000.gisb-arb: registered irqs: 57, 58
[ 4.004690] brcm-pcie f0460000.pcie: host bridge /pcie@f0460000 ranges:
[ 4.004739] brcm-pcie f0460000.pcie: MEM 0x00c0000000..0x00dfffffff -> 0x00c0000000
[ 4.004761] brcm-pcie f0460000.pcie: IB MEM 0x0000000000..0x00bfffffff -> 0x0100000000
[ 4.004777] brcm-pcie f0460000.pcie: IB MEM 0x0100000000..0x013fffffff -> 0x01c0000000
[ 4.060530] brcmstb-pm-psci: Using PSCI based system PM (full featured)
[ 4.060595] debugfs: Directory 'brcmstb-pm' with parent '/' already present!
[ 4.061240] brcmstb_memc f1102000.memc-ddr: registered
[ 4.061923] brcm-waketimer f041a680.waketimer: wake IRQ found: 63
[ 4.061992] brcm-waketimer f041a680.waketimer: timer IRQ found: 64
[ 4.062363] brcm-waketimer f041a680.waketimer: registered as rtc0
[ 4.062409] brcm-waketimer f041a680.waketimer: setting system clock to 1970-01-01T00:00:28 UTC (28)
[ 4.062428] brcm-waketimer f041a680.waketimer: registered wake timer
[ 4.065944] brcmstb-scmi-dvfs scmi_dev.3: ClkVerTest: PASS: {v4,rdb=35d145a,pl=5c356dc,xls=28-12,S=7fd0}
[ 4.066659] arm-scmi brcm_scmi@0: Failed. SCMI protocol 22 not active.
[ 4.092472] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 4.095582] f040c000.serial: ttyS0 at MMIO 0xf040c000 (irq = 36, base_baud = 5062500) is a 16550A
[ 5.076647] printk: console [ttyS0] enabled
[ 5.083210] f040d000.serial: ttyS1 at MMIO 0xf040d000 (irq = 37, base_baud = 5062500) is a 16550A
[ 5.094382] f040e000.serial: ttyS2 at MMIO 0xf040e000 (irq = 38, base_baud = 5062500) is a 16550A
[ 5.109445] brd: module loaded
[ 5.117711] loop: module loaded
[ 5.122480] brcmstb_qspi f0200920.qspi: using bspi-mspi mode
[ 5.129216] spi-nor spi0.0: found mt25qu512a, expected m25p80
[ 5.135083] spi-nor spi0.0: mt25qu512a (65536 Kbytes)
[ 5.140210] 12 fixed-partitions partitions found on MTD device spi0.0
[ 5.146669] Creating 12 MTD partitions on "spi0.0":
[ 5.151562] 0x000000000000-0x000000180000 : "flash0.bolt"
[ 5.157220] sysfs: cannot create duplicate filename '/devices/platform/rdb/f0200920.qspi/spi_master/spi0/spi0.0/mtd/mtd0/mtd0'
[ 5.168647] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.10.167-1.2pre-g7221b85b7881 #2
[ 5.176577] Hardware name: Broadcom STB (Flattened Device Tree)
[ 5.182507] Backtrace:
[ 5.184972] [<c0d37da0>] (dump_backtrace) from [<c0d38050>] (show_stack+0x20/0x24)
[ 5.192557] r7:c36074d0 r6:60000013 r5:00000000 r4:c24bfdac
[ 5.198228] [<c0d38030>] (show_stack) from [<c0d3d180>] (dump_stack+0xa4/0xb8)
[ 5.205470] [<c0d3d0dc>] (dump_stack) from [<c0447e40>] (sysfs_warn_dup+0x68/0x74)
[ 5.213054] r7:c36074d0 r6:c363b7c0 r5:c36074d0 r4:c3342000
[ 5.218725] [<c0447dd8>] (sysfs_warn_dup) from [<c0447f5c>] (sysfs_create_dir_ns+0xbc/0xfc)
[ 5.227091] r7:c36074d0 r6:ffffffef r5:c2404d08 r4:c2bd8008
[ 5.232766] [<c0447ea0>] (sysfs_create_dir_ns) from [<c0714c28>] (kobject_add_internal+0xcc/0x36c)
[ 5.241740] r7:c365bcf8 r6:00000000 r5:c365bcf8 r4:c2bd8008
[ 5.247411] [<c0714b5c>] (kobject_add_internal) from [<c0714f28>] (kobject_add+0x60/0xbc)
[ 5.255604] r9:00000000 r8:00000000 r7:c365bcf8 r6:00000000 r5:c2bd8008 r4:c2404d08
[ 5.263366] [<c0714ec8>] (kobject_add) from [<c0835260>] (device_add+0x11c/0x7b0)
[ 5.270862] r3:00000000 r2:00000000
[ 5.274443] r7:c365bcf8 r6:c2404d08 r5:c2404d08 r4:c2bd8008
[ 5.280117] [<c0835144>] (device_add) from [<c0ab4a14>] (nvmem_register+0x31c/0x884)
[ 5.287875] r10:c1047438 r9:00000000 r8:00000000 r7:00000000 r6:c2404d08 r5:c29518e4
[ 5.295718] r4:c2bd8000
[ 5.298261] [<c0ab46f8>] (nvmem_register) from [<c08b66c4>] (add_mtd_device+0x294/0x574)
[ 5.306368] r10:c365bb50 r9:00000000 r8:c2404d08 r7:00000000 r6:05a00000 r5:c365bcf8
[ 5.314212] r4:c365bc00
[ 5.316752] [<c08b6430>] (add_mtd_device) from [<c08b9bd8>] (add_mtd_partitions+0xcc/0x170)
[ 5.325118] r9:c365bc00 r8:0000000c r7:c306f628 r6:c365b840 r5:c365b840 r4:00000001
[ 5.332878] [<c08b9b0c>] (add_mtd_partitions) from [<c08b9778>] (parse_mtd_partitions+0x114/0x4a8)
[ 5.341854] r10:00000000 r9:c365b840 r8:c2404d08 r7:00000000 r6:0000000c r5:00000000
[ 5.349698] r4:c24d1068
[ 5.352238] [<c08b9664>] (parse_mtd_partitions) from [<c08b6b18>] (mtd_device_parse_register+0x78/0x1e4)
[ 5.361735] r10:00000000 r9:00000000 r8:c2404d08 r7:00000000 r6:00000000 r5:00000000
[ 5.369577] r4:c365b840
[ 5.372121] [<c08b6aa0>] (mtd_device_parse_register) from [<c08e7d48>] (spi_nor_probe+0x28c/0x2cc)
[ 5.381096] r7:00000000 r6:04000000 r5:00000000 r4:c365b840
[ 5.386768] [<c08e7abc>] (spi_nor_probe) from [<c09066bc>] (spi_mem_probe+0x94/0xa0)
[ 5.394527] r9:c24d2300 r8:c2524960 r7:c24d2300 r6:c310c800 r5:c35efcc0 r4:c365b400
[ 5.402286] [<c0906628>] (spi_mem_probe) from [<c090177c>] (spi_drv_probe+0x94/0xb8)
[ 5.410043] r7:00000000 r6:c24d22f0 r5:00000000 r4:c365b400
[ 5.415715] [<c09016e8>] (spi_drv_probe) from [<c083aa9c>] (really_probe+0x11c/0x4f4)
[ 5.423559] r7:00000000 r6:c256d5f4 r5:c256d5ec r4:c365b400
[ 5.429230] [<c083a980>] (really_probe) from [<c083b0b8>] (driver_probe_device+0x88/0x204)
[ 5.437511] r10:c24c8aec r9:00000000 r8:00000001 r7:c2524960 r6:c2951ba4 r5:c24d2300
[ 5.445354] r4:c365b400
[ 5.447895] [<c083b030>] (driver_probe_device) from [<c083b400>] (__device_attach_driver+0xbc/0x120)
[ 5.457045] r9:00000000 r8:00000001 r7:c365b400 r6:c2951ba4 r5:00000001 r4:c24d2300
[ 5.464804] [<c083b344>] (__device_attach_driver) from [<c0838950>] (bus_for_each_drv+0x90/0xd4)
[ 5.473605] r7:c083b344 r6:c2951ba4 r5:c2404d08 r4:00000000
[ 5.479276] [<c08388c0>] (bus_for_each_drv) from [<c083a888>] (__device_attach+0x104/0x1dc)
[ 5.487642] r7:c310c800 r6:c365b444 r5:c2404d08 r4:c365b400
[ 5.493312] [<c083a784>] (__device_attach) from [<c083b480>] (device_initial_probe+0x1c/0x20)
[ 5.501852] r8:c256d5c4 r7:c310c800 r6:c24d263c r5:c365b400 r4:c365b400
[ 5.508567] [<c083b464>] (device_initial_probe) from [<c08398b4>] (bus_probe_device+0x94/0x9c)
[ 5.517195] [<c0839820>] (bus_probe_device) from [<c0835588>] (device_add+0x444/0x7b0)
[ 5.525127] r7:c310c800 r6:00000000 r5:c2404d08 r4:c365b400
[ 5.530797] [<c0835144>] (device_add) from [<c0902d10>] (spi_add_device+0xbc/0x1cc)
[ 5.538468] r10:c2b9e810 r9:00000001 r8:00000000 r7:c2b9e810 r6:00000000 r5:c310c800
[ 5.546310] r4:c365b400
[ 5.548850] [<c0902c54>] (spi_add_device) from [<c09031b0>] (of_register_spi_device+0x254/0x360)
[ 5.557651] r7:c310c800 r6:c2404d08 r5:cf7eaba8 r4:c365b400
[ 5.563322] [<c0902f5c>] (of_register_spi_device) from [<c0903830>] (spi_register_controller+0x574/0x82c)
[ 5.572906] r9:c2404d08 r8:c0ff0900 r7:cf7eabf8 r6:cf7eaba8 r5:00000000 r4:c310c800
[ 5.580666] [<c09032bc>] (spi_register_controller) from [<c090b8a8>] (bcm_qspi_probe+0x614/0x644)
[ 5.589555] r10:c2b9e810 r9:c2404d08 r8:00000000 r7:c2404d08 r6:c310cb80 r5:c2b9e800
[ 5.597397] r4:c310c800
[ 5.599939] [<c090b294>] (bcm_qspi_probe) from [<c0908f48>] (brcmstb_qspi_probe+0x1c/0x20)
[ 5.608218] r10:00000000 r9:c24d3300 r8:c2524960 r7:00000000 r6:c24d3300 r5:00000000
[ 5.616061] r4:c2b9e810
[ 5.618602] [<c0908f2c>] (brcmstb_qspi_probe) from [<c083d86c>] (platform_drv_probe+0x58/0xa8)
[ 5.627231] [<c083d814>] (platform_drv_probe) from [<c083aa9c>] (really_probe+0x11c/0x4f4)
[ 5.635510] r7:00000000 r6:c256d5f4 r5:c256d5ec r4:c2b9e810
[ 5.641180] [<c083a980>] (really_probe) from [<c083b0b8>] (driver_probe_device+0x88/0x204)
[ 5.649459] r10:c2539000 r9:c1259854 r8:c35ef2b8 r7:c2524960 r6:c24d3300 r5:c24d3300
[ 5.657301] r4:c2b9e810
[ 5.659842] [<c083b030>] (driver_probe_device) from [<c083b4ec>] (device_driver_attach+0x68/0x70)
[ 5.668731] r9:c1259854 r8:c35ef2b8 r7:c083b4f4 r6:c24d3300 r5:00000000 r4:c2b9e810
[ 5.676490] [<c083b484>] (device_driver_attach) from [<c083b5f8>] (__driver_attach+0x104/0x170)
[ 5.685203] r7:c083b4f4 r6:c24d3300 r5:c2b9e810 r4:c24d3300
[ 5.690873] [<c083b4f4>] (__driver_attach) from [<c0838854>] (bus_for_each_dev+0x84/0xc4)
[ 5.699066] r7:c083b4f4 r6:c24d3300 r5:c2404d08 r4:c2b73934
[ 5.704736] [<c08387d0>] (bus_for_each_dev) from [<c083a2c4>] (driver_attach+0x2c/0x30)
[ 5.712754] r7:00000000 r6:c35ef280 r5:c24c90b0 r4:c24d3300
[ 5.718424] [<c083a298>] (driver_attach) from [<c0839bb8>] (bus_add_driver+0x1b4/0x220)
[ 5.726443] [<c0839a04>] (bus_add_driver) from [<c083c140>] (driver_register+0x84/0x118)
[ 5.734549] r8:ffffe000 r7:00000000 r6:c122e828 r5:c2404d08 r4:c24d3300
[ 5.741264] [<c083c0bc>] (driver_register) from [<c083d7c0>] (__platform_driver_register+0x50/0x58)
[ 5.750325] r5:c2404d08 r4:c2515640
[ 5.753912] [<c083d770>] (__platform_driver_register) from [<c122e84c>] (brcmstb_qspi_driver_init+0x24/0x28)
[ 5.763759] [<c122e828>] (brcmstb_qspi_driver_init) from [<c0202244>] (do_one_initcall+0x64/0x26c)
[ 5.772738] [<c02021e0>] (do_one_initcall) from [<c12014bc>] (kernel_init_freeable+0x1ec/0x244)
[ 5.781452] r8:00000007 r7:c2a1c2c0 r6:c1259834 r5:0000011d r4:c1290ba4
[ 5.788168] [<c12012d0>] (kernel_init_freeable) from [<c0d462b8>] (kernel_init+0x18/0x12c)
[ 5.796448] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c0d462a0
[ 5.804291] r4:00000000
[ 5.806830] [<c0d462a0>] (kernel_init) from [<c0200138>] (ret_from_fork+0x14/0x3c)
[ 5.814413] Exception stack(0xc2951fb0 to 0xc2951ff8)
[ 5.819473] 1fa0: 00000000 00000000 00000000 00000000
[ 5.827666] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 5.835858] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 5.842483] r5:c0d462a0 r4:00000000
[ 5.846078] kobject_add_internal failed for mtd0 with -EEXIST, don't try to register things with the same name in the same directory.
[ 5.858106] mtd mtd0: Failed to register NVMEM device
[ 5.863340] Deleting MTD partitions on "spi0.0":
[ 5.868137] sysfs: cannot create duplicate filename '/bus/nvmem/devices/mtd0'
[ 5.875298] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.10.167-1.2pre-g7221b85b7881 #2
[ 5.883229] Hardware name: Broadcom STB (Flattened Device Tree)
[ 5.889157] Backtrace:
[ 5.891620] [<c0d37da0>] (dump_backtrace) from [<c0d38050>] (show_stack+0x20/0x24)
[ 5.899204] r7:c363b980 r6:60000013 r5:00000000 r4:c24bfdac
[ 5.904875] [<c0d38030>] (show_stack) from [<c0d3d180>] (dump_stack+0xa4/0xb8)
[ 5.912116] [<c0d3d0dc>] (dump_stack) from [<c0447e40>] (sysfs_warn_dup+0x68/0x74)
[ 5.919698] r7:c363b980 r6:c363b980 r5:c2b0d108 r4:c3343000
[ 5.925369] [<c0447dd8>] (sysfs_warn_dup) from [<c04481cc>] (sysfs_do_create_link_sd+0xec/0xf8)
[ 5.934083] r7:c363b980 r6:c2b0d108 r5:ffffffef r4:c35acb58
[ 5.939753] [<c04480e0>] (sysfs_do_create_link_sd) from [<c0448210>] (sysfs_create_link+0x38/0x44)
[ 5.948729] r9:c0e92434 r8:00000000 r7:c365b938 r6:00000000 r5:c24e5960 r4:c2bd8408
[ 5.956491] [<c04481d8>] (sysfs_create_link) from [<c0839768>] (bus_add_device+0x84/0x13c)
[ 5.964770] [<c08396e4>] (bus_add_device) from [<c0835510>] (device_add+0x3cc/0x7b0)
[ 5.972528] r7:c365b938 r6:00000000 r5:c2404d08 r4:c2bd8408
[ 5.978201] [<c0835144>] (device_add) from [<c0ab48d0>] (nvmem_register+0x1d8/0x884)
[ 5.985958] r10:c1047438 r9:00000000 r8:00000000 r7:00000000 r6:c2404d08 r5:c295198c
[ 5.993801] r4:c2bd8400
[ 5.996342] [<c0ab46f8>] (nvmem_register) from [<c08b66c4>] (add_mtd_device+0x294/0x574)
[ 6.004449] r10:00000000 r9:00000000 r8:c2404d08 r7:00000000 r6:05a00000 r5:c365b938
[ 6.012291] r4:c365b840
[ 6.014832] [<c08b6430>] (add_mtd_device) from [<c08b6bbc>] (mtd_device_parse_register+0x11c/0x1e4)
[ 6.023895] r9:00000000 r8:c2404d08 r7:00000000 r6:00000000 r5:ffffffef r4:c365b840
[ 6.031656] [<c08b6aa0>] (mtd_device_parse_register) from [<c08e7d48>] (spi_nor_probe+0x28c/0x2cc)
[ 6.040632] r7:00000000 r6:04000000 r5:00000000 r4:c365b840
[ 6.046303] [<c08e7abc>] (spi_nor_probe) from [<c09066bc>] (spi_mem_probe+0x94/0xa0)
[ 6.054061] r9:c24d2300 r8:c2524960 r7:c24d2300 r6:c310c800 r5:c35efcc0 r4:c365b400
[ 6.061820] [<c0906628>] (spi_mem_probe) from [<c090177c>] (spi_drv_probe+0x94/0xb8)
[ 6.069577] r7:00000000 r6:c24d22f0 r5:00000000 r4:c365b400
[ 6.075248] [<c09016e8>] (spi_drv_probe) from [<c083aa9c>] (really_probe+0x11c/0x4f4)
[ 6.083092] r7:00000000 r6:c256d5f4 r5:c256d5ec r4:c365b400
[ 6.088763] [<c083a980>] (really_probe) from [<c083b0b8>] (driver_probe_device+0x88/0x204)
[ 6.097042] r10:c24c8aec r9:00000000 r8:00000001 r7:c2524960 r6:c2951ba4 r5:c24d2300
[ 6.104885] r4:c365b400
[ 6.107426] [<c083b030>] (driver_probe_device) from [<c083b400>] (__device_attach_driver+0xbc/0x120)
[ 6.116575] r9:00000000 r8:00000001 r7:c365b400 r6:c2951ba4 r5:00000001 r4:c24d2300
[ 6.124335] [<c083b344>] (__device_attach_driver) from [<c0838950>] (bus_for_each_drv+0x90/0xd4)
[ 6.133137] r7:c083b344 r6:c2951ba4 r5:c2404d08 r4:00000000
[ 6.138807] [<c08388c0>] (bus_for_each_drv) from [<c083a888>] (__device_attach+0x104/0x1dc)
[ 6.147173] r7:c310c800 r6:c365b444 r5:c2404d08 r4:c365b400
[ 6.152844] [<c083a784>] (__device_attach) from [<c083b480>] (device_initial_probe+0x1c/0x20)
[ 6.161384] r8:c256d5c4 r7:c310c800 r6:c24d263c r5:c365b400 r4:c365b400
[ 6.168098] [<c083b464>] (device_initial_probe) from [<c08398b4>] (bus_probe_device+0x94/0x9c)
[ 6.176726] [<c0839820>] (bus_probe_device) from [<c0835588>] (device_add+0x444/0x7b0)
[ 6.184657] r7:c310c800 r6:00000000 r5:c2404d08 r4:c365b400
[ 6.190327] [<c0835144>] (device_add) from [<c0902d10>] (spi_add_device+0xbc/0x1cc)
[ 6.197998] r10:c2b9e810 r9:00000001 r8:00000000 r7:c2b9e810 r6:00000000 r5:c310c800
[ 6.205841] r4:c365b400
[ 6.208380] [<c0902c54>] (spi_add_device) from [<c09031b0>] (of_register_spi_device+0x254/0x360)
[ 6.217182] r7:c310c800 r6:c2404d08 r5:cf7eaba8 r4:c365b400
[ 6.222853] [<c0902f5c>] (of_register_spi_device) from [<c0903830>] (spi_register_controller+0x574/0x82c)
[ 6.232436] r9:c2404d08 r8:c0ff0900 r7:cf7eabf8 r6:cf7eaba8 r5:00000000 r4:c310c800
[ 6.240196] [<c09032bc>] (spi_register_controller) from [<c090b8a8>] (bcm_qspi_probe+0x614/0x644)
[ 6.249086] r10:c2b9e810 r9:c2404d08 r8:00000000 r7:c2404d08 r6:c310cb80 r5:c2b9e800
[ 6.256928] r4:c310c800
[ 6.259468] [<c090b294>] (bcm_qspi_probe) from [<c0908f48>] (brcmstb_qspi_probe+0x1c/0x20)
[ 6.267747] r10:00000000 r9:c24d3300 r8:c2524960 r7:00000000 r6:c24d3300 r5:00000000
[ 6.275590] r4:c2b9e810
[ 6.278129] [<c0908f2c>] (brcmstb_qspi_probe) from [<c083d86c>] (platform_drv_probe+0x58/0xa8)
[ 6.286757] [<c083d814>] (platform_drv_probe) from [<c083aa9c>] (really_probe+0x11c/0x4f4)
[ 6.295036] r7:00000000 r6:c256d5f4 r5:c256d5ec r4:c2b9e810
[ 6.300707] [<c083a980>] (really_probe) from [<c083b0b8>] (driver_probe_device+0x88/0x204)
[ 6.308987] r10:c2539000 r9:c1259854 r8:c35ef2b8 r7:c2524960 r6:c24d3300 r5:c24d3300
[ 6.316829] r4:c2b9e810
[ 6.319369] [<c083b030>] (driver_probe_device) from [<c083b4ec>] (device_driver_attach+0x68/0x70)
[ 6.328257] r9:c1259854 r8:c35ef2b8 r7:c083b4f4 r6:c24d3300 r5:00000000 r4:c2b9e810
[ 6.336015] [<c083b484>] (device_driver_attach) from [<c083b5f8>] (__driver_attach+0x104/0x170)
[ 6.344730] r7:c083b4f4 r6:c24d3300 r5:c2b9e810 r4:c24d3300
[ 6.350401] [<c083b4f4>] (__driver_attach) from [<c0838854>] (bus_for_each_dev+0x84/0xc4)
[ 6.358593] r7:c083b4f4 r6:c24d3300 r5:c2404d08 r4:c2b73934
[ 6.364264] [<c08387d0>] (bus_for_each_dev) from [<c083a2c4>] (driver_attach+0x2c/0x30)
[ 6.372283] r7:00000000 r6:c35ef280 r5:c24c90b0 r4:c24d3300
[ 6.377955] [<c083a298>] (driver_attach) from [<c0839bb8>] (bus_add_driver+0x1b4/0x220)
[ 6.385975] [<c0839a04>] (bus_add_driver) from [<c083c140>] (driver_register+0x84/0x118)
[ 6.394080] r8:ffffe000 r7:00000000 r6:c122e828 r5:c2404d08 r4:c24d3300
[ 6.400795] [<c083c0bc>] (driver_register) from [<c083d7c0>] (__platform_driver_register+0x50/0x58)
[ 6.409856] r5:c2404d08 r4:c2515640
[ 6.413442] [<c083d770>] (__platform_driver_register) from [<c122e84c>] (brcmstb_qspi_driver_init+0x24/0x28)
[ 6.423291] [<c122e828>] (brcmstb_qspi_driver_init) from [<c0202244>] (do_one_initcall+0x64/0x26c)
[ 6.432269] [<c02021e0>] (do_one_initcall) from [<c12014bc>] (kernel_init_freeable+0x1ec/0x244)
[ 6.440982] r8:00000007 r7:c2a1c2c0 r6:c1259834 r5:0000011d r4:c1290ba4
[ 6.447699] [<c12012d0>] (kernel_init_freeable) from [<c0d462b8>] (kernel_init+0x18/0x12c)
[ 6.455978] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c0d462a0
[ 6.463821] r4:00000000
[ 6.466360] [<c0d462a0>] (kernel_init) from [<c0200138>] (ret_from_fork+0x14/0x3c)
[ 6.473943] Exception stack(0xc2951fb0 to 0xc2951ff8)
[ 6.479004] 1fa0: 00000000 00000000 00000000 00000000
[ 6.487196] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 6.495388] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 6.502013] r5:c0d462a0 r4:00000000
[ 6.505635] mtd mtd0: Failed to register NVMEM device
[ 6.510832] spi-nor: probe of spi0.0 failed with error -17
[ 6.516646] brcmstb_qspi f0418000.mspi: using mspi mode
[ 6.525470] bcmgenet f0480000.ethernet: GENET 5.0 EPHY: 0x0000
[ 6.570267] unimac-mdio unimac-mdio.0: Broadcom UniMAC MDIO bus
[ 6.577641] e1000e: Intel(R) PRO/1000 Network Driver
[ 6.582660] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 6.588659] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
[ 6.596126] usbcore: registered new interface driver pegasus
[ 6.601836] usbcore: registered new interface driver r8152
[ 6.607362] usbcore: registered new interface driver asix
[ 6.612805] usbcore: registered new interface driver ax88179_178a
[ 6.618938] usbcore: registered new interface driver cdc_ether
[ 6.624820] usbcore: registered new interface driver cdc_ncm
[ 6.630757] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 6.637331] ehci-pci: EHCI PCI platform driver
[ 6.642536] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 6.648770] ohci-pci: OHCI PCI platform driver
[ 6.653271] ohci-platform: OHCI generic platform driver
[ 6.659594] usbcore: registered new interface driver cdc_acm
[ 6.665296] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 6.673368] usbcore: registered new interface driver usb-storage
[ 6.679938] i2c /dev entries driver
[ 6.684453] hwmon hwmon0: temp1_input not attached to any thermal zone
[ 6.691637] brcmstb_thermal f04d1500.thermal: registered AVS TMON of-sensor driver
[ 6.699985] bcm7038-wdt f040a5a8.watchdog: Registered BCM7038 Watchdog
[ 6.707817] sdhci: Secure Digital Host Controller Interface driver
[ 6.714064] sdhci: Copyright(c) Pierre Ossman
[ 6.718440] sdhci-pltfm: SDHCI platform and OF driver helper
[ 6.724595] arm-scmi brcm_scmi@0: Failed. SCMI protocol 17 not active.
[ 6.731271] hid: raw HID events driver (C) Jiri Kosina
[ 6.736678] usbcore: registered new interface driver usbhid
[ 6.742284] usbhid: USB HID core driver
[ 6.747583] NET: Registered protocol family 10
[ 6.752630] Segment Routing with IPv6
[ 6.756353] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 6.762705] NET: Registered protocol family 17
[ 6.767238] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 6.780338] 8021q: 802.1Q VLAN Support v1.8
[ 6.784575] Key type dns_resolver registered
[ 6.788872] Registering SWP/SWPB emulation handler
[ 6.793913] Loading compiled-in X.509 certificates
[ 6.809444] brcmstb-usb-phy f0b00200.usb-phy: Suspend Clock not found in Device Tree
[ 6.817818] brcm-pcie f0460000.pcie: host bridge /pcie@f0460000 ranges:
[ 6.824492] brcm-pcie f0460000.pcie: MEM 0x00c0000000..0x00dfffffff -> 0x00c0000000
[ 6.832623] brcm-pcie f0460000.pcie: IB MEM 0x0000000000..0x00bfffffff -> 0x0100000000
[ 6.840738] brcm-pcie f0460000.pcie: IB MEM 0x0100000000..0x013fffffff -> 0x01c0000000
[ 6.989198] brcm-pcie f0460000.pcie: link down
[ 6.998487] ehci-brcm f0b00500.ehci_v2: EHCI Host Controller
[ 7.004323] ehci-brcm f0b00500.ehci_v2: new USB bus registered, assigned bus number 1
[ 7.022414] ehci-brcm f0b00500.ehci_v2: irq 39, io mem 0xf0b00500
[ 7.035205] ehci-brcm f0b00500.ehci_v2: USB 2.0 started, EHCI 1.00
[ 7.041869] hub 1-0:1.0: USB hub found
[ 7.045662] hub 1-0:1.0: 1 port detected
[ 7.050323] ohci-platform f0b00600.ohci_v2: Generic Platform OHCI controller
[ 7.057577] ohci-platform f0b00600.ohci_v2: new USB bus registered, assigned bus number 2
[ 7.065946] ohci-platform f0b00600.ohci_v2: irq 40, io mem 0xf0b00600
[ 7.128639] hub 2-0:1.0: USB hub found
[ 7.132434] hub 2-0:1.0: 1 port detected
[ 7.137306] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 7.153357] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 7.160486] ALSA device list:
[ 7.163467] No soundcards found.
[ 7.181552] Freeing unused kernel memory: 18432K
[ 7.194400] Run /init as init process
Mounting /proc and /sys...
Looking for modules to load...
Mounting remaining file systems...
Starting rngd...
Switching to schedutil governor...
Setting cpu: 0
Setting cpu: 1
Setting cpu: 2
Setting cpu: 3
Configuring eth0 interface
[ 7.385647] unimac-mdio-0:01: Broadcom BCM72116 PHY revision: 0x00
[ 7.392417] bcmgenet f0480000.ethernet: configuring instance for internal PHY
[ 7.400291] bcmgenet f0480000.ethernet eth0: Link is Down
Configuring lo interface
Configuring sit0 interface
Starting network services
* WARNING: this system uses box mode #0 until Nexus is loaded.
* This box mode is extremely conservative and will not produce
* meaningful benchmarks when used. Consider loading the desired
* box mode through Nexus before benchmarking this system.
# sensors
scmi_sensors-virtual-0
Adapter: Virtual device
avs_stb_volt: 983.00 mV
avs_pvt_temp: +32.1 C
# sleep 5
[ 9.706183] bcmgenet f0480000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[ 9.714758] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
# ping -c 2 192.168.1.254
PING 192.168.1.254 (192.168.1.254): 56 data bytes
64 bytes from 192.168.1.254: seq=0 ttl=64 time=0.539 ms
64 bytes from 192.168.1.254: seq=1 ttl=64 time=0.324 ms
--- 192.168.1.254 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.324/0.431/0.539 ms
# cat /sys/devices/platform/rdb/*/dpfe_*
cat: can't open '/sys/devices/platform/rdb/*/dpfe_*': No such file or directory
# pml
[ 13.717888] brcm-waketimer f041a680.waketimer: Using sysfs attributes, consider using 'rtcwake'
Pass 1 out of 1, mode=none, tp_a[ 13.734880] PM: suspend entry (deep)
ll=1, cycle_tp=, sleep=, wakeup_[ 13.740989] Filesystems sync: 0.000 seconds
time=1
[ 13.750169] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 13.758279] OOM killer disabled.
[ 13.761524] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
[ 13.769648] printk: Suspending console(s) (use no_console_suspend to debug)
AMS: System is entering S2 (retention: 1)...^[[0m
[ 13.873572] bcmgenet f0480000.ethernet eth0: Link is Down
[ 13.877613] Disabling non-boot CPUs ...
[ 13.879261] CPU1 killed.
[ 13.881063] CPU2 killed.
[ 13.882939] CPU3 killed.
[ 13.883463] Enabling non-boot CPUs ...
[ 13.884391] CPU1 is up
[ 13.885198] CPU2 is up
[ 13.886023] CPU3 is up
[ 13.898317] bcmgenet f0480000.ethernet eth0: Link is Down
[ 14.005465] OOM killer enabled.
[ 14.008633] Restarting tasks ... done.
[ 14.013410] PM: suspend exit
------------------------------[ 14.017946] brcm-waketimer f041a680.waketimer: Using sysfs attributes, consider using 'rtcwake'
# sensors
scmi_sensors-virtual-0
Adapter: Virtual device
avs_stb_volt: 961.00 mV
avs_pvt_temp: +32.1 C
# sleep 5
[ 16.467499] bcmgenet f0480000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
# ping -c 2 192.168.1.254
PING 192.168.1.254 (192.168.1.254): 56 data bytes
64 bytes from 192.168.1.254: seq=0 ttl=64 time=0.541 ms
64 bytes from 192.168.1.254: seq=1 ttl=64 time=0.312 ms
--- 192.168.1.254 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.312/0.426/0.541 ms
# cat /sys/devices/platform/rdb/*/dpfe_*
cat: can't open '/sys/devices/platform/rdb/*/dpfe_*': No such file or directory
# pml -d
[ 20.218288] brcm-waketimer f041a680.waketimer: Using sysfs attributes, consider using 'rtcwake'
Pass 1 out of 1, mode=none, tp_a[ 20.234915] PM: suspend entry (deep)
ll=1, cycle_tp=, sleep=, wakeup_[ 20.241025] Filesystems sync: 0.000 seconds
time=1
[ 20.248721] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 20.256910] OOM killer disabled.
[ 20.260162] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 20.268691] printk: Suspending console(s) (use no_console_suspend to debug)
AMS: System is entering S3...^[[0m
\0CPU 0123
AVS init...
AVS init OK
AVS load:select_image: addr_offset: 00051000 part_offset: 00000000 bootStatus: 20252b25
AVS load_code offset =00051000
LOADED
I2C @ f041a380
BID: 00000010
BCM972116SV
using board #a
select_image: addr_offset: 00056800 part_offset: 00000000 bootStatus: 202b2525
MEMSYS-STD
SHMOO 03480100 BLD:memsys-72165a-m2rc2-3433-g129c38858b-dirty HW:hpg0_b2p8 shmoo_ver:3.72.1.0
MCB: FLEX
OVERTEMP: mon ON
AVS start:AVS resuming S3...
81840001
001ff308
10000008
OK
Resume DDR PHYs...Done
DDR0: !@ ffe09800 <= ffe084a0 006071f8 MEMSYS-0 @ f1100000 OK
Sdram Scramble OTP = 0x00000001
SCRAMBLE_S3
Sdram Scramble OK
select_image: addr_offset: 00020000 part_offset: 00000000 bootStatus: 2025252b
BFW load mode OTP = 0x0000000f
bfw_hash_locked = 0x00000000
BFW key3 OK, BFW load OK
BFW v4.8.1
PM: verify params @ 064a4140
PM: verify OK
DTU: enabled
MVBAR: 07008000 -> 06400000
PM: re-entry not covered by hash
PM: verify main memory, len 000040f0
PM: verify OK
MICH: disable success
AVS: Running!
status=000000ff
AVS-STB:
v=978
t=32089
PV=858
MV=978
PC2=0
AVS rev=032a0100
OS reentry @ 06400000
SSBM1
CLR BSS 0700a8b0 to 0700a920
SSBM2
CACHE FLUSH OK
STACK @ 0700af00
ARCH: CONFIG OK
astrasl-lib: v1.12
SBL v4.2.2.0, Signing Tool v4.4.2.0, Profile 72116B0 ZD, Part ZD, Release build .. OK
SRR: 0x02000000@0xbe000000
AMS v2.16.4.0, Signing Tool v4.4.2.0, Profile 72116B0 ZD, Part ZD, DevOnly build .. OK
Boot Status SBL 0x00000005 AMS 0x00000005
Starting AMS with no ASF
AMS version v1.82:v2.16.4 v1.82-13-g4841047e6ea1-dirty
(2022-12-21 15:45:00 fainelli@fainelli-desktop)
Libsec v2.16.4 git:v1.82-AMS_2_16_4_82
AMS: clk: ver={v4,rdb=35d145a,pl=5c356dc,xls=28-12,S=7fd0}, nclks=245, Pmap4(nc=5)^[[0m\r[ 20.372553] bcmgenet f0480000.ethernet eth0: Link is Down
[ 20.376573] Disabling non-boot CPUs ...
[ 20.378105] CPU1 killed.
[ 20.379845] CPU2 killed.
[ 20.381441] CPU3 killed.
[ 20.381902] Enabling non-boot CPUs ...
[ 20.382957] CPU1 is up
[ 20.383811] CPU2 is up
[ 20.384676] CPU3 is up
[ 20.416231] usb usb1: root hub lost power or was reset
[ 20.416306] bcmgenet f0480000.ethernet eth0: Link is Down
[ 20.472148] usb usb2: root hub lost power or was reset
[ 20.581769] OOM killer enabled.
[ 20.584930] Restarting tasks ... done.
[ 20.589282] PM: suspend exit
------------------------------
[ 20.593484] brcm-waketimer f041a680.waketimer: Using sysfs attributes, consider using 'rtcwake'
# sensors
scmi_sensors-virtual-0
Adapter: Virtual device
avs_stb_volt: 978.00 mV
avs_pvt_temp: +32.1 C
# sleep 5
[ 22.926562] bcmgenet f0480000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
# ping -c 2 192.168.1.254
PING 192.168.1.254 (192.168.1.254): 56 data bytes
64 bytes from 192.168.1.254: seq=0 ttl=64 time=0.561 ms
64 bytes from 192.168.1.254: seq=1 ttl=64 time=0.327 ms
--- 192.168.1.254 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.327/0.444/0.561 ms
# cat /sys/devices/platform/rdb/*/dpfe_*
cat: can't open '/sys/devices/platform/rdb/*/dpfe_*': No such file or directory
#
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
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-13 23:33 ` Shuah Khan
2023-02-14 6:51 ` Guenter Roeck
` (5 subsequent siblings)
8 siblings, 0 replies; 26+ messages in thread
From: Shuah Khan @ 2023-02-13 23:33 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow, Shuah Khan
On 2/13/23 07:49, 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.
>
> 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
>
Compiled and booted on my test system. No dmesg regressions.
Tested-by: Shuah Khan <skhan@linuxfoundation.org>
thanks,
-- Shuah
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
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 9:16 ` Naresh Kamboju
1 sibling, 2 replies; 26+ messages in thread
From: Greg Kroah-Hartman @ 2023-02-14 6:20 UTC (permalink / raw)
To: Florian Fainelli
Cc: stable, rmk+kernel, Srinivas Kandagatla, patches, linux-kernel,
torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, sudipm.mukherjee, srw, rwarsow
On Mon, Feb 13, 2023 at 11:50:24AM -0800, Florian Fainelli wrote:
> On 2/13/23 06:49, 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.
> >
> > 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
>
> There is a regression coming from:
>
> nvmem: core: fix registration vs use race
>
> 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.
Can you use `git bisect` to find the offending commit?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-13 14:49 [PATCH 5.10 000/139] 5.10.168-rc1 review Greg Kroah-Hartman
` (2 preceding siblings ...)
2023-02-13 23:33 ` Shuah Khan
@ 2023-02-14 6:51 ` Guenter Roeck
2023-02-14 11:05 ` Sudip Mukherjee (Codethink)
` (4 subsequent siblings)
8 siblings, 0 replies; 26+ messages in thread
From: Guenter Roeck @ 2023-02-14 6:51 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow
On 2/13/23 06:49, 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.
>
Building powerpc:ppc32_allmodconfig ... failed
--------------
Error log:
In file included from arch/powerpc/net/bpf_jit_comp.c:16:
arch/powerpc/net/bpf_jit32.h:131:8: error: redefinition of 'struct codegen_context'
131 | struct codegen_context {
| ^~~~~~~~~~~~~~~
In file included from arch/powerpc/net/bpf_jit32.h:13,
from arch/powerpc/net/bpf_jit_comp.c:16:
arch/powerpc/net/bpf_jit.h:124:8: note: originally defined here
124 | struct codegen_context {
| ^~~~~~~~~~~~~~~
arch/powerpc/net/bpf_jit_comp.c:18:20: error: redefinition of 'bpf_flush_icache'
18 | static inline void bpf_flush_icache(void *start, void *end)
| ^~~~~~~~~~~~~~~~
In file included from arch/powerpc/net/bpf_jit32.h:13,
from arch/powerpc/net/bpf_jit_comp.c:16:
arch/powerpc/net/bpf_jit.h:139:20: note: previous definition of 'bpf_flush_icache' with type 'void(void *, void *)'
139 | static inline void bpf_flush_icache(void *start, void *end)
| ^~~~~~~~~~~~~~~~
make[3]: *** [scripts/Makefile.build:286: arch/powerpc/net/bpf_jit_comp.o] Error 1
Guenter
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-13 19:50 ` Florian Fainelli
2023-02-14 6:20 ` Greg Kroah-Hartman
@ 2023-02-14 9:16 ` Naresh Kamboju
2023-02-14 13:21 ` Naresh Kamboju
1 sibling, 1 reply; 26+ messages in thread
From: Naresh Kamboju @ 2023-02-14 9:16 UTC (permalink / raw)
To: Greg Kroah-Hartman, Florian Fainelli
Cc: stable, rmk+kernel, Srinivas Kandagatla, patches, linux-kernel,
torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, sudipm.mukherjee, srw, rwarsow, christophe.kerello,
Arnd Bergmann
Hi Greg and Florian,
On Tue, 14 Feb 2023 at 01:20, Florian Fainelli <f.fainelli@gmail.com> wrote:
>
> On 2/13/23 06:49, 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.
> >
> > 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
>
> There is a regression coming from:
>
> nvmem: core: fix registration vs use race
>
> 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 <lkft@linaro.org>
[ 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
> --
> Florian
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-13 14:49 [PATCH 5.10 000/139] 5.10.168-rc1 review Greg Kroah-Hartman
` (3 preceding siblings ...)
2023-02-14 6:51 ` Guenter Roeck
@ 2023-02-14 11:05 ` Sudip Mukherjee (Codethink)
2023-02-14 17:04 ` Guenter Roeck
` (3 subsequent siblings)
8 siblings, 0 replies; 26+ messages in thread
From: Sudip Mukherjee (Codethink) @ 2023-02-14 11:05 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli, srw, rwarsow
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
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-14 6:20 ` Greg Kroah-Hartman
@ 2023-02-14 13:20 ` Russell King (Oracle)
2023-02-14 14:53 ` Russell King (Oracle)
1 sibling, 0 replies; 26+ messages in thread
From: Russell King (Oracle) @ 2023-02-14 13:20 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: Florian Fainelli, stable, Srinivas Kandagatla, patches,
linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage,
pavel, jonathanh, sudipm.mukherjee, srw, rwarsow
On Tue, Feb 14, 2023 at 07:20:46AM +0100, Greg Kroah-Hartman wrote:
> On Mon, Feb 13, 2023 at 11:50:24AM -0800, Florian Fainelli wrote:
> > On 2/13/23 06:49, 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.
> > >
> > > 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
> >
> > There is a regression coming from:
> >
> > nvmem: core: fix registration vs use race
> >
> > 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.
>
> Can you use `git bisect` to find the offending commit?
I would guess that there is something wrong with the backporting of
my series - possibly a patch was dropped from the series?
"nvmem: core: fix cleanup after dev_set_name()" missing, which
initialises the struct device? But if that was missing, then
"nvmem: core: fix registration vs use race" wouldn't apply.
... but then you did send me a failure notice for the above
blamed commit, so I wonder how you applied it.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-14 9:16 ` Naresh Kamboju
@ 2023-02-14 13:21 ` Naresh Kamboju
0 siblings, 0 replies; 26+ messages in thread
From: Naresh Kamboju @ 2023-02-14 13:21 UTC (permalink / raw)
To: Greg Kroah-Hartman, Florian Fainelli, rmk+kernel
Cc: stable, Srinivas Kandagatla, patches, linux-kernel, torvalds,
akpm, linux, shuah, patches, lkft-triage, pavel, jonathanh,
sudipm.mukherjee, srw, rwarsow, christophe.kerello,
Arnd Bergmann, Anders Roxell
On Tue, 14 Feb 2023 at 14:46, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> Hi Greg and Florian,
>
> On Tue, 14 Feb 2023 at 01:20, Florian Fainelli <f.fainelli@gmail.com> wrote:
> >
> > On 2/13/23 06:49, 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.
> > >
> > > 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
> >
> > There is a regression coming from:
> >
> > nvmem: core: fix registration vs use race
> >
> > 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.
Our bisection found this as the first bad commit and reverting this patch
solved the reported problem.
first bad commit: [a4aee79941de8559ce6e28d47fad22efc89bfe92]
nvmem: core: fix registration vs use race
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> [ 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
>
- Naresh
> --
> Linaro LKFT
> https://lkft.linaro.org
>
> > --
> > Florian
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
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
1 sibling, 1 reply; 26+ messages in thread
From: Russell King (Oracle) @ 2023-02-14 14:53 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: Florian Fainelli, stable, Srinivas Kandagatla, patches,
linux-kernel, torvalds, akpm, linux, shuah, patches, lkft-triage,
pavel, jonathanh, sudipm.mukherjee, srw, rwarsow
On Tue, Feb 14, 2023 at 07:20:46AM +0100, Greg Kroah-Hartman wrote:
> On Mon, Feb 13, 2023 at 11:50:24AM -0800, Florian Fainelli wrote:
> > On 2/13/23 06:49, 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.
> > >
> > > 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
> >
> > There is a regression coming from:
> >
> > nvmem: core: fix registration vs use race
> >
> > 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.
>
> Can you use `git bisect` to find the offending commit?
The reason for this is because, due to how my patch series was
backported, you have ended up with nvmem_register() initialising
its embedded device, and then calling device_add() on it _twice_.
Basically, the backport of:
"nvmem: core: fix registration vs use race"
is broken, because the original patch _moved_ the device_add() and
that has not been carried forward to whatever got applied to stable
trees.
It looks like the 5.15-stable version of this patch was correct.
Maybe whoever tried to fixup the failure needs to try again?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-14 14:53 ` Russell King (Oracle)
@ 2023-02-14 15:09 ` Sasha Levin
2023-02-14 15:25 ` Russell King (Oracle)
0 siblings, 1 reply; 26+ messages in thread
From: Sasha Levin @ 2023-02-14 15:09 UTC (permalink / raw)
To: Russell King (Oracle)
Cc: Greg Kroah-Hartman, Florian Fainelli, stable,
Srinivas Kandagatla, patches, linux-kernel, torvalds, akpm,
linux, shuah, patches, lkft-triage, pavel, jonathanh,
sudipm.mukherjee, srw, rwarsow
On Tue, Feb 14, 2023 at 02:53:13PM +0000, Russell King (Oracle) wrote:
>On Tue, Feb 14, 2023 at 07:20:46AM +0100, Greg Kroah-Hartman wrote:
>> On Mon, Feb 13, 2023 at 11:50:24AM -0800, Florian Fainelli wrote:
>> > On 2/13/23 06:49, 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.
>> > >
>> > > 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
>> >
>> > There is a regression coming from:
>> >
>> > nvmem: core: fix registration vs use race
>> >
>> > 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.
>>
>> Can you use `git bisect` to find the offending commit?
>
>The reason for this is because, due to how my patch series was
>backported, you have ended up with nvmem_register() initialising
>its embedded device, and then calling device_add() on it _twice_.
>
>Basically, the backport of:
>
> "nvmem: core: fix registration vs use race"
>
>is broken, because the original patch _moved_ the device_add() and
>that has not been carried forward to whatever got applied to stable
>trees.
>
>It looks like the 5.15-stable version of this patch was correct.
>
>Maybe whoever tried to fixup the failure needs to try again?
I've dropped the backport series from both 5.15 and 5.10.
--
Thanks,
Sasha
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-14 15:09 ` Sasha Levin
@ 2023-02-14 15:25 ` Russell King (Oracle)
2023-02-14 15:33 ` Sasha Levin
0 siblings, 1 reply; 26+ messages in thread
From: Russell King (Oracle) @ 2023-02-14 15:25 UTC (permalink / raw)
To: Sasha Levin
Cc: Greg Kroah-Hartman, Florian Fainelli, stable,
Srinivas Kandagatla, patches, linux-kernel, torvalds, akpm,
linux, shuah, patches, lkft-triage, pavel, jonathanh,
sudipm.mukherjee, srw, rwarsow
On Tue, Feb 14, 2023 at 10:09:38AM -0500, Sasha Levin wrote:
> On Tue, Feb 14, 2023 at 02:53:13PM +0000, Russell King (Oracle) wrote:
> > On Tue, Feb 14, 2023 at 07:20:46AM +0100, Greg Kroah-Hartman wrote:
> > > On Mon, Feb 13, 2023 at 11:50:24AM -0800, Florian Fainelli wrote:
> > > > On 2/13/23 06:49, 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.
> > > > >
> > > > > 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
> > > >
> > > > There is a regression coming from:
> > > >
> > > > nvmem: core: fix registration vs use race
> > > >
> > > > 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.
> > >
> > > Can you use `git bisect` to find the offending commit?
> >
> > The reason for this is because, due to how my patch series was
> > backported, you have ended up with nvmem_register() initialising
> > its embedded device, and then calling device_add() on it _twice_.
> >
> > Basically, the backport of:
> >
> > "nvmem: core: fix registration vs use race"
> >
> > is broken, because the original patch _moved_ the device_add() and
> > that has not been carried forward to whatever got applied to stable
> > trees.
> >
> > It looks like the 5.15-stable version of this patch was correct.
> >
> > Maybe whoever tried to fixup the failure needs to try again?
>
> I've dropped the backport series from both 5.15 and 5.10.
So you've dropped what looks to be a perfectly good backport in 5.15,
and all of the 5.10 despite it just being the last patch which is the
problem. Sounds like a total over-reaction to me.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-14 15:25 ` Russell King (Oracle)
@ 2023-02-14 15:33 ` Sasha Levin
2023-02-14 15:39 ` Russell King (Oracle)
0 siblings, 1 reply; 26+ messages in thread
From: Sasha Levin @ 2023-02-14 15:33 UTC (permalink / raw)
To: Russell King (Oracle)
Cc: Greg Kroah-Hartman, Florian Fainelli, stable,
Srinivas Kandagatla, patches, linux-kernel, torvalds, akpm,
linux, shuah, patches, lkft-triage, pavel, jonathanh,
sudipm.mukherjee, srw, rwarsow
On Tue, Feb 14, 2023 at 03:25:52PM +0000, Russell King (Oracle) wrote:
>On Tue, Feb 14, 2023 at 10:09:38AM -0500, Sasha Levin wrote:
>> On Tue, Feb 14, 2023 at 02:53:13PM +0000, Russell King (Oracle) wrote:
>> > On Tue, Feb 14, 2023 at 07:20:46AM +0100, Greg Kroah-Hartman wrote:
>> > > On Mon, Feb 13, 2023 at 11:50:24AM -0800, Florian Fainelli wrote:
>> > > > On 2/13/23 06:49, 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.
>> > > > >
>> > > > > 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
>> > > >
>> > > > There is a regression coming from:
>> > > >
>> > > > nvmem: core: fix registration vs use race
>> > > >
>> > > > 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.
>> > >
>> > > Can you use `git bisect` to find the offending commit?
>> >
>> > The reason for this is because, due to how my patch series was
>> > backported, you have ended up with nvmem_register() initialising
>> > its embedded device, and then calling device_add() on it _twice_.
>> >
>> > Basically, the backport of:
>> >
>> > "nvmem: core: fix registration vs use race"
>> >
>> > is broken, because the original patch _moved_ the device_add() and
>> > that has not been carried forward to whatever got applied to stable
>> > trees.
>> >
>> > It looks like the 5.15-stable version of this patch was correct.
>> >
>> > Maybe whoever tried to fixup the failure needs to try again?
>>
>> I've dropped the backport series from both 5.15 and 5.10.
>
>So you've dropped what looks to be a perfectly good backport in 5.15,
>and all of the 5.10 despite it just being the last patch which is the
>problem. Sounds like a total over-reaction to me.
The context is that we want to get the releases out today, and neither
of us will have time to verify that we did the right thing in 5.15 in
the next few hours.
I'm just defering it to the next release cycle which is probably a few
days away, not completely throwing it away.... why is it such a big
deal?
--
Thanks,
Sasha
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-14 15:33 ` Sasha Levin
@ 2023-02-14 15:39 ` Russell King (Oracle)
0 siblings, 0 replies; 26+ messages in thread
From: Russell King (Oracle) @ 2023-02-14 15:39 UTC (permalink / raw)
To: Sasha Levin
Cc: Greg Kroah-Hartman, Florian Fainelli, stable,
Srinivas Kandagatla, patches, linux-kernel, torvalds, akpm,
linux, shuah, patches, lkft-triage, pavel, jonathanh,
sudipm.mukherjee, srw, rwarsow
On Tue, Feb 14, 2023 at 10:33:15AM -0500, Sasha Levin wrote:
> On Tue, Feb 14, 2023 at 03:25:52PM +0000, Russell King (Oracle) wrote:
> > On Tue, Feb 14, 2023 at 10:09:38AM -0500, Sasha Levin wrote:
> > > On Tue, Feb 14, 2023 at 02:53:13PM +0000, Russell King (Oracle) wrote:
> > > > On Tue, Feb 14, 2023 at 07:20:46AM +0100, Greg Kroah-Hartman wrote:
> > > > > On Mon, Feb 13, 2023 at 11:50:24AM -0800, Florian Fainelli wrote:
> > > > > > On 2/13/23 06:49, 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.
> > > > > > >
> > > > > > > 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
> > > > > >
> > > > > > There is a regression coming from:
> > > > > >
> > > > > > nvmem: core: fix registration vs use race
> > > > > >
> > > > > > 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.
> > > > >
> > > > > Can you use `git bisect` to find the offending commit?
> > > >
> > > > The reason for this is because, due to how my patch series was
> > > > backported, you have ended up with nvmem_register() initialising
> > > > its embedded device, and then calling device_add() on it _twice_.
> > > >
> > > > Basically, the backport of:
> > > >
> > > > "nvmem: core: fix registration vs use race"
> > > >
> > > > is broken, because the original patch _moved_ the device_add() and
> > > > that has not been carried forward to whatever got applied to stable
> > > > trees.
> > > >
> > > > It looks like the 5.15-stable version of this patch was correct.
> > > >
> > > > Maybe whoever tried to fixup the failure needs to try again?
> > >
> > > I've dropped the backport series from both 5.15 and 5.10.
> >
> > So you've dropped what looks to be a perfectly good backport in 5.15,
> > and all of the 5.10 despite it just being the last patch which is the
> > problem. Sounds like a total over-reaction to me.
>
> The context is that we want to get the releases out today, and neither
> of us will have time to verify that we did the right thing in 5.15 in
> the next few hours.
>
> I'm just defering it to the next release cycle which is probably a few
> days away, not completely throwing it away.... why is it such a big
> deal?
Maybe because you didn't explain that it was being dropped
_temporarily_?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-13 14:49 [PATCH 5.10 000/139] 5.10.168-rc1 review Greg Kroah-Hartman
` (4 preceding siblings ...)
2023-02-14 11:05 ` Sudip Mukherjee (Codethink)
@ 2023-02-14 17:04 ` Guenter Roeck
2023-02-14 17:59 ` Guenter Roeck
2023-02-14 17:15 ` Guenter Roeck
` (2 subsequent siblings)
8 siblings, 1 reply; 26+ messages in thread
From: Guenter Roeck @ 2023-02-14 17:04 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow
On 2/13/23 06:49, 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.
>
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.
Guenter
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-13 14:49 [PATCH 5.10 000/139] 5.10.168-rc1 review Greg Kroah-Hartman
` (5 preceding siblings ...)
2023-02-14 17:04 ` Guenter Roeck
@ 2023-02-14 17:15 ` Guenter Roeck
2023-02-14 17:51 ` Guenter Roeck
2023-02-14 19:45 ` Salvatore Bonaccorso
2023-02-15 7:30 ` zhouzhixiu
8 siblings, 1 reply; 26+ messages in thread
From: Guenter Roeck @ 2023-02-14 17:15 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow
On 2/13/23 06:49, 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.
>
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.
Guenter
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
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:05 ` Greg Kroah-Hartman
0 siblings, 2 replies; 26+ messages in thread
From: Guenter Roeck @ 2023-02-14 17:51 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow
On 2/14/23 09:15, Guenter Roeck wrote:
> On 2/13/23 06:49, 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.
>>
>
> 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.
Guenter
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
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
1 sibling, 1 reply; 26+ messages in thread
From: Linus Torvalds @ 2023-02-14 17:54 UTC (permalink / raw)
To: Guenter Roeck
Cc: Greg Kroah-Hartman, stable, patches, linux-kernel, akpm, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow
On Tue, Feb 14, 2023 at 9:51 AM Guenter Roeck <linux@roeck-us.net> wrote:
>
> Reverting the nvmem patches fixed this problem.
But upstream is fine?
Linus
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-14 17:04 ` Guenter Roeck
@ 2023-02-14 17:59 ` Guenter Roeck
0 siblings, 0 replies; 26+ messages in thread
From: Guenter Roeck @ 2023-02-14 17:59 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow
On 2/14/23 09:04, Guenter Roeck wrote:
> On 2/13/23 06:49, 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.
>>
>
> 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 also caused by the nvmem problem.
Guenter
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-14 17:51 ` Guenter Roeck
2023-02-14 17:54 ` Linus Torvalds
@ 2023-02-14 18:05 ` Greg Kroah-Hartman
1 sibling, 0 replies; 26+ messages in thread
From: Greg Kroah-Hartman @ 2023-02-14 18:05 UTC (permalink / raw)
To: Guenter Roeck
Cc: stable, patches, linux-kernel, torvalds, akpm, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow
On Tue, Feb 14, 2023 at 09:51:39AM -0800, Guenter Roeck wrote:
> On 2/14/23 09:15, Guenter Roeck wrote:
> > On 2/13/23 06:49, 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.
> > >
> >
> > 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.
nvmem patches are now dropped and a -rc2 is pushed out.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-14 17:54 ` Linus Torvalds
@ 2023-02-14 18:09 ` Guenter Roeck
0 siblings, 0 replies; 26+ messages in thread
From: Guenter Roeck @ 2023-02-14 18:09 UTC (permalink / raw)
To: Linus Torvalds
Cc: Greg Kroah-Hartman, stable, patches, linux-kernel, akpm, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow
On 2/14/23 09:54, Linus Torvalds wrote:
> On Tue, Feb 14, 2023 at 9:51 AM Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> Reverting the nvmem patches fixed this problem.
>
> But upstream is fine?
>
Yes, this was a bad backport. One of the nvmem patches was missing
from the backport. However, a fix for that missing patch was backported,
causing a double device registration and all kinds of interesting
problems.
Guenter
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-13 14:49 [PATCH 5.10 000/139] 5.10.168-rc1 review Greg Kroah-Hartman
` (6 preceding siblings ...)
2023-02-14 17:15 ` Guenter Roeck
@ 2023-02-14 19:45 ` Salvatore Bonaccorso
2023-02-14 19:57 ` Guenter Roeck
2023-02-15 7:30 ` zhouzhixiu
8 siblings, 1 reply; 26+ messages in thread
From: Salvatore Bonaccorso @ 2023-02-14 19:45 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: stable, patches, linux-kernel, torvalds, akpm, linux, shuah,
patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow
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.
>
> 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 ]---
Regards,
Salvatore
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-14 19:45 ` Salvatore Bonaccorso
@ 2023-02-14 19:57 ` Guenter Roeck
2023-02-14 20:30 ` Salvatore Bonaccorso
0 siblings, 1 reply; 26+ messages in thread
From: Guenter Roeck @ 2023-02-14 19:57 UTC (permalink / raw)
To: Salvatore Bonaccorso, Greg Kroah-Hartman
Cc: stable, patches, linux-kernel, torvalds, akpm, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow
On 2/14/23 11:45, Salvatore Bonaccorso wrote:
> 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.
>>
>> 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 ]---
>
This is caused by the bad nvmem patch in -rc1. -rc2 has the fix.
Guenter
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-14 19:57 ` Guenter Roeck
@ 2023-02-14 20:30 ` Salvatore Bonaccorso
0 siblings, 0 replies; 26+ messages in thread
From: Salvatore Bonaccorso @ 2023-02-14 20:30 UTC (permalink / raw)
To: Guenter Roeck, gregkh
Cc: Greg Kroah-Hartman, stable, patches, linux-kernel, torvalds,
akpm, shuah, patches, lkft-triage, pavel, jonathanh, f.fainelli,
sudipm.mukherjee, srw, rwarsow
Hi Guenter,
On Tue, Feb 14, 2023 at 11:57:04AM -0800, Guenter Roeck wrote:
> On 2/14/23 11:45, Salvatore Bonaccorso wrote:
> > 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.
> > >
> > > 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 ]---
> >
>
> This is caused by the bad nvmem patch in -rc1. -rc2 has the fix.
Confirmed; -rc3 boots fine.
For 5.10.168-rc3:
Tested-by: Salvatore Bonaccorso <carnil@debian.org>
Regards,
Salvatore
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH 5.10 000/139] 5.10.168-rc1 review
2023-02-13 14:49 [PATCH 5.10 000/139] 5.10.168-rc1 review Greg Kroah-Hartman
` (7 preceding siblings ...)
2023-02-14 19:45 ` Salvatore Bonaccorso
@ 2023-02-15 7:30 ` zhouzhixiu
8 siblings, 0 replies; 26+ messages in thread
From: zhouzhixiu @ 2023-02-15 7:30 UTC (permalink / raw)
To: Greg Kroah-Hartman, stable
Cc: patches, linux-kernel, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee, srw,
rwarsow
On 2023/2/13 22:49, 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.
>
> 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
>
> -------------
Tested on arm64 and x86 for 5.10.168-rc1,
Kernel
repo:https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Branch: linux-5.10.y
Version: 5.10.168-rc1
Commit: 65fa84413c15ee131ad4b76077c48f0603d1d8ec
Compiler: gcc version 7.3.0 (GCC)
arm64:
--------------------------------------------------------------------
Testcase Result Summary:
total: 9023
passed: 9023
failed: 0
timeout: 0
--------------------------------------------------------------------
x86:
--------------------------------------------------------------------
Testcase Result Summary:
total: 9023
passed: 9023
failed: 0
timeout: 0
--------------------------------------------------------------------
Tested-by: Hulk Robot <hulkrobot@huawei.com>
^ permalink raw reply [flat|nested] 26+ messages in thread
end of thread, other threads:[~2023-02-15 7:30 UTC | newest]
Thread overview: 26+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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)
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).