Re: freeze during boot regression Re: [PATCH 6.12 000/265] 6.12.77-rc1 review
From: Ron Economos
Date: Fri Mar 13 2026 - 02:10:41 EST
On 3/12/26 22:55, Barry K. Nathan wrote:
On 3/12/26 22:32, Barry K. Nathan wrote:
On 3/12/26 13:06, Greg Kroah-Hartman wrote:[snip]
This is the start of the stable review cycle for the 6.12.77 release.
There are 265 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 Fri, 13 Mar 2026 20:09:29 +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/v6.x/stable-review/patch-6.12.77-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-6.12.y
and the diffstat can be found below.
thanks,
greg k-h
Intermittently, but significantly greater than 50% of the time,
6.12.77-rc1 fails to boot on my Lenovo ThinkPad T14 Gen 1 running Debian
12 bookworm. When boot fails, the last couple lines of console output
(retyped from a photo) are:
Loading, please wait...
Starting systemd-udevd version 252.39-1~deb12u1
I will begin bisection shortly. I happen to have also previously
compiled 6.12.76 + stable-queue as of
commit 4b2b2b5cf3cd78f4de4646687a4efecbd21643af, and that shows the same
boot failures. That means the following patches are *not* to blame for
the problem:
I also happen to have previously compiled 6.12.76 + stable-queue as of
commit 8d45879cc803965facf8d8257f13d130508b5986, and that also shows
the same boot failures, so that narrows the cause down to the
following 40 patches:
drm-vmwgfx-fix-invalid-kref_put-callback-in-vmw_bo_d.patch
drm-vmwgfx-return-the-correct-value-in-vmw_translate.patch
drm-logicvc-fix-device-node-reference-leak-in-logicv.patch
kvm-arm64-advertise-support-for-feat_sctlr2.patch
kvm-arm64-hide-s1poe-from-guests-when-not-supported-.patch
irqchip-sifive-plic-fix-frozen-interrupt-due-to-affi.patch
scsi-lpfc-properly-set-wc-for-dpp-mapping.patch
scsi-pm8001-fix-use-after-free-in-pm8001_queue_comma.patch
alsa-scarlett2-fix-redeclaration-of-loop-variable.patch
alsa-scarlett2-fix-dsp-filter-control-array-handling.patch
alsa-usb-audio-remove-validate_rates-quirk-for-focus.patch
x86-fred-correct-speculative-safety-in-fred_extint.patch
sched-fair-fix-eevdf-entity-placement-bug-causing-sc.patch
sched-fair-fix-lag-clamp.patch
rseq-clarify-rseq-registration-rseq_size-bound-check.patch
cgroup-cpuset-fix-incorrect-use-of-cpuset_update_tas.patch
scsi-ufs-core-move-link-recovery-for-hibern8-exit-fa.patch
alsa-usb-audio-cap-the-packet-size-pre-calculations.patch
alsa-usb-audio-use-inclusive-terms.patch
perf-fix-__perf_event_overflow-vs-perf_remove_from_c.patch
s390-idle-fix-cpu-idle-exit-cpu-time-accounting.patch
s390-vtime-fix-virtual-timer-forwarding.patch
pci-endpoint-introduce-pci_epc_function_is_valid.patch
pci-endpoint-introduce-pci_epc_mem_map-unmap.patch
pci-dwc-endpoint-implement-the-pci_epc_ops-align_add.patch
pci-dwc-ep-use-align-addr-function-for-dw_pcie_ep_ra.patch
pci-dwc-ep-flush-msi-x-write-before-unmapping-its-at.patch
drm-amdgpu-unlock-a-mutex-before-destroying-it.patch
drm-amdgpu-replace-kzalloc-copy_from_user-with-memdu.patch
drm-amdgpu-fix-locking-bugs-in-error-paths.patch
alsa-pci-hda-use-snd_kcontrol_chip.patch
alsa-hda-cs35l56-fix-signedness-error-in-cs35l56_hda.patch
btrfs-fix-incorrect-key-offset-in-error-message-in-c.patch
btrfs-fix-objectid-value-in-error-message-in-check_e.patch
btrfs-fix-warning-in-scrub_verify_one_metadata.patch
btrfs-print-correct-subvol-num-if-active-swapfile-pr.patch
btrfs-fix-compat-mask-in-error-messages-in-btrfs_che.patch
bpf-arm64-force-8-byte-alignment-for-jit-buffer-to-p.patch
bpf-fix-stack-out-of-bounds-write-in-devmap.patch
pci-correct-pci_cap_exp_endpoint_sizeof_v2-value.patch
I expect my next followup to be once I finish bisection.
I'm seeing this WARN on RISC-V in the same place.
Starting systemd-udevd version 255.4-1ubuntu8.12
[ 5.417957] usb 1-2: new high-speed USB device number 2 using xhci_hcd
[ 5.765956] ------------[ cut here ]------------
[ 5.765976] WARNING: CPU: 0 PID: 17 at kernel/sched/fair.c:5266 place_entity+0x130/0x138
[ 5.766013] Modules linked in:
[ 5.766028] CPU: 0 UID: 0 PID: 17 Comm: rcu_preempt Not tainted 6.12.77-rc1 #2
[ 5.766038] Hardware name: SiFive HiFive Unmatched A00 (DT)
[ 5.766043] epc : place_entity+0x130/0x138
[ 5.766052] ra : place_entity+0x9c/0x138
[ 5.766061] epc : ffffffff800721c8 ra : ffffffff80072134 sp : ffffffc6000a3af0
[ 5.766067] gp : ffffffff823a8a70 tp : ffffffd6808c1d80 t0 : 0000000000000000
[ 5.766072] t1 : 0000000000000000 t2 : 0000000000000000 s0 : ffffffc6000a3b30
[ 5.766078] s1 : ffffffd9fed138c0 a0 : 0000000000577fff a1 : ffffffd681175400
[ 5.766084] a2 : 0000000000000000 a3 : 0000000000000177 a4 : 0000000000000000
[ 5.766089] a5 : 0000000026fdb4a5 a6 : 0000000000000000 a7 : 0000000000000002
[ 5.766095] s2 : 0000000000000000 s3 : ffffffd9fed137c0 s4 : ffffffd682b1d880
[ 5.766100] s5 : 0000000000000200 s6 : 0000000000000003 s7 : 0000000000000001
[ 5.766106] s8 : ffffffd9fed138c0 s9 : 0000000000200b20 s10: ffffffd681175400
[ 5.766112] s11: 0000000000000000 t3 : 0000000000000000 t4 : 0000000000000000
[ 5.766117] t5 : 0000000000000000 t6 : 0000000000000000
[ 5.766121] status: 0000000200000100 badaddr: 0000000000000177 cause: 0000000000000003
[ 5.766130] [<ffffffff800721c8>] place_entity+0x130/0x138
[ 5.766141] [<ffffffff80072780>] reweight_entity+0x178/0x1a0
[ 5.766151] [<ffffffff8007285e>] update_cfs_group+0x76/0xa8
[ 5.766161] [<ffffffff80073340>] dequeue_entities+0x120/0x550
[ 5.766171] [<ffffffff800738c4>] pick_task_fair+0x84/0x108
[ 5.766179] [<ffffffff8007b954>] pick_next_task_fair+0x1c/0x1b0
[ 5.766192] [<ffffffff80e2fe72>] __schedule+0x172/0xc10
[ 5.766204] [<ffffffff80e30932>] schedule+0x22/0x140
[ 5.766212] [<ffffffff80e36df0>] schedule_timeout+0x80/0x180
[ 5.766226] [<ffffffff800d3586>] rcu_gp_fqs_loop+0xfe/0x4d0
[ 5.766243] [<ffffffff800d6a12>] rcu_gp_kthread+0x122/0x158
[ 5.766255] [<ffffffff80050280>] kthread+0xc8/0xe8
[ 5.766268] [<ffffffff80e39cce>] ret_from_fork+0xe/0x18
[ 5.766282] ---[ end trace 0000000000000000 ]---
[ 5.992429] usb 1-2: New USB device found, idVendor=174c, idProduct=2074, bcdDevice= 0.01
[ 5.999916] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 6.007028] usb 1-2: Product: AS2107
Probably those sched/fair patches.