Linux kernel regression status

[next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive]

current cycle (v7.2.. aka v7.3-rc), culprit identified
eddba19b8b5f (v7.3-rc1)	*PCI/AER: MacBookPro16,1 powers off ~20 s after boot* by Perlow, Jason Earliest & latest activity: & . Latest five known activities: Re: [REGRESSION] PCI/AER: MacBookPro16,1 powers off ~20 s after boot , by Aditya Garg Re: [REGRESSION] PCI/AER: MacBookPro16,1 powers off ~20 s after boot , by Lukas Wunner Re: [REGRESSION] PCI/AER: MacBookPro16,1 powers off ~20 s after boot , by Aditya Garg Re: [REGRESSION] PCI/AER: MacBookPro16,1 powers off ~20 s after boot , by Alex Deucher Re: [REGRESSION] PCI/AER: MacBookPro16,1 powers off ~20 s after boot , by Perlow, Jason Regzbot command history: introduced: eddba19b8b5f76d57424ee328a68fd495c5db857 , by Perlow, Jason When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: eddba19b8b5f ("PCI/AER: Support Advisory Non-Fatal Errors") Reported-by: Perlow, Jason <jperlow@gmail.com> Link: https://lore.kernel.org/r/CABZrw2HcaOh3DHTJtxU5dXrb3Vg19scr6%2BqR-xe_%2BR7rME35_Q@mail.gmail.com/
447cbe95ebb9 (v7.3-rc1)	*vlan: IOMMU DMA faults on macvlan/vlan with bnxt_en* by Stefan Fleischmann Earliest & latest activity: & . Noteworthy: [1], [2], [3], [patch (SOB)]. [1]: Re: [PATCH net] bnxt_en: fix DMA mapping length for padded small packets [implicit due to Link/Closes tag] , by netdev-bot+sashiko (monitored) [2]: [PATCH v2 net] bnxt_en: fix DMA mapping length for padded small packets [implicit due to Link/Closes tag] , by Eric Dumazet (monitored) [3]: [PATCH v3 net] bnxt_en: fix DMA mapping length for padded small packets [implicit due to Link/Closes tag] , by Eric Dumazet (monitored) Latest patch: [PATCH v3 net] bnxt_en: fix DMA mapping length for padded small packets , by Eric Dumazet; signed-off-by present Earlier patches: 1, 2, 3, 4 Latest five known activities: [PATCH v3 net] bnxt_en: fix DMA mapping length for padded small packets , by Eric Dumazet; contains a signed-off patch Re: [PATCH v2 net] bnxt_en: fix DMA mapping length for padded small packets , by Eric Dumazet Re: [PATCH v2 net] bnxt_en: fix DMA mapping length for padded small packets , by netdev-bot+sashiko Re: [REGRESSION] Commit 447cbe95ebb9 causes IOMMU DMA faults on macvlan/vlan with bnxt_en , by Sasha Levin Re: [PATCH v2 net] bnxt_en: fix DMA mapping length for padded small packets , by Michael Chan Regzbot command history: note: "[PATCH net] vlan: do not insert the vlan header in vlan_dev_hard_header()" contains a 'Fixes:' tag for the culprit of this regression , by Eric Dumazet relate: https://lore.kernel.org/netdev/20261007051747.455273-1-edumazet@kernel.org/ [PATCH v3 net] bnxt_en: fix DMA mapping length for padded small packets [implicit due to Link/Closes tag] , by Eric Dumazet note: https://lore.kernel.org/netdev/20261004122616.56714cbd@nargothrond/ Re: [RFC net v4 0/4] bnxt_en: Make RING FREE more robust [implicit due to link] , by anmory note: https://lore.kernel.org/netdev/20261006042153.199444-1-edumazet@kernel.org/ Re: [RFC net v4 0/4] bnxt_en: Make RING FREE more robust [implicit due to link] , by anmory note: https://lore.kernel.org/netdev/20261004122616.56714cbd@nargothrond/ Re: [RFC net v4 0/4] bnxt_en: Make RING FREE more robust [implicit due to link] , by Joe Damato note: https://lore.kernel.org/netdev/20261006042153.199444-1-edumazet@kernel.org/ Re: [RFC net v4 0/4] bnxt_en: Make RING FREE more robust [implicit due to link] , by Joe Damato note: https://lore.kernel.org/all/20261006042153.199444-1-edumazet@kernel.org/ Re: [REGRESSION][BISECTED] r8169: TX stall with checksum offload on VLAN frames with inline tag (REORDER_HDR off) since 1517d1996b52 [implicit due to link] , by Thorsten Leemhuis note: https://lore.kernel.org/all/20261004122616.56714cbd@nargothrond/ Re: [REGRESSION][BISECTED] r8169: TX stall with checksum offload on VLAN frames with inline tag (REORDER_HDR off) since 1517d1996b52 [implicit due to link] , by Thorsten Leemhuis relate: https://lore.kernel.org/netdev/20261006042153.199444-1-edumazet@kernel.org/ [PATCH v2 net] bnxt_en: fix DMA mapping length for padded small packets [implicit due to Link/Closes tag] , by Eric Dumazet relate: https://lore.kernel.org/netdev/179123498942.434549.13440734253618262332@kernel.org/ Re: [PATCH net] bnxt_en: fix DMA mapping length for padded small packets [implicit due to Link/Closes tag] , by netdev-bot+sashiko summary: vlan: IOMMU DMA faults on macvlan/vlan with bnxt_en , by Thorsten Leemhuis introduced: 447cbe95ebb9 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 447cbe95ebb9 ("vlan: fix skb_under_panic and races when toggling HW VLAN offload") Reported-by: Stefan Fleischmann <sfle@kth.se> Link: https://lore.kernel.org/r/20261004122616.56714cbd@nargothrond/
9e4a3ec3411b (v7.3-rc4)	*x86: mm: protection fault when using a boot-time function tracer and a filter* by Mikhail Gavrilov Earliest & latest activity: & . Noteworthy: [fix incoming]. Fix incoming: 1f1076ea64b9 ("mm: don't schedule deferred kernel page table freeing while booting") Latest five known activities: 1f1076ea64b9, the fix specified through '#regzbot fix:' earlier landed in next , by Mikhail Gavrilov 217dcb6dbc5f, the fix specified through '#regzbot fix:' earlier landed in next , by Mikhail Gavrilov 15629d8d32f7, the fix specified through '#regzbot fix:' earlier landed in next , by Mikhail Gavrilov 9bf8c82d45c9, the fix specified through '#regzbot fix:' earlier landed in next , by Mikhail Gavrilov c131bc1737a8, the fix specified through '#regzbot fix:' earlier landed in next , by Mikhail Gavrilov Regzbot command history: note: "[merged mm-hotfixes-stable] mm-dont-schedule-deferred-kernel-page-table-freeing-while-booting.patch removed from -mm tree" contains a 'Fixes:' tag for the culprit of this regression , by Andrew Morton note: 'fix' commit '1f1076ea64b9' now in 'next' , by Mikhail Gavrilov note: 'fix' commit '217dcb6dbc5f' now in 'next' , by Mikhail Gavrilov note: 'fix' commit '15629d8d32f7' now in 'next' , by Mikhail Gavrilov note: 'fix' commit '9bf8c82d45c9' now in 'next' , by Mikhail Gavrilov note: 'fix' commit 'c131bc1737a8' now in 'next' , by Mikhail Gavrilov note: 'fix' commit '5087b8da514c' now in 'next' , by Mikhail Gavrilov note: 'fix' commit 'eb84f18caeaf' now in 'next' , by Mikhail Gavrilov fix: mm: don't schedule deferred kernel page table freeing while booting , by Thorsten Leemhuis summary: x86: mm: protection fault when using a boot-time function tracer and a filter , by Thorsten Leemhuis introduced: 9e4a3ec3411b , by Thorsten Leemhuis note: "[PATCH] mm: don't defer freeing kernel page tables while booting" contains a 'Fixes:' tag for the culprit of this regression , by Mikhail Gavrilov
97d34aa65c29 (v7.3-rc2)	*secretmem: SIGBUS on memfd_secret() pages while perf record runs* by Ameer Hamza Earliest & latest activity: & . Latest five known activities: Re: [REGRESSION] secretmem: SIGBUS on memfd_secret() pages while perf record runs , by David Hildenbrand (Arm) Re: [REGRESSION] secretmem: SIGBUS on memfd_secret() pages while perf record runs , by Sasha Levin Re: [REGRESSION] secretmem: SIGBUS on memfd_secret() pages while perf record runs , by Sasha Levin Re: [REGRESSION] secretmem: SIGBUS on memfd_secret() pages while perf record runs , by Ameer Hamza Re: [REGRESSION] secretmem: SIGBUS on memfd_secret() pages while perf record runs , by Ameer Hamza Regzbot command history: note: "[PATCH] perf/core: track the perf mlock gift separately" contains a 'Fixes:' tag for the culprit of this regression , by Lorenzo Stoakes (ARM) introduced: 97d34aa65c29 , by Ameer Hamza When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 97d34aa65c29 ("mm/secretmem: properly account locked pages") Reported-by: Ameer Hamza <ameer.hamza@truenas.com> Link: https://lore.kernel.org/r/20261002175651.811343-1-ameer.hamza@truenas.com/
980084de4d9b (v7.3-rc1)	*Bluetooth: btusb: bt stopped working due to missing firmware* by Thorsten Leemhuis Earliest & latest activity: . All known activities: Re: Thread for updating minor properties of tracked regressions [consider ignoring it!] , by Thorsten Leemhuis Regzbot command history: summary: Bluetooth: btusb: bt stopped working due to missing firmware , by Thorsten Leemhuis introduced: 980084de4d9b25 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 980084de4d9b ("Bluetooth: btusb: Add ASUS USB-BT540 for Realtek 8761CU") Reported-by: Thorsten Leemhuis <regressions@leemhuis.info> Link: https://lore.kernel.org/r/d81824c1-f802-4488-960d-6545cbe51f6e@leemhuis.info/
022eb347ff3a (v7.3-rc1)	*HID: logitech: hi-res scroll broken after supend and resume* by Roman Stingler Earliest & latest activity: & . Noteworthy: [1], [2], [3], [4], [fix incoming]. [1]: [PATCH 0/2] HID: logitech-hidpp: fix Bolt hi-res wheel handling [implicit due to Link/Closes tag] , by Erik Håkansson (monitored) [2]: [PATCH] Revert "HID: logitech: add Bolt receiver support for Logitech HID++ devices" [implicit due to Link/Closes tag] , by Benjamin Tissoires (monitored) [3]: [PATCH] HID: logitech-hidpp: do not overwrite the device's hi-res wheel mode [implicit due to Link/Closes tag] , by Roman Stingler (monitored) [4]: [PATCH v2] HID: logitech-hidpp: do not overwrite the device's hi-res wheel mode [implicit due to Link/Closes tag] , by Roman Stingler (monitored) Fix incoming: perf/core: track the perf mlock gift separately Latest five known activities: 3fabd8ec206b, the fix specified through '#regzbot fix:' earlier landed in mainline , by Benjamin Tissoires Re: [PATCH] HID: logitech-hidpp: do not overwrite the device's hi-res wheel mode , by Erik Håkansson Re: [PATCH] HID: logitech-hidpp: do not overwrite the device's hi-res wheel mode , by johannes.goede Re: [PATCH] HID: logitech-hidpp: do not overwrite the device's hi-res wheel mode , by johannes.goede [PATCH v2] HID: logitech-hidpp: do not overwrite the device's hi-res wheel mode , by Roman Stingler; contains a signed-off patch Regzbot command history: fix: perf/core: track the perf mlock gift separately , by Thorsten Leemhuis fix: 3fabd8ec206bd4 , by Thorsten Leemhuis fixed: 'fix' commit '3fabd8ec206b' now in 'mainline' , by Benjamin Tissoires relate: https://lore.kernel.org/lkml/20260923190128.10394-1-roman.stingler@gmail.com/ [PATCH v2] HID: logitech-hidpp: do not overwrite the device's hi-res wheel mode [implicit due to Link/Closes tag] , by Roman Stingler relate: https://lore.kernel.org/lkml/20260923181203.422097-1-roman.stingler@gmail.com/ [PATCH] HID: logitech-hidpp: do not overwrite the device's hi-res wheel mode [implicit due to Link/Closes tag] , by Roman Stingler relate: https://lore.kernel.org/lkml/20260923-revert-bolt-v1-1-52c2ef6f614d@kernel.org/ [PATCH] Revert "HID: logitech: add Bolt receiver support for Logitech HID++ devices" [implicit due to Link/Closes tag] , by Benjamin Tissoires relate: https://lore.kernel.org/lkml/20260922-feature-bolt-fix-v1-0-63b0fa8da0d3@gmail.com/ [PATCH 0/2] HID: logitech-hidpp: fix Bolt hi-res wheel handling [implicit due to Link/Closes tag] , by Erik Håkansson note: https://lore.kernel.org/linux-input/20260920094508.39682-1-roman.stingler@gmail.com/ Re: [PATCH] HID: logitech-hidpp: fix hi-res scroll for Bolt-connected MX Master [implicit due to link] , by erikhakan summary: HID: logitech: hi-res scroll broken after supend and resume , by Thorsten Leemhuis introduced: 022eb347ff3a48281e7e69c3addcb11bf24afa53 , by Roman Stingler
a637a140ab86 (v7.3-rc1)	*Single-frame scanout corruption on DCN32 at 120 Hz, 90x more frequent since a637a140ab86* by Mikhail Gavrilov and Mikhail Gavrilov Earliest & latest activity: & . Latest five known activities: drm/amd, issue 5714: new comment (#1) , by Josh Kasten Re: [REGRESSION 7.3] drm/amd/display: single-frame scanout corruption on DCN32 at 120 Hz since a637a140ab86 , by Mikhail Gavrilov [via dup] Re: [REGRESSION 7.3] drm/amd/display: single-frame scanout corruption on DCN32 at 120 Hz since a637a140ab86 , by Mikhail Gavrilov [via dup] drm/amd, issue 5714: new comment (#1) , by Mikhail Gavrilov [REGRESSION 7.3] drm/amd/display: single-frame scanout corruption on DCN32 at 120 Hz since a637a140ab86 , by Mikhail Gavrilov [via dup] Regzbot command history: note: https://gitlab.freedesktop.org/drm/amd/-/work_items/5714 Re: [REGRESSION 7.3] drm/amd/display: single-frame scanout corruption on DCN32 at 120 Hz since a637a140ab86 [implicit due to link] , by Mikhail Gavrilov resolve: inconclusive: looks like this wasn't a regressions , by Thorsten Leemhuis note: https://gitlab.freedesktop.org/drm/amd/-/work_items/5714 Re: [REGRESSION 7.3] drm/amd/display: single-frame scanout corruption on DCN32 at 120 Hz since a637a140ab86 [implicit due to link] , by Mikhail Gavrilov duplicate: https://lore.kernel.org/lkml/20260829010525.29935-1-mikhail.v.gavrilov@gmail.com/ [implicit via duplicate] , by Thorsten Leemhuis introduced: a637a140ab86 [implicit via duplicate] , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: a637a140ab86 ("drm/amd/display: Allocate DCN32/1 dmub memory to GTT") Reported-by: Mikhail Gavrilov <Mikhail> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/5714 Reported-by: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com> Link: https://lore.kernel.org/r/20260829010525.29935-1-mikhail.v.gavrilov@gmail.com/
143755bdabaa (v7.3-rc4)	*dma-buf: drm/msm hardware video decode broken* by Jianfeng Liu Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH] Revert "dma-buf: Make DMABUF_DEBUG default to y on DEBUG_KERNEL kernels" , by Jianfeng Liu (monitored) Fix incoming: Revert "dma-buf: Make DMABUF_DEBUG default to y on DEBUG_KERNEL kernels" Latest five known activities: Re: [PATCH] Revert "dma-buf: Make DMABUF_DEBUG default to y on DEBUG_KERNEL kernels" , by Karl Mehltretter Re: [PATCH] Revert "dma-buf: Make DMABUF_DEBUG default to y on DEBUG_KERNEL kernels" , by Karl Mehltretter Re: [PATCH] Revert "dma-buf: Make DMABUF_DEBUG default to y on DEBUG_KERNEL kernels" , by Rob Clark Re: [PATCH] Revert "dma-buf: Make DMABUF_DEBUG default to y on DEBUG_KERNEL kernels" , by Rob Clark Re: [PATCH] Revert "dma-buf: Make DMABUF_DEBUG default to y on DEBUG_KERNEL kernels" , by Christian König Regzbot command history: note: https://lore.kernel.org/r/20260926022026.10539-1-liujianfeng1994@gmail.com [RFC PATCH 0/3] dma-buf: warn-only mode for DMABUF_DEBUG [implicit due to link] , by Karl Mehltretter note: https://lore.kernel.org/r/20260923074256.9357-1-liujianfeng1994@gmail.com [RFC PATCH 0/3] dma-buf: warn-only mode for DMABUF_DEBUG [implicit due to link] , by Karl Mehltretter relate: https://lore.kernel.org/all/20260926022026.10539-1-liujianfeng1994@gmail.com/ , by Thorsten Leemhuis fix: Revert "dma-buf: Make DMABUF_DEBUG default to y on DEBUG_KERNEL kernels" , by Thorsten Leemhuis relate: https://lore.kernel.org/lkml/20260926022026.10539-1-liujianfeng1994@gmail.com/ [PATCH] Revert "dma-buf: Make DMABUF_DEBUG default to y on DEBUG_KERNEL kernels" [implicit due to Link/Closes tag] , by Jianfeng Liu summary: dma-buf: drm/msm hardware video decode broken , by Thorsten Leemhuis introduced: 143755bdabaa9 , by Thorsten Leemhuis note: "[RFC PATCH v1 1/2] dma-buf: keep DMABUF_DEBUG off by default" contains a 'Fixes:' tag for the culprit of this regression , by Jianfeng Liu
current cycle (v7.2.. aka v7.3-rc), unknown culprit
none known by regzbot
previous cycle (v7.1..v7.2), culprit identified, with activity in the past three months
7e5760f084d0 (v7.2-rc1)	*drm: amdgpu: various problems wrt to outputs, apparently already fixed in 7.3* by Michał Górny, Prslc, and Bjørnar Hansen Earliest & latest activity: & . Noteworthy: [1], [patch (SOB)]. [1]: [PATCH 7.2.y] drm/amd/display: keep HDMI 4:2:0-only modes and automatic 4:4:4 [implicit due to Link/Closes tag] , by Miguel Mesa (monitored) Latest patch: [PATCH 7.2.y] drm/amd/display: keep HDMI 4:2:0-only modes and automatic 4:4:4 , by Miguel Mesa; signed-off-by present Latest five known activities: Re: [PATCH 7.2.y] drm/amd/display: keep HDMI 4:2:0-only modes and automatic 4:4:4 , by Mario Limonciello Re: [PATCH 7.2.y] drm/amd/display: keep HDMI 4:2:0-only modes and automatic 4:4:4 , by Greg KH drm/amd, issue 5760: new comment (#7) , by miguelmesaevolutia [PATCH 7.2.y] drm/amd/display: keep HDMI 4:2:0-only modes and automatic 4:4:4 , by Miguel Mesa; contains a signed-off patch drm/amd, issue 5760: new comment (#6) , by Mario Limonciello Regzbot command history: relate: https://lore.kernel.org/stable/20261003131523.1502250-1-miguel@miguelmesa.com/ [PATCH 7.2.y] drm/amd/display: keep HDMI 4:2:0-only modes and automatic 4:4:4 [implicit due to Link/Closes tag] , by Miguel Mesa summary: drm: amdgpu: various problems wrt to outputs, apparently already fixed in 7.3 , by Thorsten Leemhuis duplicate: https://gitlab.freedesktop.org/drm/amd/-/work_items/5777 , by Thorsten Leemhuis duplicate: https://gitlab.freedesktop.org/drm/amd/-/work_items/5786 , by Thorsten Leemhuis summary: drm: amdgpu: saturation control stopped working on TV connected via HDMI , by Thorsten Leemhuis introduced: 7e5760f084d06ca57e46e4dbf7ef08f03f857be8 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 7e5760f084d0 ("drm/amd/display: add HDMI 2.1 Compliance Support") Reported-by: Bjørnar Hansen <habjo> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/5786 Reported-by: Michał Górny <mgorny> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/5760 Reported-by: Prslc <Prslc> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/5777
f0866517be93 (v7.2-rc1)	*HID: logitech-hidpp: hi-res wheel scrolling over Lightspeed receiver (G903) broken* by Frantisek Musil Earliest & latest activity: & . Latest five known activities: Re: [REGRESSION] HID: logitech-hidpp: commit f0866517be93 breaks hi-res wheel scrolling over Lightspeed receiver (G903) , by Lauri Saurus Re: [REGRESSION] HID: logitech-hidpp: commit f0866517be93 breaks hi-res wheel scrolling over Lightspeed receiver (G903) , by Frantisek Musil Re: [REGRESSION] HID: logitech-hidpp: commit f0866517be93 breaks hi-res wheel scrolling over Lightspeed receiver (G903) , by Lauri Saurus Re: [REGRESSION] HID: logitech-hidpp: commit f0866517be93 breaks hi-res wheel scrolling over Lightspeed receiver (G903) , by Frantisek Musil Re: [REGRESSION] HID: logitech-hidpp: commit f0866517be93 breaks hi-res wheel scrolling over Lightspeed receiver (G903) , by Lauri Saurus Regzbot command history: summary: HID: logitech-hidpp: hi-res wheel scrolling over Lightspeed receiver (G903) broken , by Thorsten Leemhuis introduced: f0866517be9345 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: f0866517be93 ("HID: logitech-hidpp: sync wheel multiplier on wheel mode changes") Reported-by: Frantisek Musil <lister@gamesplit.cz> Link: https://lore.kernel.org/r/77888c45-0b12-4973-a9c8-9aa5d70eb1b5@gamesplit.cz/
cf6444c3e1bb (v7.2-rc1)	*tick/sched: /proc/stat idle time exceeds wall time since v7.2* by Stian Halseth Earliest & latest activity: & . Noteworthy: [1], [patch (SOB)]. [1]: [PATCH v2] sched/cputime: Don't account idle time twice after dyntick-idle [implicit due to Link/Closes tag] , by Stian Halseth (monitored) Latest patch: [PATCH v2] sched/cputime: Don't account idle time twice after dyntick-idle , by Stian Halseth; signed-off-by present Earlier patches: 1 Latest five known activities: Re: [PATCH v2] sched/cputime: Don't account idle time twice after dyntick-idle , by Stian Halseth Re: [PATCH v2] sched/cputime: Don't account idle time twice after dyntick-idle , by Stian Halseth Re: [PATCH v2] sched/cputime: Don't account idle time twice after dyntick-idle , by Frederic Weisbecker Re: [PATCH v2] sched/cputime: Don't account idle time twice after dyntick-idle , by Stian Halseth Re: [PATCH v2] sched/cputime: Don't account idle time twice after dyntick-idle , by Frederic Weisbecker Regzbot command history: relate: https://lore.kernel.org/lkml/20261005194010.168299-1-stian@itx.no/ [PATCH v2] sched/cputime: Don't account idle time twice after dyntick-idle [implicit due to Link/Closes tag] , by Stian Halseth introduced: cf6444c3e1bb7 , by Stian Halseth When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: cf6444c3e1bb ("tick/sched: Unify idle cputime accounting") Reported-by: Stian Halseth <stian@itx.no> Link: https://lore.kernel.org/r/20261004142724.3896396-1-stian@itx.no/
70b7e3526c53 (v7.2-rc1)	*reads and writes hang if NFS server has v3 disabled* by Benji Wiebe Earliest & latest activity: . Noteworthy: [fix incoming]. Fix incoming: 5d28b2c920d9 ("nfsd: don't offer flexfiles layouts when NFSv3 isn't being served") All known activities: 5d28b2c920d9, the fix specified through '#regzbot fix:' earlier landed in next , by Jeff Layton Regzbot command history: note: 'fix' commit '5d28b2c920d9' now in 'next' , by Jeff Layton fix: nfsd: don't offer flexfiles layouts when NFSv3 isn't being served , by Thorsten Leemhuis introduced: 70b7e3526c53d9dd7caccdbeff5b0485640d8cf1 , by Benji Wiebe
bee25f97ad24 (v7.2-rc1)	*powerpc: Power9 pseries boot hang* by Venkat Rao Bagalkote Earliest & latest activity: & . Noteworthy: [1], [2], [3], [4], [patch (SOB)]. [1]: [PATCH] powerpc/kasan: require memintrinsic prefix support for KASAN [implicit due to Link/Closes tag] , by Mukesh Kumar Chaurasiya (IBM) (monitored) [2]: [PATCH V2] powerpc/kasan: require memintrinsic prefix support for KASAN [implicit due to Link/Closes tag] , by Mukesh Kumar Chaurasiya (IBM) (monitored) [3]: [PATCH V3] powerpc/kasan: require memintrinsic prefix support for KASAN [implicit due to Link/Closes tag] , by Mukesh Kumar Chaurasiya (IBM) (monitored) [4]: [PATCH V4] powerpc/kasan: fix r2 corruption in mem() on GENERIC_ENTRY with old compilers [implicit due to Link/Closes tag]* , by Mukesh Kumar Chaurasiya (IBM) (monitored) Latest patch: [PATCH V4] powerpc/kasan: fix r2 corruption in mem() on GENERIC_ENTRY with old compilers , by Mukesh Kumar Chaurasiya (IBM); signed-off-by present Earlier patches: 1, 2, 3, 4, 5 Latest five known activities: [PATCH V4] powerpc/kasan: fix r2 corruption in mem() on GENERIC_ENTRY with old compilers , by Mukesh Kumar Chaurasiya (IBM); contains a signed-off patch Re: [PATCH V3] powerpc/kasan: require memintrinsic prefix support for KASAN , by Mukesh Kumar Chaurasiya Re: [PATCH V3] powerpc/kasan: require memintrinsic prefix support for KASAN , by Andrey Ryabinin; contains a simple patch Re: [PATCH V3] powerpc/kasan: require memintrinsic prefix support for KASAN , by Mukesh Kumar Chaurasiya Re: [PATCH V3] powerpc/kasan: require memintrinsic prefix support for KASAN , by Christophe Leroy (CS GROUP) Regzbot command history: relate: https://lore.kernel.org/lkml/20261003094006.3404731-1-mkchauras@gmail.com/ [PATCH V4] powerpc/kasan: fix r2 corruption in mem() on GENERIC_ENTRY with old compilers [implicit due to Link/Closes tag] , by Mukesh Kumar Chaurasiya (IBM) note: '1a2063f06238' in 'stable/linux-7.2.y' contains a 'Fixes:' tag for the culprit of this regression* , by Aboorva Devarajan note: 'c8e80c19c3b9' in 'stable/linux-7.2.y' contains a 'Fixes:' tag for the culprit of this regression , by Ritesh Harjani (IBM) relate: https://lore.kernel.org/lkml/20260915100938.1337401-1-mkchauras@gmail.com/ [PATCH V3] powerpc/kasan: require memintrinsic prefix support for KASAN [implicit due to Link/Closes tag] , by Mukesh Kumar Chaurasiya (IBM) note: '19b54740e2e1' in 'stable/linux-7.2.y' contains a 'Fixes:' tag for the culprit of this regression , by Mukesh Kumar Chaurasiya (IBM) note: '11ae2e1dc583' in 'mainline' contains a 'Fixes:' tag for the culprit of this regression , by Aboorva Devarajan relate: https://lore.kernel.org/lkml/20260911180536.3234640-2-mkchauras@gmail.com/ [PATCH V2] powerpc/kasan: require memintrinsic prefix support for KASAN [implicit due to Link/Closes tag] , by Mukesh Kumar Chaurasiya (IBM) note: '11ae2e1dc583' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Aboorva Devarajan note: 'c2549d749539' in 'mainline' contains a 'Fixes:' tag for the culprit of this regression , by Ritesh Harjani (IBM) relate: https://lore.kernel.org/lkml/20260908064948.999530-1-mkchauras@gmail.com/ [PATCH] powerpc/kasan: require memintrinsic prefix support for KASAN [implicit due to Link/Closes tag] , by Mukesh Kumar Chaurasiya (IBM) note: 'c2549d749539' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Ritesh Harjani (IBM) note: '69cb2be898be' in 'mainline' contains a 'Fixes:' tag for the culprit of this regression , by Mukesh Kumar Chaurasiya (IBM) summary: powerpc: Power9 pseries boot hang , by Thorsten Leemhuis introduced: bee25f97ad24 , by Thorsten Leemhuis note: '69cb2be898be' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Mukesh Kumar Chaurasiya (IBM) note: '334f3f6d7a16' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Shrikanth Hegde note: '4e1187e12de4' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Mukesh Kumar Chaurasiya (IBM) note: 'bddf7540099b' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Mukesh Kumar Chaurasiya (IBM) When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: bee25f97ad24 ("powerpc: Enable GENERIC_ENTRY feature") Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com> Link: https://lore.kernel.org/r/96dae110-f79b-4e54-8a9b-514369019b5d@linux.ibm.com/
87a6f2fa6e6c (v7.2-rc1)	*ALSA: usb-audio: Audient EVO4 hardware volume control broken* by Faaris Ansari Earliest & latest activity: & . Noteworthy: [patch]. Latest patch: Re: [REGRESSION] Audient EVO4 hardware volume control now requires quirk , by Takashi Iwai; simple patch Earlier patches: 1 Latest five known activities: Re: [REGRESSION] Audient EVO4 hardware volume control now requires quirk , by Sasha Levin Re: [REGRESSION] Audient EVO4 hardware volume control now requires quirk , by Sasha Levin Re: [REGRESSION] Audient EVO4 hardware volume control now requires quirk , by Takashi Iwai Re: [REGRESSION] Audient EVO4 hardware volume control now requires quirk , by Sasha Levin Re: [REGRESSION] Audient EVO4 hardware volume control now requires quirk , by Christian Ruppert Regzbot command history: note: 'a154f7b9f197' in 'mainline' contains a 'Fixes:' tag for the culprit of this regression , by Takashi Iwai note: 'a154f7b9f197' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Takashi Iwai summary: ALSA: usb-audio: Audient EVO4 hardware volume control broken , by Thorsten Leemhuis introduced: 87a6f2fa6e6c , by Thorsten Leemhuis note: https://lore.kernel.org/regressions/CANBVYRCL=8QdLxGg4S6qrahrFtwJxhv-aSGpW7-1S=+iOe4ZGA@mail.gmail.com/T/#mfc03d59d61c4c46165dedde6dc23e26aff5f697d Re: [PATCH 0/4] ALSA: usb-audio: Demote the severity of sticky GET_CUR [implicit due to link] , by Faaris Ansari note: https://lore.kernel.org/regressions/CANBVYRCL=8QdLxGg4S6qrahrFtwJxhv-aSGpW7-1S=+iOe4ZGA@mail.gmail.com/ Re: [PATCH 0/3] Add Audient EVO4 support [implicit due to link] , by Faaris Ansari introduced: v7.1.13..v7.2.5 , by Faaris Ansari When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 87a6f2fa6e6c ("ALSA: usb-audio: Propagate write errors in generic mixer put callbacks") Reported-by: Faaris Ansari <faarisansari@googlemail.com> Link: https://lore.kernel.org/r/CANBVYRCL=8QdLxGg4S6qrahrFtwJxhv-aSGpW7-1S=%2BiOe4ZGA@mail.gmail.com/
b8eeeca55456 (v7.2-rc1)	*clocksource/drivers/timer-ti-dm: OpenPandora (OMAP3) fails to boot* by H. Nikolaus Schaller Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH] clocksource/drivers/timer-ti-dm: Register clocksource/event only for am654 , by Markus Schneider-Pargmann (TI) (monitored) Fix incoming: clocksource/drivers/timer-ti-dm: Register clocksource/event only for am654 Latest five known activities: Re: [PATCH] clocksource/drivers/timer-ti-dm: Register clocksource/event only for am654 , by Daniel Lezcano Re: [PATCH] clocksource/drivers/timer-ti-dm: Register clocksource/event only for am654 , by Markus Schneider-Pargmann Re: [PATCH] clocksource/drivers/timer-ti-dm: Register clocksource/event only for am654 , by Markus Schneider-Pargmann Re: [PATCH] clocksource/drivers/timer-ti-dm: Register clocksource/event only for am654 , by Kevin Hilman Re: [PATCH] clocksource/drivers/timer-ti-dm: Register clocksource/event only for am654 , by H. Nikolaus Schaller Regzbot command history: relate: https://lore.kernel.org/all/20260828-v7-3-next-topic-ti-timer-dm-clocksource-omap-fix-v1-1-85f0e4dc6f9f@baylibre.com/ , by Thorsten Leemhuis fix: clocksource/drivers/timer-ti-dm: Register clocksource/event only for am654 , by Thorsten Leemhuis summary: clocksource/drivers/timer-ti-dm: OpenPandora (OMAP3) fails to boot , by Thorsten Leemhuis introduced: b8eeeca5545659 , by Thorsten Leemhuis note: "[PATCH] clocksource/drivers/timer-ti-dm: Register clocksource/event only for am654" contains a 'Fixes:' tag for the culprit of this regression , by Markus Schneider-Pargmann (TI)
578294b8b60d (v7.2-rc1)	*e1000e: heavy packet loss on Lenovo ThinkPad P14s Gen 5 (I219-LM, Meteor Lake) after K1 re-enable; fixed by disable-k1* by Javier Herrera Earliest & latest activity: & . Noteworthy: [1], [2], [patch (SOB)]. [1]: [PATCH iwl-net] e1000e: add system to disable K1 list [implicit due to Link/Closes tag] , by Tony Nguyen (monitored) [2]: [PATCH net 6/6] e1000e: add system to disable K1 list [implicit due to Link/Closes tag] , by Tony Nguyen (monitored) Latest patch: [PATCH net 6/6] e1000e: add system to disable K1 list , by Tony Nguyen; signed-off-by present Earlier patches: 1 Latest five known activities: [PATCH net 6/6] e1000e: add system to disable K1 list , by Tony Nguyen; contains a signed-off patch RE: [PATCH iwl-net] e1000e: add system to disable K1 list , by Loktionov, Aleksandr [PATCH iwl-net] e1000e: add system to disable K1 list , by Tony Nguyen; contains a signed-off patch Re: [REGRESSION] e1000e: heavy packet loss on Lenovo ThinkPad P14s Gen 5 (I219-LM, Meteor Lake) after K1 re-enable; fixed by disable-k1 , by Tony Nguyen Re: [REGRESSION] e1000e: heavy packet loss on Lenovo ThinkPad P14s Gen 5 (I219-LM, Meteor Lake) after K1 re-enable; fixed by disable-k1 , by Thorsten Leemhuis Regzbot command history: note: https://lore.kernel.org/all/20261001222443.3500206-7-anthony.l.nguyen@intel.com/ Re: e1000e: I219-V RX CRC errors on ThinkPad P14s Gen6 Intel; disabling K1 restores throughput [implicit due to link] , by Paul Menzel relate: https://lore.kernel.org/netdev/20261001222443.3500206-7-anthony.l.nguyen@intel.com/ [PATCH net 6/6] e1000e: add system to disable K1 list [implicit due to Link/Closes tag] , by Tony Nguyen relate: https://lore.kernel.org/intel-wired-lan/20260925192047.3308768-1-anthony.l.nguyen@intel.com/ [PATCH iwl-net] e1000e: add system to disable K1 list [implicit due to Link/Closes tag] , by Tony Nguyen introduced: 578294b8b60d , by Javier Herrera When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 578294b8b60d ("e1000e: Reconfigure PLL clock gate timeout and re-enable K1 on Meteor Lake") Reported-by: Javier Herrera <javier.herrera@afronta.com> Link: https://lore.kernel.org/r/CAKRuCQLWEcci9hPgNUmvq44Bd2H30T5_vP=exMjsknXMN5Yh9A@mail.gmail.com/
7e5760f084d0 (v7.2-rc1)	*drm: amdgpu: HDMI 4K60 black screen, RGB chosen for a YCbCr 4:2:0-only sink* by Curtis Vogt Earliest & latest activity: & . Latest five known activities: drm/amd, issue 5720: new comment (#7) , by John Audia drm/amd, issue 5720: new comment (#6) , by John Audia drm/amd, issue 5720: new comment (#5) , by Daniel Byers drm/amd, issue 5720: new comment (#4) , by Jan Alexander Steffens drm/amd, issue 5720: new comment (#3) , by John Audia Regzbot command history: summary: drm: amdgpu: HDMI 4K60 black screen, RGB chosen for a YCbCr 4:2:0-only sink , by Thorsten Leemhuis introduced: 7e5760f084d0 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 7e5760f084d0 ("drm/amd/display: add HDMI 2.1 Compliance Support") Reported-by: Curtis Vogt <omus> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/5720
dd0c03d68522 (v7.2-rc1)	*qcom/qcom-msm8960-samsung-expressatt: SSH over USB no longer works* by Rudraksha Gupta Earliest & latest activity: & . All known activities: Re: [REGRESSION] qcom/qcom-msm8960-samsung-expressatt: SSH over USB no longer works , by Rudraksha Gupta qcom/qcom-msm8960-samsung-expressatt: SSH over USB no longer works , by Rudraksha Gupta Regzbot command history: introduced: dd0c03d68522 , by Rudraksha Gupta When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: dd0c03d68522 ("usb: chipidea: udc: support dynamic gadget add/remove") Reported-by: Rudraksha Gupta <guptarud@gmail.com> Link: https://lore.kernel.org/r/8e659c4f-723b-4241-9c2b-8ea42c6c3600@gmail.com/
5ead2063611a (v7.2-rc1)	*Bluetooth: btusb: RTL8761BU 0bda:a728 broken due to BROKEN_EXT_SCAN quirk* by Andy Tsvetinskiy Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH] Bluetooth: btusb: drop BROKEN_EXT_SCAN quirk for 0bda:a728 , by Junjie Cao (monitored) Fix incoming: fdd5964bd389 ("Bluetooth: btusb: drop BROKEN_EXT_SCAN quirk for 0bda:a728") Latest five known activities: Commit fdd5964bd389 in next , by Junjie Cao Re: [PATCH] Bluetooth: btusb: drop BROKEN_EXT_SCAN quirk for 0bda:a728 , by patchwork-bot+bluetooth Re: [REGRESSION] RTL8761BU 0bda:a728: removing BROKEN_EXT_SCAN fixes 0x200c timeout , by Thorsten Leemhuis Re: [REGRESSION] RTL8761BU 0bda:a728: removing BROKEN_EXT_SCAN fixes 0x200c timeout , by Andy Tsvetinskiy Re: [REGRESSION] RTL8761BU 0bda:a728: removing BROKEN_EXT_SCAN fixes 0x200c timeout , by Thorsten Leemhuis Regzbot command history: fix: fdd5964bd389 in next referred to this regression , by Junjie Cao relate: https://lore.kernel.org/all/20260920020227.709800-1-junjie.cao@intel.com/ , by Thorsten Leemhuis summary: Bluetooth: btusb: RTL8761BU 0bda:a728 broken due to BROKEN_EXT_SCAN quirk , by Thorsten Leemhuis introduced: 5ead2063611a , by Thorsten Leemhuis note: "[PATCH] Bluetooth: btusb: drop BROKEN_EXT_SCAN quirk for 0bda:a728" contains a 'Fixes:' tag for the culprit of this regression , by Junjie Cao note: 'f609eac02d11' in 'stable/linux-6.18.y' contains a 'Fixes:' tag for the culprit of this regression , by Junjie Cao note: '9fe52fd63e5b' in 'stable/linux-7.2.y' contains a 'Fixes:' tag for the culprit of this regression , by Junjie Cao note: '0c9d2588a514' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Junjie Cao note: 'ca0583c24661' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Junjie Cao
72780f796468 (v7.2-rc1)	*PCI: booting takes longer* by Edward and Andreas Wild Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH v3] PCI: Skip Target Speed quirk on clamped ports with no link , by Andreas Wild (monitored) Fix incoming: ff8a969f7dc8 ("PCI: Skip Target Speed quirk on clamped ports with no link") Latest five known activities: Re: [PATCH v3] PCI: Skip Target Speed quirk on clamped ports with no link , by Andreas Wild [via dup] Re: [PATCH v3] PCI: Skip Target Speed quirk on clamped ports with no link , by Thorsten Leemhuis [via dup] bugzilla.kernel.org, issue 221801: new comment (#25) , by Edward bugzilla.kernel.org, issue 221801: new comment (#24) , by The Linux kernel's regression tracker (Thorsten Leemhuis) bugzilla.kernel.org, issue 221801: new comment (#23) , by Edward Regzbot command history: note: 'fix' commit 'ff8a969f7dc8' now in 'next' , by Maciej W. Rozycki note: https://bugzilla.kernel.org/show_bug.cgi?id=221801#c13. Re: [PATCH v3] PCI: Skip Target Speed quirk on clamped ports with no link [implicit due to link] , by Bjorn Helgaas note: https://bugzilla.kernel.org/show_bug.cgi?id=221801 Re: [PATCH v3] PCI: Skip Target Speed quirk on clamped ports with no link [implicit due to link] , by Bjorn Helgaas note: https://bugzilla.kernel.org/show_bug.cgi?id=221801#c14 Re: [REGRESSION] PCIe/qcom: on-board WCN7850 link stuck in Polling on X1E80100 (Surface Pro 11) [implicit due to link] , by Thorsten Leemhuis note: https://bugzilla.kernel.org/show_bug.cgi?id=221801 Quick regression status pre 7.2 final/-rc8 [implicit due to link] , by Thorsten Leemhuis note: https://bugzilla.kernel.org/show_bug.cgi?id=221801 Re: [PATCH v3] PCI: Skip Target Speed quirk on clamped ports with no link [implicit due to link] , by Aoxtj relate: https://lore.kernel.org/all/20260801201244.4421-1-andiwild@gmail.com/ , by Thorsten Leemhuis fix: PCI: Skip Target Speed quirk on clamped ports with no link , by Thorsten Leemhuis duplicate: https://lore.kernel.org/all/20260801201244.4421-1-andiwild@gmail.com/ , by Thorsten Leemhuis summary: PCI: booting takes longer , by Thorsten Leemhuis note: https://bugzilla.kernel.org/show_bug.cgi?id=221801 Re: [PATCH v3] PCI: Skip Target Speed quirk on clamped ports with no link [implicit due to link] , by Thorsten Leemhuis note: https://bugzilla.kernel.org/show_bug.cgi?id=221801 Re: [PATCH v3] PCI: Skip Target Speed quirk on clamped ports with no link [implicit due to link] , by Thorsten Leemhuis note: https://bugzilla.kernel.org/show_bug.cgi?id=221801 Re: [PATCH v3] PCI: Skip Target Speed quirk on clamped ports with no link [implicit due to link] , by Thorsten Leemhuis summary: PCI: booting a lot slower (or broke ?) , by Thorsten Leemhuis introduced: 72780f7964684939d7d2f69c348876213b184 , by Thorsten Leemhuis
8e2b43d2c10b (v7.2-rc1)	*edia: i2c: cvs: machine has no sound* by Junjie Cao Earliest & latest activity: & . Noteworthy: [fix incoming]. Fix incoming: ed447e2b1da9 ("media: i2c: cvs: Get the wake IRQ without claiming the GPIO") Latest five known activities: ed447e2b1da9, the fix specified through '#regzbot fix:' earlier landed in next , by Junjie Cao Re: [PATCH] media: i2c: cvs: Get the wake IRQ without claiming the GPIO , by Antti Laakso Re: [PATCH] media: i2c: cvs: Get the wake IRQ without claiming the GPIO , by Junjie Cao Re: [PATCH] media: i2c: cvs: Get the wake IRQ without claiming the GPIO , by Manuel Knitza Re: [PATCH] media: i2c: cvs: Get the wake IRQ without claiming the GPIO , by Manuel Knitza Regzbot command history: note: 'fix' commit 'ed447e2b1da9' now in 'next' , by Junjie Cao note: https://lore.kernel.org/r/20260908105717.496232-1-junjie.cao@intel.com [PATCH v2] media: i2c: cvs: Get the wake IRQ without claiming the GPIO [implicit due to link] , by Junjie Cao note: "[PATCH] media: i2c: cvs: Do not hide the option in the ancillary menu" contains a 'Fixes:' tag for the culprit of this regression , by Junjie Cao fix: media: i2c: cvs: Get the wake IRQ without claiming the GPIO , by Thorsten Leemhuis summary: edia: i2c: cvs: machine has no sound , by Thorsten Leemhuis introduced: 8e2b43d2c10b , by Thorsten Leemhuis note: '7456b40bc992' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Antti Laakso note: "[PATCH] media: i2c: cvs: Get the wake IRQ without claiming the GPIO" contains a 'Fixes:' tag for the culprit of this regression , by Junjie Cao
03a43677ca91 (v7.2-rc1)	*exfat: swapping broken* by Petr Vorel Earliest & latest activity: & . Noteworthy: [fix incoming]. Fix incoming: 80e764ecaf02 ("exfat: map allocated extents for swap activation") Latest five known activities: 80e764ecaf02, the fix specified through '#regzbot fix:' earlier landed in next , by Namjae Jeon d1b432080f57, the fix specified through '#regzbot fix:' earlier landed in next , by Namjae Jeon 20cb0bad8c3a, the fix specified through '#regzbot fix:' earlier landed in next , by Namjae Jeon Re: [LTP] [PATCH v1 1/1] swap: Add exfat to filesystems requiring tst_fill_file , by Petr Vorel Re: [LTP] [PATCH v1 1/1] swap: Add exfat to filesystems requiring tst_fill_file , by Namjae Jeon Regzbot command history: note: 'fix' commit '80e764ecaf02' now in 'next' , by Namjae Jeon note: 'fix' commit 'd1b432080f57' now in 'next' , by Namjae Jeon note: 'fix' commit '20cb0bad8c3a' now in 'next' , by Namjae Jeon fix: exfat: map allocated extents for swap activation , by Thorsten Leemhuis summary: exfat: swapping broken , by Thorsten Leemhuis introduced: 03a43677ca91 , by Thorsten Leemhuis
dd29c017aed6 (v7.2-rc1)	*sched/rt: multi-second PI-boost starvation in pro-audio workloads on an ordinary non-PREEMPT_RT desktop* by Martin King Earliest & latest activity: & . All known activities: Re: [REGRESSION] sched/rt: NO_RT_PUSH_IPI causes multi-second PI-boost starvation in pro-audio workloads (dd29c017aed6) , by Steven Rostedt Re: [REGRESSION] sched/rt: NO_RT_PUSH_IPI causes multi-second PI-boost starvation in pro-audio workloads (dd29c017aed6) , by Thorsten Leemhuis Re: [REGRESSION] sched/rt: NO_RT_PUSH_IPI causes multi-second PI-boost starvation in pro-audio workloads (dd29c017aed6) , by Steven Rostedt sched/rt: NO_RT_PUSH_IPI causes multi-second PI-boost starvation in pro-audio workloads (dd29c017aed6) , by Martin King Regzbot command history: summary: sched/rt: multi-second PI-boost starvation in pro-audio workloads on an ordinary non-PREEMPT_RT desktop , by Thorsten Leemhuis introduced: dd29c017aed6 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: dd29c017aed6 ("sched/rt: Have RT_PUSH_IPI be default off for non PREEMPT_RT") Reported-by: Martin King <martin3kx@gmail.com> Link: https://lore.kernel.org/r/CAEB5A_91hob8ddOhW=PrO1=O7GrFmSxY3r1-_Ard6x8KHHuJGA@mail.gmail.com/
older cycles (..v7.1), culprit identified, with activity in the past three months
3f2ad90060f6 (v7.1-rc1)	*[BUG] KHO handover hangs when memmap reserves PMEM* by Chris Bainbridge Earliest & latest activity: & . Latest five known activities: Re: [BUG] KHO handover hangs when memmap reserves PMEM , by Mike Rapoport Re: [BUG] KHO handover hangs when memmap reserves PMEM , by Chris Bainbridge Re: [BUG] KHO handover hangs when memmap reserves PMEM , by Mike Rapoport Re: [BUG] KHO handover hangs when memmap reserves PMEM , by Pratyush Yadav Re: [BUG] KHO handover hangs when memmap reserves PMEM , by Chris Bainbridge Regzbot command history: note: 'd13dfb48dfa3' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by George Guo note: 'd64b0372760e' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by George Guo introduced: 3f2ad90060f6 , by Chris Bainbridge When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 3f2ad90060f6 ("kho: adopt radix tree for preserved memory tracking") Reported-by: Chris Bainbridge <chris.bainbridge@canonical.com> Link: https://lore.kernel.org/r/asE0R_f2r2TL-3Sy@px13/
2a70e5dc0301 (v7.1-rc1)	*usb: xhci_hcd: Resuming from hibernation fails with "Not enough host resources"* by Harald Judt Earliest & latest activity: & . Noteworthy: [1], [patch (SOB)]. [1]: [PATCH 1/5] usb: xhci: clear stale bandwidth data after hibernation [implicit due to Link/Closes tag] , by Niklas Neronin (monitored) Latest patch: [PATCH 1/5] usb: xhci: clear stale bandwidth data after hibernation , by Niklas Neronin; signed-off-by present Earlier patches: 1, 2, 3 Latest five known activities: Re: [PATCH 1/5] usb: xhci: clear stale bandwidth data after hibernation , by sashiko-bot Re: [PATCH 1/5] usb: xhci: clear stale bandwidth data after hibernation , by Michal Pecio [PATCH 1/5] usb: xhci: clear stale bandwidth data after hibernation , by Niklas Neronin; contains a signed-off patch bugzilla.kernel.org, issue 222071: new comment (#14) , by Harald Judt bugzilla.kernel.org, issue 222071: new comment (#13) with patch , by Niklas Neronin; contains a signed-off patch Regzbot command history: relate: https://lore.kernel.org/linux-usb/20261006152427.3735383-2-niklas.neronin@linux.intel.com/ [PATCH 1/5] usb: xhci: clear stale bandwidth data after hibernation [implicit due to Link/Closes tag] , by Niklas Neronin summary: usb: xhci_hcd: Resuming from hibernation fails with "Not enough host resources" , by Thorsten Leemhuis introduced: 2a70e5dc0301ad961b198f086a39e2479f6b8 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 2a70e5dc0301 ("usb: xhci: optimize resuming from S4 (suspend-to-disk)") Reported-by: Harald Judt Link: https://bugzilla.kernel.org/show_bug.cgi?id=222071
0a3fe972a7cb (v7.0-rc5)	*amd_sfh: accelerometer broken since 6.19 ("Event data for report 1 was too short (15 vs 14)")* by Andrej Scek Earliest & latest activity: & . Noteworthy: [1], [2], [patch (SOB)]. [1]: [PATCH -next 3/3] HID: amd_sfh: Remove unsupported motion-state field from accelerometer report [implicit due to Link/Closes tag] , by Basavaraj Natikar (monitored) [2]: [PATCH -next v2 3/4] HID: amd_sfh: Remove unsupported motion-state field from accelerometer report [implicit due to Link/Closes tag] , by Basavaraj Natikar (monitored) Latest patch: [PATCH -next v2 3/4] HID: amd_sfh: Remove unsupported motion-state field from accelerometer report , by Basavaraj Natikar; signed-off-by present Earlier patches: 1 All known activities: [PATCH -next v2 3/4] HID: amd_sfh: Remove unsupported motion-state field from accelerometer report , by Basavaraj Natikar; contains a signed-off patch [PATCH -next 3/3] HID: amd_sfh: Remove unsupported motion-state field from accelerometer report , by Basavaraj Natikar; contains a signed-off patch Re: [REGRESSION] amd_sfh: accelerometer broken since 6.19 ("Event data for report 1 was too short (15 vs 14)") , by Andrej Scek amd_sfh: accelerometer broken since 6.19 ("Event data for report 1 was too short (15 vs 14)") , by Andrej Scek Regzbot command history: relate: https://lore.kernel.org/stable/20261006103754.3614316-4-Basavaraj.Natikar@amd.com/ [PATCH -next v2 3/4] HID: amd_sfh: Remove unsupported motion-state field from accelerometer report [implicit due to Link/Closes tag] , by Basavaraj Natikar relate: https://lore.kernel.org/stable/20261004155919.726226-4-Basavaraj.Natikar@amd.com/ [PATCH -next 3/3] HID: amd_sfh: Remove unsupported motion-state field from accelerometer report [implicit due to Link/Closes tag] , by Basavaraj Natikar introduced: 0a3fe972a7cb , by Andrej Scek introduced: v6.18..v6.19 , by Andrej Scek When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 0a3fe972a7cb ("HID: core: Mitigate potential OOB by removing bogus memset()") Reported-by: Andrej Scek <scek.andrej@gmail.com> Link: https://lore.kernel.org/r/CADrS85612m-Hh-G4BJmOhy-y6r3Ni3kD8_GM-2QRBeWWEEZWuA@mail.gmail.com/
b921aa3f8dec (v7.0-rc1)	*PCI/pwrctrl: WCN7850 on PERST#-less qcom port not enumerated after pwrctrl rework* by François Roux Earliest & latest activity: & . Noteworthy: [1], [patch (SOB)]. [1]: [PATCH v2] power: sequencing: qcom-wcn: power off WLAN at probe [implicit due to Link/Closes tag] , by François Roux (monitored) Latest patch: [PATCH v2] power: sequencing: qcom-wcn: power off WLAN at probe , by François Roux; signed-off-by present Earlier patches: 1, 2 Latest five known activities: Re: [PATCH v2] power: sequencing: qcom-wcn: power off WLAN at probe , by Bartosz Golaszewski Re: [PATCH v2] power: sequencing: qcom-wcn: power off WLAN at probe , by sashiko-bot [PATCH v2] power: sequencing: qcom-wcn: power off WLAN at probe , by François Roux; contains a signed-off patch Re: [PATCH] power: sequencing: qcom-wcn: power off WLAN at probe , by sashiko-bot [PATCH] power: sequencing: qcom-wcn: power off WLAN at probe , by Franz; contains a signed-off patch Regzbot command history: relate: https://lore.kernel.org/lkml/20261004165124.4277-1-franzelfranzel@gmail.com/ [PATCH v2] power: sequencing: qcom-wcn: power off WLAN at probe [implicit due to Link/Closes tag] , by François Roux note: '2d8c5098b847' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Chen-Yu Tsai summary: PCI/pwrctrl: WCN7850 on PERST#-less qcom port not enumerated after pwrctrl rework , by François Roux introduced: b921aa3f8dec , by François Roux When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: b921aa3f8dec ("PCI/pwrctrl: Switch to pwrctrl create, power on/off, destroy APIs") Reported-by: François Roux <franzelfranzel@gmail.com> Link: https://lore.kernel.org/r/CAPjyS8dY0Q_o3XmFjuKZZsjhzhoSNL%2BZGJtw5cQt8HiV3sUtxA@mail.gmail.com/
0ac903d1bfdc (v7.0-rc1)	*NFSD: U-Boot can no longer access symlinks in NFS shares* by Jörg Sommer Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH v1] NFSD: Return NFSERR_ISDIR for NFSv2 READ and WRITE on a non-regular file , by Chuck Lever (monitored) Fix incoming: 07649099cc8c ("NFSD: Return NFSERR_ISDIR for NFSv2 READ and WRITE on a non-regular file") Latest five known activities: Commit 07649099cc8c in next , by Chuck Lever 07649099cc8c, the fix specified through '#regzbot fix:' earlier landed in next , by Chuck Lever Commit ac04dab23b5f in next , by Chuck Lever ac04dab23b5f, the fix specified through '#regzbot fix:' earlier landed in next , by Chuck Lever Commit f946aa41b37c in next , by Chuck Lever Regzbot command history: fix: 07649099cc8c in next referred to this regression , by Chuck Lever note: 'fix' commit '07649099cc8c' now in 'next' , by Chuck Lever fix: ac04dab23b5f in next referred to this regression , by Chuck Lever note: 'fix' commit 'ac04dab23b5f' now in 'next' , by Chuck Lever fix: f946aa41b37c in next referred to this regression , by Chuck Lever note: 'fix' commit 'f946aa41b37c' now in 'next' , by Chuck Lever fix: 8c17541454cf in next referred to this regression , by Chuck Lever note: 'fix' commit '8c17541454cf' now in 'next' , by Chuck Lever relate: https://lore.kernel.org/all/20260828231841.282003-1-cel@kernel.org/ , by Thorsten Leemhuis fix: NFSD: Return NFSERR_ISDIR for NFSv2 READ and WRITE on a non-regular file , by Thorsten Leemhuis summary: NFSD: U-Boot can no longer access symlinks in NFS shares , by Thorsten Leemhuis introduced: 0ac903d1bfdce8ff40657c2b7d996947b72b6645 , by Thorsten Leemhuis
7299b1b39a25 (v7.0-rc3)	*can: usb: f81604: valid interrupt URBs are rejected* by Dynetrex, Admin Earliest & latest activity: & . Noteworthy: [1], [2], [3], [4], [5], [patch (SOB)]. [1]: [PATCH v2] can: usb: f81604: fix struct f81604_int_data size mismatch [implicit due to Link/Closes tag] , by Ji-Ze Hong via B4 Relay (monitored) [2]: [PATCH net 13/14] can: usb: f81604: fix struct f81604_int_data size mismatch [implicit due to Link/Closes tag] , by Marc Kleine-Budde (monitored) [3]: [PATCH net 18/22] usb: f81604: fix struct f81604_int_data size mismatch [implicit due to Link/Closes tag] , by Marc Kleine-Budde (monitored) [4]: [PATCH net 10/16] usb: f81604: fix struct f81604_int_data size mismatch [implicit due to Link/Closes tag] , by Marc Kleine-Budde (monitored) [5]: [PATCH net 3/3] usb: f81604: fix struct f81604_int_data size mismatch [implicit due to Link/Closes tag] , by Marc Kleine-Budde (monitored) Latest patch: [PATCH net 3/3] usb: f81604: fix struct f81604_int_data size mismatch , by Marc Kleine-Budde; signed-off-by present Earlier patches: 1, 2, 3, 4 Latest five known activities: Re: [PATCH net 3/3] usb: f81604: fix struct f81604_int_data size mismatch , by Marc Kleine-Budde Re: [PATCH v2] can: usb: f81604: fix struct f81604_int_data size mismatch , by Marc Kleine-Budde [PATCH net 3/3] usb: f81604: fix struct f81604_int_data size mismatch , by Marc Kleine-Budde; contains a signed-off patch [PATCH net 10/16] usb: f81604: fix struct f81604_int_data size mismatch , by Marc Kleine-Budde; contains a signed-off patch [PATCH net 18/22] usb: f81604: fix struct f81604_int_data size mismatch , by Marc Kleine-Budde; contains a signed-off patch Regzbot command history: relate: https://lore.kernel.org/netdev/20261001151905.1556270-4-mkl@pengutronix.de/ [PATCH net 3/3] usb: f81604: fix struct f81604_int_data size mismatch [implicit due to Link/Closes tag] , by Marc Kleine-Budde relate: https://lore.kernel.org/netdev/20260929210700.1183036-11-mkl@pengutronix.de/ [PATCH net 10/16] usb: f81604: fix struct f81604_int_data size mismatch [implicit due to Link/Closes tag] , by Marc Kleine-Budde relate: https://lore.kernel.org/netdev/20260928193312.553632-19-mkl@pengutronix.de/ [PATCH net 18/22] usb: f81604: fix struct f81604_int_data size mismatch [implicit due to Link/Closes tag] , by Marc Kleine-Budde relate: https://lore.kernel.org/netdev/20260826121036.2706424-14-mkl@pengutronix.de/ [PATCH net 13/14] can: usb: f81604: fix struct f81604_int_data size mismatch [implicit due to Link/Closes tag] , by Marc Kleine-Budde relate: https://lore.kernel.org/lkml/20260824-f81604-fix-v2-1-fc9be5581394@fintek.com.tw/ [PATCH v2] can: usb: f81604: fix struct f81604_int_data size mismatch [implicit due to Link/Closes tag] , by Ji-Ze Hong via B4 Relay note: https://lore.kernel.org/r/A3834A07-5639-4779-844F-C5843DFC3928@dynetrex.com Re: [PATCH] can: usb: f81604: fix struct f81604_int_data size mismatch [implicit due to link] , by Greg KH note: "[PATCH] can: usb: f81604: fix struct f81604_int_data size mismatch" contains a 'Fixes:' tag for the culprit of this regression , by PS10 PETER HONG 洪繼澤 summary: can: usb: f81604: valid interrupt URBs are rejected , by Thorsten Leemhuis introduced: 7299b1b39a255f , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 7299b1b39a25 ("can: usb: f81604: handle short interrupt urb messages properly") Reported-by: Dynetrex, Admin <admin@dynetrex.com> Link: https://lore.kernel.org/r/A3834A07-5639-4779-844F-C5843DFC3928@dynetrex.com/
ff643b81bc38 (v7.1-rc1)	*wifi: mt76: mt7925: WiFi 7 MLO (5GHz+6GHz) silently stops passing traffic after a few minutes* by Jonas Hort Earliest & latest activity: & . Noteworthy: [1], [patch (SOB)]. [1]: Re: [REGRESSION] mt7925: MLO connectivity silently stalls with 6GHz link active , by Jonas Hort (monitored) Latest patch: [PATCH v2] wifi: mt76: mt7925: keep MLD membership consistent during link add , by Andrei Rusu de Castro; signed-off-by present Latest five known activities: Re: [PATCH v2] wifi: mt76: mt7925: keep MLD membership consistent during link add , by Devin Wittmayer Re: [PATCH v2] wifi: mt76: mt7925: keep MLD membership consistent during link add , by Jonas Hort [PATCH v2] wifi: mt76: mt7925: keep MLD membership consistent during link add , by Andrei Rusu de Castro; contains a signed-off patch Re: [REGRESSION] mt7925: MLO connectivity silently stalls with 6GHz link active , by Andrei Rusu de Castro Re: [REGRESSION] mt7925: MLO connectivity silently stalls with 6GHz link active , by Devin Wittmayer Regzbot command history: relate: https://lore.kernel.org/all/503eb10e-80cf-493e-95fd-04fc0f94ce01@posteo.de/ , by Thorsten Leemhuis summary: wifi: mt76: mt7925: WiFi 7 MLO (5GHz+6GHz) silently stops passing traffic after a few minutes , by Thorsten Leemhuis introduced: ff643b81bc38eaff6c0 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: ff643b81bc38 ("wifi: mt76: mt7925: pass mlink and mconf to sta_mld_tlv()") Reported-by: Jonas Hort <jonas.hort@posteo.de> Link: https://lore.kernel.org/r/066b30cc-a9e6-4aeb-964d-71551e8ea3ef@posteo.de/
d33e89d12295 (v7.1-rc1)	*thermal: core: battery data corrupted after resume on ThinkPad P1 Gen2 since d33e89d12295* by Charis Stratakis Earliest & latest activity: . Noteworthy: [1]. [1]: After "Resume thermal zones asynchronously" commit: Wrong Battery Reading after Wake from S3 Sleep - Lenovo Thinkpad P1 Gen2 , by fhortner All known activities: thermal: core: battery data corrupted after resume on ThinkPad P1 Gen2 since d33e89d12295 , by Charis Stratakis Regzbot command history: relatebrief: https://bugzilla.kernel.org/show_bug.cgi?id=218881 , by Charis Stratakis introduced: d33e89d12295 , by Charis Stratakis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: d33e89d12295 ("thermal: core: Suspend thermal zones later and resume them earlier") Reported-by: Charis Stratakis <c.stratakis@proton.me> Link: https://lore.kernel.org/r/37N_jFulf7n-Z55NfKfE71C_wVPxYvZ0xD_iRUg2fXu7TypDiF5PStQ6siSfVBih6fThg5WoPes8U5ZQpfVm_teMFcUGXFxz2DdMbfSWuws=@proton.me/
82378c6c2f43 (v6.15-rc1)	*x86/mm: Probabilistic segfaults on AMD hardware with INVLPGB* by Henrik Böving Earliest & latest activity: & . Noteworthy: [patch]. Latest patch: Re: PROBLEM: Probabilistic segfault on AMD hardware with INVLPGB , by Rik van Riel; simple patch Latest five known activities: Re: PROBLEM: Probabilistic segfault on AMD hardware with INVLPGB , by Borislav Petkov Re: PROBLEM: Probabilistic segfault on AMD hardware with INVLPGB , by Borislav Petkov Re: PROBLEM: Probabilistic segfault on AMD hardware with INVLPGB , by Tal Zussman Re: PROBLEM: Probabilistic segfault on AMD hardware with INVLPGB , by Borislav Petkov Re: PROBLEM: Probabilistic segfault on AMD hardware with INVLPGB , by Matt Fleming Regzbot command history: note: https://lore.kernel.org/all/CAAuFnRTyva1_3tsF3vrMBL+TLS1YL4EgUPT2c3O9k7A9hWUMnA@mail.gmail.com/ Re: hunting memory corruption bug in 6.18.x [implicit due to link] , by Lorenzo Stoakes (ARM) summary: x86/mm: Probabilistic segfaults on AMD hardware with INVLPGB , by Thorsten Leemhuis introduced: 82378c6c2f435d , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 82378c6c2f43 ("x86/mm: Use INVLPGB for kernel TLB flushes") Reported-by: Henrik Böving <henrik@lean-fro.org> Link: https://lore.kernel.org/r/CAAuFnRTyva1_3tsF3vrMBL%2BTLS1YL4EgUPT2c3O9k7A9hWUMnA@mail.gmail.com/
3958bf16e2fe (v7.0-rc1)	*PCI: bridge window undersized when child bridge windows are larger than their alignment (regression since 3958bf16e2fe, v7.0)* by Nikolas Joshua Britton Earliest & latest activity: & . Noteworthy: [1], [2], [patch (SOB)]. [1]: [PATCH 4/5] PCI: Fix composite resource sizing [implicit due to Link/Closes tag] , by Ilpo Järvinen (monitored) [2]: [PATCH v2 6/7] PCI: Fix composite resource sizing [implicit due to Link/Closes tag] , by Ilpo Järvinen (monitored) Latest patch: [PATCH v2 6/7] PCI: Fix composite resource sizing , by Ilpo Järvinen; signed-off-by present Earlier patches: 1, 2 Latest five known activities: Re: [PATCH v2 6/7] PCI: Fix composite resource sizing , by sashiko-bot Re: PCI: bridge window undersized when child bridge windows are larger than their alignment (regression since 3958bf16e2fe, v7.0) , by Ilpo Järvinen [PATCH v2 6/7] PCI: Fix composite resource sizing , by Ilpo Järvinen; contains a signed-off patch Re: [PATCH 4/5] PCI: Fix composite resource sizing , by Ilpo Järvinen Re: [PATCH 4/5] PCI: Fix composite resource sizing , by sashiko-bot Regzbot command history: relate: https://lore.kernel.org/lkml/20261002113319.6652-7-ilpo.jarvinen@linux.intel.com/ [PATCH v2 6/7] PCI: Fix composite resource sizing [implicit due to Link/Closes tag] , by Ilpo Järvinen relate: https://lore.kernel.org/lkml/20260923131757.7792-5-ilpo.jarvinen@linux.intel.com/ [PATCH 4/5] PCI: Fix composite resource sizing [implicit due to Link/Closes tag] , by Ilpo Järvinen introduced: 3958bf16e2fe , by Nikolas Joshua Britton When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 3958bf16e2fe ("PCI: Stop over-estimating bridge window size") Reported-by: Nikolas Joshua Britton <nbritton@exabit.io> Link: https://lore.kernel.org/r/20260903063124.9316-1-nbritton@exabit.io/
1a6845aaa6de (v7.0-rc1)	*[PATCH v2 0/2] PCI: Fix Renesas uPD720201 hang after the RCB Link Control write* by Stefan Roese Earliest & latest activity: & . Noteworthy: [patch (SOB)]. Latest patch: [PATCH v2 2/2] PCI: Set RCB only when the Root Port has it set , by Stefan Roese; signed-off-by present Earlier patches: 1, 2 All known activities: Re: [PATCH v2 1/2] PCI/ASPM: Clear ASPM Control on links without common ASPM support , by sashiko-bot Re: [PATCH v2 2/2] PCI: Set RCB only when the Root Port has it set , by sashiko-bot [PATCH v2 2/2] PCI: Set RCB only when the Root Port has it set , by Stefan Roese; contains a signed-off patch [PATCH v2 1/2] PCI/ASPM: Clear ASPM Control on links without common ASPM support , by Stefan Roese; contains a signed-off patch [PATCH v2 0/2] PCI: Fix Renesas uPD720201 hang after the RCB Link Control write , by Stefan Roese; contains a simple patch Regzbot command history: note: "[PATCH v2 2/2] PCI: Set RCB only when the Root Port has it set" contains a 'Fixes:' tag for the culprit of this regression , by Stefan Roese note: "[PATCH v2 1/2] PCI/ASPM: Clear ASPM Control on links without common ASPM support" contains a 'Fixes:' tag for the culprit of this regression , by Stefan Roese introduced: 1a6845aaa6de , by Stefan Roese When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 1a6845aaa6de ("PCI: Initialize RCB from pci_configure_device()") Reported-by: Stefan Roese <stefan.roese@mailbox.org> Link: https://lore.kernel.org/r/20261002091029.2225203-1-stefan.roese@mailbox.org/
1a6845aaa6de (v7.0-rc1)	*[PATCH 0/2] PCI: Fix Renesas uPD720201 hang after the RCB Link Control write* by Stefan Roese Earliest & latest activity: & . Noteworthy: [patch]. Latest patch: [PATCH 0/2] PCI: Fix Renesas uPD720201 hang after the RCB Link Control write , by Stefan Roese; simple patch All known activities: Re: [PATCH 1/2] PCI: Write RCB only when it changes , by Stefan Roese Re: [PATCH 1/2] PCI: Write RCB only when it changes , by Haakon Bugge Re: [PATCH 2/2] PCI/ASPM: Clear ASPM Control on links without common ASPM support , by sashiko-bot Re: [PATCH 1/2] PCI: Write RCB only when it changes , by sashiko-bot [PATCH 0/2] PCI: Fix Renesas uPD720201 hang after the RCB Link Control write , by Stefan Roese; contains a simple patch Regzbot command history: note: "[PATCH v2 2/2] PCI: Set RCB only when the Root Port has it set" contains a 'Fixes:' tag for the culprit of this regression , by Stefan Roese note: "[PATCH v2 1/2] PCI/ASPM: Clear ASPM Control on links without common ASPM support" contains a 'Fixes:' tag for the culprit of this regression , by Stefan Roese note: https://lore.kernel.org/r/20260930144650.3701516-1-stefan.roese@mailbox.org [PATCH v2 0/2] PCI: Fix Renesas uPD720201 hang after the RCB Link Control write [implicit due to link] , by Stefan Roese introduced: 1a6845aaa6de , by Stefan Roese When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 1a6845aaa6de ("PCI: Initialize RCB from pci_configure_device()") Reported-by: Stefan Roese <stefan.roese@mailbox.org> Link: https://lore.kernel.org/r/20260930144650.3701516-1-stefan.roese@mailbox.org/
bf3fc94cd72a (v7.1-rc1)	*drm/amd/display: screen will randomly display static on high refresh rates* by solonovamax Earliest & latest activity: & . All known activities: Re: [REGRESSION] drm/amd/display: screen will randomly display static on high refresh rates , by Thorsten Leemhuis drm/amd/display: screen will randomly display static on high refresh rates , by solonovamax Regzbot command history: introduced: bf3fc94cd72abe6fc6cd88691fa98f817f4cd6db , by solonovamax When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: bf3fc94cd72a ("drm/amd/display: Use drm_display_info for AMD VSDB data") Reported-by: solonovamax <solonovamax@12oclockpoint.com> Link: https://lore.kernel.org/r/9404c689-a95f-4475-a53a-47a724f6784f@12oclockpoint.com/
4b490e0d103c (v6.19-rc1)	*ALSA snd-ctxfi: no PCM playback* by Dany Patoine Earliest & latest activity: & . Noteworthy: [patch]. Latest patch: Re: [REGRESSION 6.14 -> 7.0] ALSA snd-ctxfi: no PCM playback on Creative X-Fi Titanium HD (EMU20k2 / SB1270) , by Dany Patoine; simple patch All known activities: Re: [REGRESSION 6.14 -> 7.0] ALSA snd-ctxfi: no PCM playback on Creative X-Fi Titanium HD (EMU20k2 / SB1270) , by Dany Patoine; contains a simple patch Re: [REGRESSION 6.14 -> 7.0] ALSA snd-ctxfi: no PCM playback on Creative X-Fi Titanium HD (EMU20k2 / SB1270) , by Dany Patoine Re: [REGRESSION 6.14 -> 7.0] ALSA snd-ctxfi: no PCM playback on Creative X-Fi Titanium HD (EMU20k2 / SB1270) , by Takashi Iwai [REGRESSION 6.14 -> 7.0] ALSA snd-ctxfi: no PCM playback on Creative X-Fi Titanium HD (EMU20k2 / SB1270) , by Dany Patoine Regzbot command history: summary: ALSA snd-ctxfi: no PCM playback , by Thorsten Leemhuis introduced: 4b490e0d103c , by Thorsten Leemhuis note: '4fa0c91c2c4c' in 'mainline' contains a 'Fixes:' tag for the culprit of this regression , by Harin Lee note: '4fa0c91c2c4c' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Harin Lee note: "[PATCH] ALSA: ctxfi: Fix silent playback on Titanium HD (SB1270)" contains a 'Fixes:' tag for the culprit of this regression , by Harin Lee summary: ALSA: ctxfi: no PCM playback on Creative X-Fi Titanium HD (EMU20k2 / SB1270) , by Thorsten Leemhuis introduced: 4b490e0d103c , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 4b490e0d103c ("ALSA: ctxfi: Add ADC helper functions for GPIO") Reported-by: Dany Patoine <dany_patoine@hotmail.com> Link: https://lore.kernel.org/r/DM6PR02MB5433F3C2A156335B6ED47756EA8E2@DM6PR02MB5433.namprd02.prod.outlook.com/
b364a0d23cae (v7.1-rc1)	*ALSA: usb-audio: Behringer USB-MIDI output stalls, since "Use strings in struct usb_dev for manufacturer & co"* by Jan Lentfer Earliest & latest activity: & . Noteworthy: [patch]. Latest patch: Re: [REGRESSION] ALSA: usb-audio: Behringer USB-MIDI output stalls, since "Use strings in struct usb_dev for manufacturer & co" , by Takashi Iwai; simple patch All known activities: Re: [REGRESSION] ALSA: usb-audio: Behringer USB-MIDI output stalls, since "Use strings in struct usb_dev for manufacturer & co" , by Takashi Iwai Re: [REGRESSION] ALSA: usb-audio: Behringer USB-MIDI output stalls, since "Use strings in struct usb_dev for manufacturer & co" , by Jan Lentfer Re: [REGRESSION] ALSA: usb-audio: Behringer USB-MIDI output stalls, since "Use strings in struct usb_dev for manufacturer & co" , by Takashi Iwai; contains a simple patch ALSA: usb-audio: Behringer USB-MIDI output stalls, since "Use strings in struct usb_dev for manufacturer & co" , by Jan Lentfer Regzbot command history: note: 'b5c4823cf3e4' in 'mainline' contains a 'Fixes:' tag for the culprit of this regression , by Takashi Iwai note: 'b5c4823cf3e4' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Takashi Iwai introduced: b364a0d23cae15 , by Thorsten Leemhuis introduced: v7.0..v7.1 , by Jan Lentfer When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: b364a0d23cae ("ALSA: usb-audio: Use strings in struct usb_dev for manufacturer & co") Reported-by: Jan Lentfer <jan.lentfer@web.de> Link: https://lore.kernel.org/r/e7087d42-5e74-4d85-b1c5-b11eff235d41@web.de/
7029acd8a950 (v6.13-rc1)	*io_uring MSG_RING SEND_FD fixed-file installation slowdown* by Chengfeng Lin Earliest & latest activity: & . Noteworthy: [1], [2], [3], [patch]. [1]: [RFC PATCH 1/3] io_uring/rsrc: allocate io_rsrc_node from a dedicated kmem_cache [implicit due to Link/Closes tag] , by Uzair Beg (monitored) [2]: [RFC PATCH 2/3] io_uring/rsrc: bulk refill the node cache on allocation miss [implicit due to Link/Closes tag] , by Uzair Beg (monitored) [3]: [RFC PATCH 3/3] io_uring/rsrc: prefill the node cache when a file table is registered empty [implicit due to Link/Closes tag] , by Uzair Beg (monitored) Latest patch: [RFC PATCH 3/3] io_uring/rsrc: prefill the node cache when a file table is registered empty , by Uzair Beg; simple patch Earlier patches: 1, 2 Latest five known activities: Re: [RFC PATCH 3/3] io_uring/rsrc: prefill the node cache when a file table is registered empty , by Gabriel Krisman Bertazi Re: [RFC PATCH 3/3] io_uring/rsrc: prefill the node cache when a file table is registered empty , by Uzair Beg Re: [RFC PATCH 1/3] io_uring/rsrc: allocate io_rsrc_node from a dedicated kmem_cache , by Uzair Beg Re: [RFC PATCH 3/3] io_uring/rsrc: prefill the node cache when a file table is registered empty , by Gabriel Krisman Bertazi Re: [RFC PATCH 1/3] io_uring/rsrc: allocate io_rsrc_node from a dedicated kmem_cache , by Gabriel Krisman Bertazi Regzbot command history: relate: https://lore.kernel.org/lkml/20260914092049.130079-4-uzairbeg11@gmail.com/ [RFC PATCH 3/3] io_uring/rsrc: prefill the node cache when a file table is registered empty [implicit due to Link/Closes tag] , by Uzair Beg relate: https://lore.kernel.org/lkml/20260914092049.130079-3-uzairbeg11@gmail.com/ [RFC PATCH 2/3] io_uring/rsrc: bulk refill the node cache on allocation miss [implicit due to Link/Closes tag] , by Uzair Beg relate: https://lore.kernel.org/lkml/20260914092049.130079-2-uzairbeg11@gmail.com/ [RFC PATCH 1/3] io_uring/rsrc: allocate io_rsrc_node from a dedicated kmem_cache [implicit due to Link/Closes tag] , by Uzair Beg note: https://lore.kernel.org/io-uring/CANGjgdmt0FQ=offsdfn+wEaDxbOFoAa6bi92X_vEo4S6aCZ56A@mail.gmail.com/ [RFC PATCH 0/3] io_uring/rsrc: reduce node allocation cost on sparse file table installs [implicit due to link] , by Uzair Beg note: '6eeeb08a0474' in 'stable/linux-6.14.y' contains a 'Fixes:' tag for the culprit of this regression , by Pavel Begunkov note: 'ab6005f3912f' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Pavel Begunkov summary: io_uring MSG_RING SEND_FD fixed-file installation slowdown , by Chengfeng Lin introduced: 7029acd8a950 , by Chengfeng Lin When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 7029acd8a950 ("io_uring/rsrc: get rid of per-ring io_rsrc_node list") Reported-by: Chengfeng Lin <lin2530632123@gmail.com> Link: https://lore.kernel.org/r/CANGjgdmt0FQ=offsdfn%2BwEaDxbOFoAa6bi92X_vEo4S6aCZ56A@mail.gmail.com/
8d95d1f4aa5c (v7.1-rc1)	*platform/x86: asus-wmi: ScreenPad stops functioning as a secondary display* by Salvatore Bonaccorso and Denis Benato Earliest & latest activity: & . Noteworthy: [1], [2], [3], [4], [5], [6], [7], [fix incoming]. [1]: Re: Bug#1141604: linux-image-6.12.94+deb13-amd64: does not detect ScreenPad on ASUS VivoBook , by Salvatore Bonaccorso [2]: [PATCH] platform/x86: asus-wmi: fix unclear usage of bd->props.power [implicit due to Link/Closes tag] , by Denis Benato (monitored) [3]: [PATCH] platform/x86: asus-wmi: fix unclear usage of bd->props.power [implicit due to Link/Closes tag] , by Denis Benato (monitored) [via dup] [4]: Re: asus-wmi: screenpad backlight power state is never read back (UX5400EA) [implicit due to Link/Closes tag] , by Denis Benato (monitored) [5]: Re: asus-wmi: screenpad backlight power state is never read back (UX5400EA) [implicit due to Link/Closes tag] , by Denis Benato (monitored) [via dup] [6]: [PATCH v1 0/4] platform/x86: asus-wmi: fix screenpad backlight regression [implicit due to Link/Closes tag] , by Denis Benato (monitored) [7]: [PATCH v1 1/4] platform/x86: asus-wmi: fix unclear usage of bd->props.power [implicit due to Link/Closes tag] , by Denis Benato (monitored) [via dup] Fix incoming: 159e956fd4f9 ("platform/x86: asus-wmi: fix unclear usage of bd->props.power") Latest five known activities: Commit 159e956fd4f9 in next , by Denis Benato Re: [PATCH v1 0/4] platform/x86: asus-wmi: fix screenpad backlight regression , by Ilpo Järvinen [PATCH v1 4/4] platform/x86: asus-wmi: remove unused screenpad_brightness , by Denis Benato; contains a signed-off patch [PATCH v1 3/4] platform/x86: asus-wmi: use backlight_is_blank() for screenpad power , by Denis Benato; contains a signed-off patch [PATCH v1 2/4] platform/x86: asus-wmi: fix screenpad power state detection , by Denis Benato; contains a signed-off patch Regzbot command history: fix: 159e956fd4f9 in next referred to this regression , by Denis Benato relate: https://lore.kernel.org/lkml/20260916143838.170950-1-denis.benato@linux.dev/ [PATCH v1 0/4] platform/x86: asus-wmi: fix screenpad backlight regression [implicit due to Link/Closes tag] , by Denis Benato relate: https://lore.kernel.org/platform-driver-x86/d34b4d0f-2db4-47fb-bada-ef71f3ef3eff@linux.dev/ Re: asus-wmi: screenpad backlight power state is never read back (UX5400EA) [implicit due to Link/Closes tag] , by Denis Benato relate: https://lore.kernel.org/lkml/20260819205353.1651888-1-denis.benato@linux.dev/ [PATCH] platform/x86: asus-wmi: fix unclear usage of bd->props.power [implicit due to Link/Closes tag] , by Denis Benato duplicate: https://lore.kernel.org/all/ea9c63d1-4776-49d5-9dc4-6c09498f99c9@linux.dev/ , by Thorsten Leemhuis summary: platform/x86: asus-wmi: ScreenPad stops functioning as a secondary display , by Thorsten Leemhuis note: https://lore.kernel.org/all/178362762638.911488.8564892548331679884@eldamar.lan/ Re: [PATCH v3 1/2] platform/x86: asus-wmi: adjust screenpad power/brightness handling — regression on non-DUO ScreenPad (ASUS ZenBook UX435EG) [implicit due to link] , by Denis Benato note: https://lore.kernel.org/all/178362762638.911488.8564892548331679884@eldamar.lan/ Re: [PATCH v3 1/2] platform/x86: asus-wmi: adjust screenpad power/brightness handling — regression on non-DUO ScreenPad (ASUS ZenBook UX435EG) [implicit due to link] , by Denis Benato relatebrief: https://bugs.debian.org/1141604 , by Salvatore Bonaccorso introduced: 8d95d1f4aa5c76202b0833a70998769384612488 , by Salvatore Bonaccorso
6456ccbd2ff7 (v6.17-rc1)	*apparmor AF_UNIX datagram send slowdown* by Chengfeng Lin Earliest & latest activity: & . All known activities: Re: [REGRESSION] apparmor: AF_UNIX datagram send slowdown after 6456ccbd2ff7 , by Chengfeng Lin Re: [REGRESSION] apparmor: AF_UNIX datagram send slowdown after 6456ccbd2ff7 , by John Johansen apparmor: AF_UNIX datagram send slowdown after 6456ccbd2ff7 , by Chengfeng Lin Regzbot command history: summary: apparmor AF_UNIX datagram send slowdown , by Chengfeng Lin introduced: 6456ccbd2ff7 , by Chengfeng Lin When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 6456ccbd2ff7 ("apparmor: fix regression in fs based unix sockets when using old abi") Reported-by: Chengfeng Lin <lin2530632123@gmail.com> Link: https://lore.kernel.org/r/CANGjgdnoz4NdqzOV9%2BSZaYTc%2BO_GkNNn5NVp%2BZpHUQbp5h-QVQ@mail.gmail.com/
4d4c10f763d7 (v6.16-rc1)	*[REGRESSION 6.16] r8169 RTL8168h/8111h fails to probe — "Unable to change power state from D3cold to D0" — bisected to 4d4c10f763d7* by Josh Perry Earliest & latest activity: & . All known activities: Re: [REGRESSION 6.16] r8169 RTL8168h/8111h fails to probe — "Unable to change power state from D3cold to D0" — bisected to 4d4c10f763d7 , by Bjorn Helgaas Re: [REGRESSION 6.16] r8169 RTL8168h/8111h fails to probe — "Unable to change power state from D3cold to D0" — bisected to 4d4c10f763d7 , by Mario Limonciello Re: [REGRESSION 6.16] r8169 RTL8168h/8111h fails to probe — "Unable to change power state from D3cold to D0" — bisected to 4d4c10f763d7 , by Thorsten Leemhuis [REGRESSION 6.16] r8169 RTL8168h/8111h fails to probe — "Unable to change power state from D3cold to D0" — bisected to 4d4c10f763d7 , by Josh Perry Regzbot command history: note: https://lore.kernel.org/netdev/d4aaa5e8-7366-461c-94b1-ccf3631c8bf9@6bit.com/ Re: [REGRESSION][BISECTED] HDA controller MMIO unreadable on Intel 5-series PCH (Ibex Peak) since v6.16 [implicit due to link] , by Filippe Duke note: https://lore.kernel.org/netdev/d4aaa5e8-7366-461c-94b1-ccf3631c8bf9@6bit.com/ Re: [REGRESSION][BISECTED] HDA controller MMIO unreadable on Intel 5-series PCH (Ibex Peak) since v6.16 [implicit due to link] , by Thorsten Leemhuis note: '907a7a2e5bf4' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Mario Limonciello introduced: 4d4c10f763d7 , by Josh Perry When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 4d4c10f763d7 ("PCI: Explicitly put devices into D0 when initializing") Reported-by: Josh Perry <josh@6bit.com> Link: https://lore.kernel.org/r/d4aaa5e8-7366-461c-94b1-ccf3631c8bf9@6bit.com/
1f340724419e (v6.15-rc1)	*PCI_DYNAMIC_OF_NODES early boot hang on ACPI x86* by Angel J Earliest & latest activity: & . Noteworthy: [patch (SOB)]. Latest patch: [PATCH v3] PCI: of_property: Omit bus properties without a subordinate bus , by Bjorn Helgaas; signed-off-by present Earlier patches: 1, 2, 3 Latest five known activities: Re: [PATCH v3] PCI: of_property: Omit bus properties without a subordinate bus , by Angel J Re: [PATCH v3] PCI: of_property: Omit bus properties without a subordinate bus , by Bjorn Helgaas Re: [PATCH v3] PCI: of_property: Omit bus properties without a subordinate bus , by sashiko-bot [PATCH v3] PCI: of_property: Omit bus properties without a subordinate bus , by Bjorn Helgaas; contains a signed-off patch Re: [REGRESSION] PCI: Dynamic OF node creation hangs on invalid bridge configuration , by Sasha Levin Regzbot command history: introduced: 1f340724419eda8ab07a20edcaf5ec8f70134231 , by Angel J note: 'db3a3a15563a' in 'stable/linux-6.17.y' contains a 'Fixes:' tag for the culprit of this regression , by Christophe JAILLET note: '2f4f72e580b5' in 'stable/linux-6.18.y' contains a 'Fixes:' tag for the culprit of this regression , by Christophe JAILLET note: '639fa8af506e' in 'stable/linux-6.18.y' contains a 'Fixes:' tag for the culprit of this regression , by Xiaolei Wang note: '9f608ae5ea78' in 'stable/linux-7.0.y' contains a 'Fixes:' tag for the culprit of this regression , by Xiaolei Wang note: '43cd4b634ef9' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Christophe JAILLET note: '367704171536' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Xiaolei Wang summary: PCI_DYNAMIC_OF_NODES early boot hang on ACPI x86 , by Angel J introduced: 49d63971f963 , by Angel J When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 1f340724419e ("PCI: of: Create device tree PCI host bridge node") Reported-by: Angel J <iamanaws@httpd.dev> Link: https://lore.kernel.org/r/GXe6anuewkS4bLNwca3cYOmUxN9csc0TxLYGSBc1qNRmfrmvFlcmD62wEM23TxfzfuXAv4P3yvUv7pyraleARrL1Na-aN8w-t9uc1Igu8DA=@httpd.dev/
9f10374bb024 (v7.0-rc1)	*[patch 0/1]can: restore skb header initialisations in init_can_skb()* by Yuchao Zhang Earliest & latest activity: . All known activities: [patch 0/1]can: restore skb header initialisations in init_can_skb() , by Yuchao Zhang Regzbot command history: introduced: 9f10374bb024 , by Yuchao Zhang When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 9f10374bb024 ("can: remove private CAN skb headroom infrastructure") Reported-by: Yuchao Zhang <ndaugoing@gmail.com> Link: https://lore.kernel.org/r/CAC2BP3LyU5Qc80YTk7nq4vS96QKiufyAAdkNjVMr_DvcO=9K8w@mail.gmail.com/
130d29c5627c (v7.1-rc1)	*platform/x86: asus-wmi: screenpad backlight power state is never read back* by hugo baigue Earliest & latest activity: & . Noteworthy: [1], [patch (SOB)]. [1]: [PATCH v1 0/4] platform/x86: asus-wmi: fix screenpad backlight regression [implicit due to Link/Closes tag] , by Denis Benato (monitored) Latest patch: [PATCH v1 4/4] platform/x86: asus-wmi: remove unused screenpad_brightness , by Denis Benato; signed-off-by present Earlier patches: 1, 2, 3, 4, 5, 6 Latest five known activities: [PATCH v1 4/4] platform/x86: asus-wmi: remove unused screenpad_brightness , by Denis Benato; contains a signed-off patch [PATCH v1 3/4] platform/x86: asus-wmi: use backlight_is_blank() for screenpad power , by Denis Benato; contains a signed-off patch [PATCH v1 2/4] platform/x86: asus-wmi: fix screenpad power state detection , by Denis Benato; contains a signed-off patch [PATCH v1 1/4] platform/x86: asus-wmi: fix unclear usage of bd->props.power , by Denis Benato; contains a signed-off patch [PATCH v1 0/4] platform/x86: asus-wmi: fix screenpad backlight regression , by Denis Benato; contains a simple patch Regzbot command history: note: '341b4769f5cf' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Denis Benato note: '159e956fd4f9' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Denis Benato note: "[PATCH v1 2/4] platform/x86: asus-wmi: fix screenpad power state detection" contains a 'Fixes:' tag for the culprit of this regression , by Denis Benato note: "[PATCH v1 1/4] platform/x86: asus-wmi: fix unclear usage of bd->props.power" contains a 'Fixes:' tag for the culprit of this regression , by Denis Benato relate: https://lore.kernel.org/lkml/20260916143838.170950-1-denis.benato@linux.dev/ [PATCH v1 0/4] platform/x86: asus-wmi: fix screenpad backlight regression [implicit due to Link/Closes tag] , by Denis Benato summary: platform/x86: asus-wmi: screenpad backlight power state is never read back , by Thorsten Leemhuis introduced: 130d29c5627c , by Thorsten Leemhuis note: "Re: asus-wmi: screenpad backlight power state is never read back (UX5400EA)" contains a 'Fixes:' tag for the culprit of this regression , by Denis Benato note: "Re: asus-wmi: screenpad backlight power state is never read back (UX5400EA)" contains a 'Fixes:' tag for the culprit of this regression , by Denis Benato When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 130d29c5627c ("platform/x86: asus-wmi: adjust screenpad power/brightness handling") Reported-by: hugo baigue <hugobaigue2004@gmail.com> Link: https://lore.kernel.org/r/CAO84%2BxJLVW_9_D9-8cwJYv_Vz%2BLK7nJqRaG-1P4_eeLrQmSiWw@mail.gmail.com/
65047194 (v7.1-rc1)	*drm: i915: eDP 3840x2400@240 mode lost since 7.1* by starccy Earliest & latest activity: & . Latest five known activities: drm/i915/kernel, issue 16854: new comment (#5) , by starccy drm/i915/kernel, issue 16854: new comment (#4) , by Ankit Nautiyal drm/i915/kernel, issue 16854: new comment (#3) , by Jani Nikula drm/i915/kernel, issue 16854: new comment (#2) , by Jani Nikula drm/i915/kernel, issue 16854: new comment (#1) , by Jani Saarinen Regzbot command history: summary: drm: i915: eDP 3840x2400@240 mode lost since 7.1 , by Thorsten Leemhuis introduced: 65047194 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 65047194 ("drm/i915/dp: Avoid joiner for eDP if not enabled in VBT") Reported-by: starccy <starccy> Link: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/16854
0919db9f3583 (v7.1-rc1)	*HID: asus: touchpad becomes unresponsive* by Panz Dev Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH v2] HID: asus: do not send keyboard init reports to touchpads , by Panz Dev (monitored) Fix incoming: 8099f9da59f1 ("HID: asus: do not send keyboard init reports to touchpads") Latest five known activities: 8099f9da59f1, the fix specified through '#regzbot fix:' earlier landed in next , by Panz Dev Re: [PATCH v2] HID: asus: do not send keyboard init reports to touchpads , by Jiri Kosina Re: [PATCH v2] HID: asus: do not send keyboard init reports to touchpads , by Denis Benato Re: [PATCH v2] HID: asus: do not send keyboard init reports to touchpads , by sashiko-bot Re: [PATCH] HID: asus: fix touchpad multitouch initialization regression , by Panz Dev Regzbot command history: note: 'fix' commit '8099f9da59f1' now in 'next' , by Panz Dev relate: https://lore.kernel.org/all/20260818151431.939132-1-panz.development@gmail.com/ , by Thorsten Leemhuis fix: HID: asus: do not send keyboard init reports to touchpads , by Thorsten Leemhuis summary: HID: asus: touchpad becomes unresponsive , by Thorsten Leemhuis introduced: 0919db9f3583 , by Thorsten Leemhuis note: 'c89046d57d53' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Denis Benato
74afeb812850 (v6.19-rc1)	*drm/vblank: display appears frozen* by Roman Ilin Earliest & latest activity: & . Noteworthy: [fix incoming]. Fix incoming: drm/vblank: Don't arm vblank timer with invalid frame duration Latest five known activities: Re: [PATCH v3] drm/vblank: Don't arm vblank timer with invalid frame duration , by Thomas Zimmermann Re: [PATCH v3] drm/vblank: Don't arm vblank timer with invalid frame duration , by Thorsten Leemhuis Re: [PATCH v3] drm/vblank: Don't arm vblank timer with invalid frame duration , by Thomas Zimmermann Re: [PATCH v3] drm/vblank: Don't arm vblank timer with invalid frame duration , by Thorsten Leemhuis Re: [PATCH v3] drm/vblank: Don't arm vblank timer with invalid frame duration , by Thomas Zimmermann Regzbot command history: fix: drm/vblank: Don't arm vblank timer with invalid frame duration , by Thorsten Leemhuis summary: drm/vblank: display appears frozen , by Thorsten Leemhuis introduced: 74afeb812850 , by Thorsten Leemhuis note: 'ed39ecd3a96c' in 'stable/linux-6.18.y' contains a 'Fixes:' tag for the culprit of this regression , by Thomas Zimmermann note: '141ffb83abe9' in 'stable/linux-6.18.y' contains a 'Fixes:' tag for the culprit of this regression , by Thomas Zimmermann note: '3946d3ba9934' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Thomas Zimmermann note: '79ae8510b5b8' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Thomas Zimmermann
bb204f19e4a1 (v7.1-rc7)	*drm: amdgpu: Runtime resume restores stale power limit wedging RX 7700S* by Hlib Kanunnikov Earliest & latest activity: & . Noteworthy: [1], [patch (SOB)]. [1]: [PATCH] drm/amd: Drop calls to restore power limit and clock from smu_resume() [implicit due to Link/Closes tag] , by Alex Deucher (monitored) Latest patch: [PATCH] drm/amd: Drop calls to restore power limit and clock from smu_resume() , by Alex Deucher; signed-off-by present Latest five known activities: Re: [PATCH] drm/amd: Drop calls to restore power limit and clock from smu_resume() , by Greg KH drm/amd, issue 5634: new comment (#3) , by Alex Deucher [PATCH] drm/amd: Drop calls to restore power limit and clock from smu_resume() , by Alex Deucher; contains a signed-off patch drm/amd, issue 5634: new comment (#2) , by The Linux kernel's regression tracker (Thorsten Leemhuis) drm/amd, issue 5634: new comment (#1) , by Hlib Kanunnikov Regzbot command history: relate: https://lore.kernel.org/stable/20260908135407.1640233-1-alexander.deucher@amd.com/ [PATCH] drm/amd: Drop calls to restore power limit and clock from smu_resume() [implicit due to Link/Closes tag] , by Alex Deucher note: https://gitlab.freedesktop.org/drm/amd/-/work_items/5634 Request stable backport of commit 4b6ec94fdae2 to Linux 6.18.y [implicit due to link] , by Hlib Wondertan summary: drm: amdgpu: Runtime resume restores stale power limit wedging RX 7700S , by Thorsten Leemhuis introduced: bb204f19e4a1 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: bb204f19e4a1 ("drm/amd/pm: fix smu13 power limit default/cap calculation") Reported-by: Hlib Kanunnikov <Wondertan> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/5634
cc6ed470caa2 (v7.1-rc1)	*7.1: apple-gmux backlight dead on MacBookPro13,3 - PCI bridge left with VGA enable set and VGA 16-bit decode cleared, aliasing legacy VGA I/O over the gmux ports* by Haram Choi Earliest & latest activity: & . Noteworthy: [1]. [1]: Re: [REGRESSION] 7.1: apple-gmux backlight dead on MacBookPro13,3 - PCI bridge left with VGA enable set and VGA 16-bit decode cleared, aliasing legacy VGA I/O over the gmux ports , by Haram Choi (monitored) All known activities: Re: [REGRESSION] 7.1: apple-gmux backlight dead on MacBookPro13,3 - PCI bridge left with VGA enable set and VGA 16-bit decode cleared, aliasing legacy VGA I/O over the gmux ports , by Ville Syrjälä Re: [REGRESSION] 7.1: apple-gmux backlight dead on MacBookPro13,3 - PCI bridge left with VGA enable set and VGA 16-bit decode cleared, aliasing legacy VGA I/O over the gmux ports , by Jani Nikula Re: [REGRESSION] 7.1: apple-gmux backlight dead on MacBookPro13,3 - PCI bridge left with VGA enable set and VGA 16-bit decode cleared, aliasing legacy VGA I/O over the gmux ports , by Haram Choi 7.1: apple-gmux backlight dead on MacBookPro13,3 - PCI bridge left with VGA enable set and VGA 16-bit decode cleared, aliasing legacy VGA I/O over the gmux ports , by Haram Choi Regzbot command history: relate: https://lore.kernel.org/all/0102019fcb5d411c-e0a555b7-46da-43a1-bd9d-6cb120f58a7f-000000@eu-west-1.amazonses.com/ , by Thorsten Leemhuis introduced: cc6ed470caa2 , by Thorsten Leemhuis introduced: v6.16..v7.1 , by Haram Choi When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: cc6ed470caa2 ("drm/i915/vga: Avoid VGA arbiter during intel_vga_disable() for iGPUs") Reported-by: Haram Choi <haram@choiharam.com> Link: https://lore.kernel.org/r/0102019fba65882f-45046e0b-9860-445f-a179-c6a1d2acfd1c-000000@eu-west-1.amazonses.com/
3f8f0133a5fc (v6.16-rc1)	*[6.12.y] crypto: ccp - Move SEV/SNP Platform initialization to KVM breaks SEV-ES VM launch* by Andrew Wilson Earliest & latest activity: & . All known activities: Re: Bug#1145026: [REGRESSION] [6.12.y] crypto: ccp - Move SEV/SNP Platform initialization to KVM breaks SEV-ES VM launch , by Salvatore Bonaccorso Re: [REGRESSION] [6.12.y] crypto: ccp - Move SEV/SNP Platform initialization to KVM breaks SEV-ES VM launch , by Andrew Wilson Re: [REGRESSION] [6.12.y] crypto: ccp - Move SEV/SNP Platform initialization to KVM breaks SEV-ES VM launch , by Sean Christopherson [6.12.y] crypto: ccp - Move SEV/SNP Platform initialization to KVM breaks SEV-ES VM launch , by Andrew Wilson Regzbot command history: introduced: 3f8f0133a5fc9b32d0c308530320c3f2430ba5ab , by Andrew Wilson When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 3f8f0133a5fc ("crypto: ccp - Move SEV/SNP Platform initialization to KVM") Reported-by: Andrew Wilson <wizlonex@gmail.com> Link: https://lore.kernel.org/r/CALAyJWrn7OQyQMd5OPoifn_3qe6iWNf1%2BxSSg_six-%2Bpo9kpvQ@mail.gmail.com/
260fbcb92bbe (v6.19-rc1)	*refcount_t: addition on 0; use-after-free, regression from 260fbcb92bbe ("cgroup: Move dying_tasks cleanup from cgroup_task_release() to cgroup_task_free()")* by Salvatore Bonaccorso Earliest & latest activity: & . Noteworthy: [1]. [1]: refcount_t: addition on 0; use-after-free, regression from 260fbcb92bbe ("cgroup: Move dying_tasks cleanup from cgroup_task_release() to cgroup_task_free()") , by Salvatore Bonaccorso All known activities: Re: Bug#1144314: refcount_t: addition on 0; use-after-free, regression from 260fbcb92bbe ("cgroup: Move dying_tasks cleanup from cgroup_task_release() to cgroup_task_free()") , by Salvatore Bonaccorso Re: refcount_t: addition on 0; use-after-free, regression from 260fbcb92bbe ("cgroup: Move dying_tasks cleanup from cgroup_task_release() to cgroup_task_free()") , by Michal Koutný refcount_t: addition on 0; use-after-free, regression from 260fbcb92bbe ("cgroup: Move dying_tasks cleanup from cgroup_task_release() to cgroup_task_free()") , by Salvatore Bonaccorso Regzbot command history: relatebrief: https://bugs.debian.org/1144314 , by Salvatore Bonaccorso introduced: 260fbcb92bbeacfcd050410fdc2d24ab15044400 , by Salvatore Bonaccorso When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 260fbcb92bbe ("cgroup: Move dying_tasks cleanup from cgroup_task_release() to cgroup_task_free()") Reported-by: Salvatore Bonaccorso <carnil@debian.org> Link: https://lore.kernel.org/r/178682274912.1759826.11422695267451330087@eldamar.lan/
6e0d71c288fd (v7.0-rc1)	*io_uring futex WAITV accounted-allocation slowdown* by Chengfeng Lin Earliest & latest activity: . All known activities: Re: [PATCH for-next] io_uring/futex: use GFP_KERNEL_ACCOUNT for futex data allocation , by Chengfeng Lin Regzbot command history: summary: io_uring futex WAITV accounted-allocation slowdown , by Chengfeng Lin introduced: 6e0d71c288fdcf5866f5d0c6cde850a091cc3c55 , by Chengfeng Lin When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 6e0d71c288fd ("io_uring/futex: use GFP_KERNEL_ACCOUNT for futex data allocation") Reported-by: Chengfeng Lin <lin2530632123@gmail.com> Link: https://lore.kernel.org/r/20260830190717.1509012-1-lin2530632123@gmail.com/
4ac74ea68f64 (v7.0-rc1)	*HID: asus: Keyboard Input Issues on Asus ROG Strix 16 (2025) during Gaming* by Thorsten Leemhuis Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH v2 0/1] HID: usbhid: skip interrupt IN polling for devices with no input reports , by Ahmed Yaseen (monitored) Fix incoming: HID: usbhid: skip interrupt IN polling for devices with no input reports All known activities: [PATCH v2] HID: usbhid: skip interrupt IN polling for devices with no input reports , by Ahmed Yaseen; contains a signed-off patch [PATCH v2 0/1] HID: usbhid: skip interrupt IN polling for devices with no input reports , by Ahmed Yaseen; contains a simple patch Regzbot command history: relate: https://lore.kernel.org/all/20260828104159.62399-1-yaseen@ghoul.dev/ , by Thorsten Leemhuis fix: HID: usbhid: skip interrupt IN polling for devices with no input reports , by Thorsten Leemhuis summary: HID: asus: Keyboard Input Issues on Asus ROG Strix 16 (2025) during Gaming , by Thorsten Leemhuis introduced: 4ac74ea68f64 , by Thorsten Leemhuis
0138610c1413 (v7.1-rc1)	*drm: amdgpu: every modeset and monitor wake stalls for ~1.9s* by Petr Belyaev Earliest & latest activity: & . Noteworthy: [1], [patch (SOB)]. [1]: [PATCH] drm/amd/pm/smu7: Don't send VddC_Request on CI [implicit due to Link/Closes tag] , by Petr Belyaev (monitored) Latest patch: [PATCH] drm/amd/pm/smu7: Don't send VddC_Request on CI , by Petr Belyaev; signed-off-by present Latest five known activities: drm/amd, issue 5678: new comment (#5) , by Timur Kristóf drm/amd, issue 5678: new comment (#4) , by Petr Belyaev drm/amd, issue 5678: state changed to: closed , by Petr Belyaev Re: [PATCH] drm/amd/pm/smu7: Don't send VddC_Request on CI , by Timur Kristóf drm/amd, issue 5678: new comment (#3) , by Timur Kristóf Regzbot command history: relate: https://lore.kernel.org/amd-gfx/20260824144714.182835-1-upcfrost@gmail.com/ [PATCH] drm/amd/pm/smu7: Don't send VddC_Request on CI [implicit due to Link/Closes tag] , by Petr Belyaev summary: drm: amdgpu: every modeset and monitor wake stalls for ~1.9s , by Thorsten Leemhuis introduced: 0138610c141304 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 0138610c1413 ("drm/amd/pm/smu7: Fix SMU7 voltage dependency on display clock") Reported-by: Petr Belyaev <upcfrost> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/5678
b96150a70696 (v7.1-rc1)	*drm: amdgpu: DisplayID Type-1 mode no longer enumerated on eDP panel* by Julien YT Earliest & latest activity: & . All known activities: drm/amd, issue 5628: new comment (#1) , by Julien YT drm/amd, issue 5628: submission , by Julien YT Regzbot command history: summary: drm: amdgpu: DisplayID Type-1 mode no longer enumerated on eDP panel , by Thorsten Leemhuis introduced: b96150a7069658 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: b96150a70696 ("drm/amd/display: Should support p-state under dcn21") Reported-by: Julien YT <julien.lebourg8> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/5628
05cffc07 (v7.1-rc1)	*drm: xe: Tiled displays broken* by Christian Zeller Earliest & latest activity: & . All known activities: drm/xe/kernel, issue 8991: new comment (#1) , by Matthew Auld drm/xe/kernel, issue 8991: submission , by Christian Zeller Regzbot command history: note: https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/8991 Re: [PATCH v3 1/1] drm/i915/display: Implement Wa_16024710867 [implicit due to link] , by Jani Nikula summary: drm: xe: Tiled displays broken , by Thorsten Leemhuis introduced: 05cffc07 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 05cffc07 ("drm/i915/display: Implement Wa_16024710867") Reported-by: Christian Zeller <chrizel> Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/8991
28e3918179aa (v7.1-rc1)	*drm/gem-shmem: muvm GPU acceleration dies with KVM* by Konstantin Fastov Earliest & latest activity: & . Noteworthy: [fix incoming]. Fix incoming: drm/shmem_helper: use vmf_insert_pfn_mkwrite() All known activities: Re: [PATCH] drm/gem-shmem: Install writable PTEs for write faults , by kernel test robot Re: [PATCH] drm/gem-shmem: Install writable PTEs for write faults , by sashiko-bot Re: [PATCH] drm/gem-shmem: Install writable PTEs for write faults , by Konstantin Fastov Re: [PATCH] drm/gem-shmem: Install writable PTEs for write faults , by Boris Brezillon [PATCH] drm/gem-shmem: Install writable PTEs for write faults , by Konstantin Fastov; contains a signed-off patch Regzbot command history: fix: drm/shmem_helper: use vmf_insert_pfn_mkwrite() , by Thorsten Leemhuis summary: drm/gem-shmem: muvm GPU acceleration dies with KVM , by Thorsten Leemhuis introduced: 28e3918179aa75 , by Thorsten Leemhuis note: 'cb2a2a5b37ad' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Boris Brezillon note: "[PATCH] drm/gem-shmem: Install writable PTEs for write faults" contains a 'Fixes:' tag for the culprit of this regression , by Konstantin Fastov
0eaa1f245ac0 (v7.1-rc7)	*iwlwifi IO_PAGE_FAULT and Master Disable Timed Out* by Chris Bainbridge Earliest & latest activity: & . All known activities: Re: [REGRESSION] iwlwifi IO_PAGE_FAULT and Master Disable Timed Out , by Chris Bainbridge RE: [REGRESSION] iwlwifi IO_PAGE_FAULT and Master Disable Timed Out , by Korenblit, Miriam Rachel iwlwifi IO_PAGE_FAULT and Master Disable Timed Out , by Chris Bainbridge Regzbot command history: introduced: 0eaa1f245ac03ed0c6394159360532726f666811 , by Chris Bainbridge When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 0eaa1f245ac0 ("wifi: iwlwifi: mvm: don't support the reset handshake for old firmwares") Reported-by: Chris Bainbridge <chris.bainbridge@gmail.com> Link: https://lore.kernel.org/r/amzVtgQb2p-_nShU@debian.local/
c273c14b0294 (v7.0-rc1)	*scsi: mpi3mr: link rate set incorrectly* by Ilya Khomyakov Earliest & latest activity: . Noteworthy: [fix incoming]. Fix incoming: scsi: mpi3mr: use DevicePage0 link rate only for direct-attached targets All known activities: [PATCH] scsi: mpi3mr: use DevicePage0 link rate only for direct-attached targets , by Ilya Khomyakov; contains a signed-off patch Regzbot command history: fix: scsi: mpi3mr: use DevicePage0 link rate only for direct-attached targets , by Thorsten Leemhuis summary: scsi: mpi3mr: link rate set incorrectly , by Thorsten Leemhuis introduced: c273c14b0294 , by Thorsten Leemhuis note: "[PATCH] scsi: mpi3mr: use DevicePage0 link rate only for direct-attached targets" contains a 'Fixes:' tag for the culprit of this regression , by Ilya Khomyakov
105c4256 (v7.0)	*ata: ahci: JMicron JMB58x AHCI 32-bit DMA fallback triggers EEH freeze* by Paul Klapperich Earliest & latest activity: & . All known activities: Re: [Regression] PowerNV: JMicron JMB58x AHCI 32-bit DMA fallback triggers EEH freeze on 7.x kernels , by Paul Klapperich Re: [Regression] PowerNV: JMicron JMB58x AHCI 32-bit DMA fallback triggers EEH freeze on 7.x kernels , by Ritesh Harjani PowerNV: JMicron JMB58x AHCI 32-bit DMA fallback triggers EEH freeze on 7.x kernels , by Paul Klapperich Regzbot command history: summary: ata: ahci: JMicron JMB58x AHCI 32-bit DMA fallback triggers EEH freeze , by Thorsten Leemhuis introduced: 105c4256 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 105c4256 ("ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585") Reported-by: Paul Klapperich <paul.klapperich@gmail.com> Link: https://lore.kernel.org/r/CADyY0-5M0%2BN1u45RVZN3Tf52iKaXcvKeUaqgdw-wP1B_4zuA0w@mail.gmail.com/
f4c31b07b136 (v7.0-rc5)	*sched/idle: Sysbench threads regression after f4c31b07b136* by Joseph Salisbury Earliest & latest activity: & . Noteworthy: [patch (SOB)]. Latest patch: [PATCH] sched/idle: Stop the tick when no cpuidle driver is available , by Christian Loehle; signed-off-by present Earlier patches: 1, 2 Latest five known activities: Re: [REGRESSION] sched/idle: Sysbench threads regression after f4c31b07b136 , by Christian Loehle Re: [REGRESSION] sched/idle: Sysbench threads regression after f4c31b07b136 , by Rafael J. Wysocki (Intel) Re: [REGRESSION] sched/idle: Sysbench threads regression after f4c31b07b136 , by Rafael J. Wysocki (Intel) Re: [REGRESSION] sched/idle: Sysbench threads regression after f4c31b07b136 , by Zhan Xusheng [PATCH] sched/idle: Stop the tick when no cpuidle driver is available , by Christian Loehle; contains a signed-off patch Regzbot command history: introduced: f4c31b07b136839e0fb3026f8a5b6543e3b14d2f , by Joseph Salisbury When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: f4c31b07b136 ("sched: idle: Consolidate the handling of two special cases") Reported-by: Joseph Salisbury <joseph.salisbury@oracle.com> Link: https://lore.kernel.org/r/096b42fa-107f-450d-b3b1-03bcad3f1e04@oracle.com/
94bd01253c3d (v7.0-rc1)	*fsnotify concurrent inotify watch add/remove slowdown* by Chengfeng Lin Earliest & latest activity: & . All known activities: Re: [REGRESSION] fsnotify: concurrent inotify watch add/remove slows after 94bd01253c3d , by Chengfeng Lin Re: [REGRESSION] fsnotify: concurrent inotify watch add/remove slows after 94bd01253c3d , by Jan Kara fsnotify: concurrent inotify watch add/remove slows after 94bd01253c3d , by Chengfeng Lin Regzbot command history: summary: fsnotify concurrent inotify watch add/remove slowdown , by Chengfeng Lin introduced: 94bd01253c3d , by Chengfeng Lin When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 94bd01253c3d ("fsnotify: Track inode connectors for a superblock") Reported-by: Chengfeng Lin <lin2530632123@gmail.com> Link: https://lore.kernel.org/r/CANGjgd=RwMy=29OYG14b6kkoF1uBHz67jTGge5Nubb-XemMvBg@mail.gmail.com/
df4148a5a3cf (v7.1-rc1)	*snd_hda_intel: 15s audio resume delay on AMD Conexant SN6140* by Demon Player Earliest & latest activity: & . All known activities: Re: 回复: 回复: [REGRESSION] snd_hda_intel: 15s audio resume delay on AMD Conexant SN6140 , by Mario Limonciello 回复: 回复: [REGRESSION] snd_hda_intel: 15s audio resume delay on AMD Conexant SN6140 , by Demon Player snd_hda_intel: 15s audio resume delay on AMD Conexant SN6140 , by Demon Player Regzbot command history: duplicate: https://gitlab.freedesktop.org/drm/amd/-/work_items/5529 , by Thorsten Leemhuis summary: snd_hda_intel: 15s audio resume delay on AMD Conexant SN6140 , by Thorsten Leemhuis introduced: df4148a5a3cf , by Thorsten Leemhuis introduced: v7.0.14..v7.1-rc1 , by Demon Player When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: df4148a5a3cf ("ASoC: Add DMIC support for the AMD RPL platform") Reported-by: Demon Player <DemonPlayer0@outlook.com> Link: https://lore.kernel.org/r/MWHPR04MB102982652A66D828B734EBC4C92CF2@MWHPR04MB10298.namprd04.prod.outlook.com/
fee50077656 (v6.19-rc6)	*amdgpu carrizo: no display signal after modeset* by Jaak Ristioja and Jaak Ristioja Earliest & latest activity: & . Noteworthy: [1]. [1]: amdgpu carrizo: no display signal after modeset , by Salvatore Bonaccorso Latest five known activities: drm/amd, issue 5531: new comment (#10) , by Jaak Ristioja [via dup] drm/amd, issue 5531: new comment (#9) , by Jaak Ristioja [via dup] drm/amd, issue 5531: new comment (#8) , by Jaak Ristioja [via dup] drm/amd, issue 5531: new comment (#8) , by Jaak Ristioja [via dup] drm/amd, issue 5531: new comment (#7) , by Dianne Skoll [via dup] Regzbot command history: duplicate: https://gitlab.freedesktop.org/drm/amd/-/work_items/5531 , by Thorsten Leemhuis from: Jaak Ristioja <jaak@ristioja.ee> , by Thorsten Leemhuis introduced: fee50077656 , by Thorsten Leemhuis relatebrief: https://bugs.debian.org/1139950 , by Salvatore Bonaccorso introduced: ae5b1d291c814a2884c3d54a56e83bc99052b1eb , by Salvatore Bonaccorso When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: fee50077656 ("drm/amd/display: Bump the HDMI clock to 340MHz") Reported-by: Jaak Ristioja <jaak@ristioja.ee> Link: https://lore.kernel.org/r/178198613176.3658222.16247101620976737948@eldamar.lan/ Reported-by: Jaak Ristioja <jotik> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/5531
cac1db8c3aad (v6.17-rc1)	*mm/mprotect: shared-dirty base-page toggle slower since v6.17* by Chengfeng Lin Earliest & latest activity: & . Latest five known activities: Re: [REGRESSION] mm/mprotect: shared-dirty base-page toggle slower since v6.17 , by Chengfeng Lin Re: [REGRESSION] mm/mprotect: shared-dirty base-page toggle slower since v6.17 , by Pedro Falcato Re: [REGRESSION] mm/mprotect: shared-dirty base-page toggle slower since v6.17 , by Dev Jain Re: [REGRESSION] mm/mprotect: shared-dirty base-page toggle slower since v6.17 , by Chengfeng Lin Re: [REGRESSION] mm/mprotect: shared-dirty base-page toggle slower since v6.17 , by Dev Jain Regzbot command history: introduced: cac1db8c3aad97d6ffb56ced8868d6cbbbd2bfbe , by Chengfeng Lin introduced: v6.16..v6.17 , by Chengfeng Lin When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: cac1db8c3aad ("mm: optimize mprotect() by PTE batching") Reported-by: Chengfeng Lin <chengfenglin@stu.xmu.edu.cn> Link: https://lore.kernel.org/r/7c9eeb21.1c04f.19efaacbb2f.Coremail.chengfenglin@stu.xmu.edu.cn/
b520c4eef83d (v7.1-rc1)	*commit b520c4eef83d ("block: split bio_alloc_bioset more clearly into a fast and slowpath") causes fsync to fail with pmem* by Sven-Hendrik Haase Earliest & latest activity: & . Noteworthy: [fix incoming]. Fix incoming: virtio-pmem: allocate flush bio from a driver-private bio_set All known activities: Re: [REGRESSION] commit b520c4eef83d ("block: split bio_alloc_bioset more clearly into a fast and slowpath") causes fsync to fail with pmem , by Christoph Hellwig Re: [REGRESSION] commit b520c4eef83d ("block: split bio_alloc_bioset more clearly into a fast and slowpath") causes fsync to fail with pmem , by Sven-Hendrik Haase Re: [REGRESSION] commit b520c4eef83d ("block: split bio_alloc_bioset more clearly into a fast and slowpath") causes fsync to fail with pmem , by Keith Busch commit b520c4eef83d ("block: split bio_alloc_bioset more clearly into a fast and slowpath") causes fsync to fail with pmem , by Sven-Hendrik Haase Regzbot command history: note: '447cfed6d700' in 'mainline' contains a 'Fixes:' tag for the culprit of this regression , by Joseph Qi note: '447cfed6d700' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Joseph Qi fix: virtio-pmem: allocate flush bio from a driver-private bio_set , by Thorsten Leemhuis fix: block: try slab allocation in bio_alloc_bioset() before mempool , by Thorsten Leemhuis note: '67807fbaf127' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Vasily Gorbik note: '7b03c93d2beb' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Christoph Hellwig note: 'b5129bda5bbc' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Christoph Hellwig introduced: b520c4eef83d , by Sven-Hendrik Haase
64c79dfbc458 (v6.10-rc1)	*serial: 8250: concurrent open of UARTs sharing an IRQ triggers "Unbalanced enable for IRQ 3"* by Wang Zhaolong Earliest & latest activity: & . Noteworthy: [1], [2], [3], [4], [5], [6], [fix incoming]. [1]: [PATCH] serial: 8250: serialize shared IRQ startup , by Wang Zhaolong (monitored) [2]: [PATCH v4] serial: 8250: fix use-after-free in IRQ chain handling [implicit due to Link/Closes tag] , by Qiliang Yuan (monitored) [3]: [PATCH v5] serial: 8250: fix use-after-free in IRQ chain handling [implicit due to Link/Closes tag] , by Qiliang Yuan (monitored) [4]: [PATCH v6] serial: 8250: fix use-after-free in IRQ chain handling [implicit due to Link/Closes tag] , by Qiliang Yuan (monitored) [5]: [PATCH v7] serial: 8250: fix use-after-free in IRQ chain handling [implicit due to Link/Closes tag] , by Jing Wu (monitored) [6]: [PATCH v8] serial: 8250: fix use-after-free in IRQ chain handling [implicit due to Link/Closes tag] , by Jing Wu (monitored) Fix incoming: serial: 8250: fix use-after-free in IRQ chain handling Latest five known activities: Re: [PATCH v6] serial: 8250: fix use-after-free in IRQ chain handling , by Greg KH Re: [PATCH v6] serial: 8250: fix use-after-free in IRQ chain handling , by Wang Zhaolong Re: [PATCH v6] serial: 8250: fix use-after-free in IRQ chain handling , by Greg KH Re: [PATCH v2] serial: 8250: fix shared IRQ startup race causing IRQ warning , by Greg KH [PATCH v8] serial: 8250: fix use-after-free in IRQ chain handling , by Jing Wu; contains a signed-off patch Regzbot command history: relate: https://lore.kernel.org/lkml/20260708-bug-221579-8250-shared-irq-race-v8-1-0ae10b073dd9@gmail.com/ [PATCH v8] serial: 8250: fix use-after-free in IRQ chain handling [implicit due to Link/Closes tag] , by Jing Wu relate: https://lore.kernel.org/lkml/20260708-bug-221579-8250-shared-irq-race-v7-1-0da8d89f6072@gmail.com/ [PATCH v7] serial: 8250: fix use-after-free in IRQ chain handling [implicit due to Link/Closes tag] , by Jing Wu relate: https://lore.kernel.org/lkml/20260707-bug-221579-8250-shared-irq-race-v6-1-f8c499a90bdd@gmail.com/ [PATCH v6] serial: 8250: fix use-after-free in IRQ chain handling [implicit due to Link/Closes tag] , by Qiliang Yuan relate: https://lore.kernel.org/lkml/20260624-bug-221579-8250-shared-irq-race-v5-1-15d841f89e1e@gmail.com/ [PATCH v5] serial: 8250: fix use-after-free in IRQ chain handling [implicit due to Link/Closes tag] , by Qiliang Yuan fix: serial: 8250: fix use-after-free in IRQ chain handling , by Thorsten Leemhuis relate: https://lore.kernel.org/lkml/20260529-bug-221579-8250-shared-irq-race-v4-1-cfda63b4420f@gmail.com/ [PATCH v4] serial: 8250: fix use-after-free in IRQ chain handling [implicit due to Link/Closes tag] , by Qiliang Yuan relate: https://lore.kernel.org/all/20260527092052.2086342-1-wangzhaolong@fnnas.com/ , by Thorsten Leemhuis summary: serial: 8250: concurrent open of UARTs sharing an IRQ triggers "Unbalanced enable for IRQ 3" , by Thorsten Leemhuis introduced: 64c79dfbc458 , by Thorsten Leemhuis
165573e41f2f (v7.0-rc3)	*tcp: secure_seq: significant TCP performance regression (QPS drop)* by xietangxin Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH net] netfilter: nf_nat_masquerade: recalculate TCP TS offset when port is randomized , by xietangxin (monitored) Fix incoming: netfilter: nf_nat_masquerade: recalculate TCP TS offset when port is randomized Latest five known activities: Re: [PATCH net] netfilter: nf_nat_masquerade: recalculate TCP TS offset when port is randomized , by Florian Westphal Re: [PATCH net] netfilter: nf_nat_masquerade: recalculate TCP TS offset when port is randomized , by xietangxin Re: [PATCH net] netfilter: nf_nat_masquerade: recalculate TCP TS offset when port is randomized , by Florian Westphal Re: [PATCH net] netfilter: nf_nat_masquerade: recalculate TCP TS offset when port is randomized , by xietangxin Re: [PATCH net] netfilter: nf_nat_masquerade: recalculate TCP TS offset when port is randomized , by Florian Westphal Regzbot command history: note: https://lore.kernel.org/all/20260629093408.3927103-1-xietangxin@h-partners.com/ [PATCH net v3] netfilter: nf_nat: recalculate TCP TS offset after SNAT port rewrite [implicit due to link] , by xietangxin note: https://lore.kernel.org/all/20260629093408.3927103-1-xietangxin@h-partners.com/ [PATCH net v2] netfilter: nf_nat: recalculate TCP TS offset when snat change sport [implicit due to link] , by xietangxin relate: https://lore.kernel.org/all/20260629093408.3927103-1-xietangxin@h-partners.com/ , by Thorsten Leemhuis fix: netfilter: nf_nat_masquerade: recalculate TCP TS offset when port is randomized , by Thorsten Leemhuis summary: tcp: secure_seq: significant TCP performance regression (QPS drop) , by Thorsten Leemhuis introduced: 165573e41f2f66ef98940cf65f838b2cb575d9d1 , by Thorsten Leemhuis
previous cycle (v7.1..v7.2), unknown culprit, with activity in the past three weeks
v7.1..v7.2	*/proc/stat idle time exceeds wall clock since v7.2* by Ahmed Shaltout Earliest & latest activity: & . Latest five known activities: Re: [REGRESSION] /proc/stat idle time exceeds wall clock since v7.2 , by Frederic Weisbecker Re: [REGRESSION] /proc/stat idle time exceeds wall clock since v7.2 , by Ahmed Shaltout Re: [REGRESSION] /proc/stat idle time exceeds wall clock since v7.2 , by Frederic Weisbecker Re: [REGRESSION] /proc/stat idle time exceeds wall clock since v7.2 , by Ahmed Shaltout Re: [REGRESSION] /proc/stat idle time exceeds wall clock since v7.2 , by Frederic Weisbecker Regzbot command history: note: https://lore.kernel.org/all/E76BE609-83E4-4FB6-88B8-191F7816EFD6@gmail.com/ Re: [PATCH] sched/cputime: Don't account idle time twice after dyntick-idle [implicit due to link] , by Thorsten Leemhuis introduced: v7.1..v7.2 , by Ahmed Shaltout When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Reported-by: Ahmed Shaltout <ahmedshaltout.payment@gmail.com> Link: https://lore.kernel.org/r/E76BE609-83E4-4FB6-88B8-191F7816EFD6@gmail.com/
older cycles (..v7.1), unknown culprit, with activity in the past three weeks
v6.18..v7.1	*Subject: [REGRESSION] mt7921e: ~20% lower throughput on first association after boot (7.1/7.2), reconnect restores it* by Георгий Беридзе Earliest & latest activity: . All known activities: Subject: [REGRESSION] mt7921e: ~20% lower throughput on first association after boot (7.1/7.2), reconnect restores it , by Георгий Беридзе Regzbot command history: introduced: v6.18..v7.1 , by Георгий Беридзе When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Reported-by: Георгий Беридзе <game.advencher229@gmail.com> Link: https://lore.kernel.org/r/CAEhAYcrrRyZvNU4i%2BjznPW4jxS1F_s5iH6AMZE4_mVgLbtAhXQ@mail.gmail.com/
b2d2ad72e06e	*wifi: iwlwifi: BE200: firmware faults* by TSUMUGI-XE Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH iwlwifi-fixes 3/5] wifi: iwlwifi: honor the per-channel 320 MHz regulatory flag [implicit due to Link/Closes tag] , by Miri Korenblit (monitored) Fix incoming: fdd83f3ad06a ("wifi: iwlwifi: honor the per-channel 320 MHz regulatory flag") Latest five known activities: Commit fdd83f3ad06a in next , by Emmanuel Grumbach [PATCH iwlwifi-fixes 3/5] wifi: iwlwifi: honor the per-channel 320 MHz regulatory flag , by Miri Korenblit; contains a signed-off patch Status now: CLOSED , by Emmanuel Grumbach bugzilla.kernel.org, issue 221675: new comment (#53) , by Emmanuel Grumbach bugzilla.kernel.org, issue 221675: new comment (#52) , by k.yamaguchi Regzbot command history: fix: fdd83f3ad06a in next referred to this regression , by Emmanuel Grumbach relate: https://lore.kernel.org/linux-wireless/20260930122439.08094e4c344f.Ic0a4bf544fd6ebaf1fc62b40bf463bd289e58cf0@changeid/ [PATCH iwlwifi-fixes 3/5] wifi: iwlwifi: honor the per-channel 320 MHz regulatory flag [implicit due to Link/Closes tag] , by Miri Korenblit summary: wifi: iwlwifi: BE200: firmware faults , by Thorsten Leemhuis introduced: b2d2ad72e06e , by Thorsten Leemhuis
v6.19..v7.0	*Silent SATA read corruption with dma-iommu on AMD 600-series AHCI (6.19 good, 7.0+ bad)* by Mikael Etienne Earliest & latest activity: & . Noteworthy: [1], [2], [patch (SOB)]. [1]: [PATCH 1/2] x86/PCI: Disable enhanced atomics on some AMD PCIe ports [implicit due to Link/Closes tag] , by Mario Limonciello (monitored) [2]: [PATCH v2 1/2] x86/PCI: Disable enhanced atomics on some AMD PCIe ports [implicit due to Link/Closes tag] , by Mario Limonciello (monitored) Latest patch: [PATCH v2 1/2] x86/PCI: Disable enhanced atomics on some AMD PCIe ports , by Mario Limonciello; signed-off-by present Earlier patches: 1 Latest five known activities: Re: [PATCH v2 1/2] x86/PCI: Disable enhanced atomics on some AMD PCIe ports , by Mario Limonciello Re: [PATCH v2 1/2] x86/PCI: Disable enhanced atomics on some AMD PCIe ports , by Bjorn Helgaas Re: [PATCH v2 1/2] x86/PCI: Disable enhanced atomics on some AMD PCIe ports , by Mario Limonciello Re: [PATCH v2 1/2] x86/PCI: Disable enhanced atomics on some AMD PCIe ports , by Bjorn Helgaas Re: [PATCH v2 1/2] x86/PCI: Disable enhanced atomics on some AMD PCIe ports , by Mario Limonciello Regzbot command history: relate: https://lore.kernel.org/lkml/20260908190600.226485-2-mario.limonciello@amd.com/ [PATCH v2 1/2] x86/PCI: Disable enhanced atomics on some AMD PCIe ports [implicit due to Link/Closes tag] , by Mario Limonciello relate: https://lore.kernel.org/lkml/20260908170035.160166-2-mario.limonciello@amd.com/ [PATCH 1/2] x86/PCI: Disable enhanced atomics on some AMD PCIe ports [implicit due to Link/Closes tag] , by Mario Limonciello note: https://lore.kernel.org/linux-ide/178789300872.392066.15963676631650361573@gmail.com/ Re: [PATCH] ahci: force 32-bit DMA for JMicron JMB582/JMB585 [implicit due to link] , by Niklas Cassel note: https://lore.kernel.org/linux-ide/178789300872.392066.15963676631650361573@gmail.com/ Re: [PATCH] ahci: force 32-bit DMA for JMicron JMB582/JMB585 [implicit due to link] , by Niklas Cassel introduced: v6.19..v7.0 , by Mikael Etienne When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Reported-by: Mikael Etienne <mikael1022bzh@gmail.com> Link: https://lore.kernel.org/r/178789300872.392066.15963676631650361573@gmail.com/
v6.18..v6.19	*bcm2835-audio fails to register on vchiq-bus in monolithic kernels since 6.19 (VCHIQ destaging?)* by Martin Wetterwald Earliest & latest activity: . All known activities: bcm2835-audio fails to register on vchiq-bus in monolithic kernels since 6.19 (VCHIQ destaging?) , by Martin Wetterwald Regzbot command history: introduced: v6.18..v6.19 , by Martin Wetterwald When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Reported-by: Martin Wetterwald <martin@wetterwald.eu> Link: https://lore.kernel.org/r/CAFERDQ0FpdVvA5VJxOyRAE_pgxnPVmFx1tkZio5R272j6Bs4tg@mail.gmail.com/
all others with unknown culprit and activity in the past three months
7.1.13..7.2.4	*Sound broken on Cirrus Logic CS8409 / iMac19,1 between 7.1.13 and 7.2.4* by Zachary Hunt Earliest & latest activity: & . All known activities: Re: [REGRESSION] Sound broken on Cirrus Logic CS8409 / iMac19,1 between 7.1.13 and 7.2.4 , by Thorsten Leemhuis Sound broken on Cirrus Logic CS8409 / iMac19,1 between 7.1.13 and 7.2.4 , by Zachary Hunt Regzbot command history: introduced: 7.1.13..7.2.4 , by Zachary Hunt When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Reported-by: Zachary Hunt <1zachhunt@gmail.com> Link: https://lore.kernel.org/r/CAOD3=bOhpz2P2%2BUUNeTsdxXiPtdhFQ%2BjZg-1WQmFAPYchSvhEg@mail.gmail.com/
v7.1..v7.2	*restore from hibernation hangs while btusb boots Intel AX210 (8087:0032)* by David Lomas Earliest & latest activity: & . All known activities: Re: [REGRESSION] 7.2: restore from hibernation hangs while btusb boots Intel AX210 (8087:0032); 7.1 and 6.18 fine , by Thorsten Leemhuis 7.2: restore from hibernation hangs while btusb boots Intel AX210 (8087:0032); 7.1 and 6.18 fine , by David Lomas Regzbot command history: summary: restore from hibernation hangs while btusb boots Intel AX210 (8087:0032) , by David Lomas introduced: v7.1..v7.2 , by David Lomas When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Reported-by: David Lomas <david.s.lomas@gmail.com> Link: https://lore.kernel.org/r/CALjEBWRoqHa=833_dpDxaWpj-tAiAhLuLZBfRQkOkSGgGF5gQA@mail.gmail.com/
v6.18..v7.2	*i915: s2idle lid-open resume leaves eDP panel black until an input event (Raptor Lake; works on 6.18 LTS)* by 徐庆 Earliest & latest activity: & . All known activities: Re: [REGRESSION] i915: s2idle lid-open resume leaves eDP panel black until an input event (Raptor Lake; works on 6.18 LTS) , by Jani Nikula i915: s2idle lid-open resume leaves eDP panel black until an input event (Raptor Lake; works on 6.18 LTS) , by 徐庆 Regzbot command history: introduced: v6.18..v7.2 , by 徐庆 When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Reported-by: 徐庆 <965456495@qq.com> Link: https://lore.kernel.org/r/tencent_8D7EB01E00F5CD0928A0F70A451C586E0608@qq.com/
v6.16..v6.17	*futex: private hash can stay on the shared atomic refcount indefinitely after auto-scaling* by Nikita Taranov Earliest & latest activity: & . Noteworthy: [patch]. Latest patch: Re: futex: private hash can stay on the shared atomic refcount indefinitely after auto-scaling , by Sebastian Andrzej Siewior; simple patch Latest five known activities: Re: futex: private hash can stay on the shared atomic refcount indefinitely after auto-scaling , by Sebastian Andrzej Siewior Re: futex: private hash can stay on the shared atomic refcount indefinitely after auto-scaling , by Nikita Taranov Re: futex: private hash can stay on the shared atomic refcount indefinitely after auto-scaling , by Sebastian Andrzej Siewior; contains a simple patch Re: futex: private hash can stay on the shared atomic refcount indefinitely after auto-scaling , by Nikita Taranov Re: futex: private hash can stay on the shared atomic refcount indefinitely after auto-scaling , by Nikita Taranov Regzbot command history: introduced: v6.16..v6.17 , by Nikita Taranov When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Reported-by: Nikita Taranov <nickita.taranov@gmail.com> Link: https://lore.kernel.org/r/20260823150046.204417-1-nickita.taranov@gmail.com/
818bebeb63dd..531ed942bb0d	*mainline/master: (build) in arch/x86/include/generated/asm/cpufeaturemasks.h (arch/x86/Make...* by KernelCI bot Earliest & latest activity: & . Noteworthy: [1]. [1]: mainline/master: (build) in arch/x86/include/generated/asm/cpufeaturemasks.h (arch/x86/Make... , by KernelCI bot All known activities: Re: [REGRESSION] mainline/master: (build) in arch/x86/include/generated/asm/cpufeaturemasks.h (arch/x86/Make... , by Thorsten Leemhuis mainline/master: (build) in arch/x86/include/generated/asm/cpufeaturemasks.h (arch/x86/Make... , by KernelCI bot Regzbot command history: relatebrief: https://d.kernelci.org/i/maestro:4f457c5cde619e65f938d53b68735abd5858719f , by KernelCI bot introduced: 818bebeb63dd6bf5f4e07e145f6cdbace520a34c..531ed942bb0df04f6747983fecdedce76a22d07f , by KernelCI bot When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Reported-by: KernelCI bot <bot@kernelci.org> Link: https://lore.kernel.org/r/178733874460.1338.14907565015998697320@kernelci.org/
b126f6f5940f..5808ac188949	*mainline/master: (build) in arch/x86/include/generated/asm/cpufeaturemasks.h (/tmp/kci/linu...* by KernelCI bot Earliest & latest activity: . Noteworthy: [1]. [1]: mainline/master: (build) in arch/x86/include/generated/asm/cpufeaturemasks.h (/tmp/kci/linu... , by KernelCI bot All known activities: mainline/master: (build) in arch/x86/include/generated/asm/cpufeaturemasks.h (/tmp/kci/linu... , by KernelCI bot Regzbot command history: relatebrief: https://d.kernelci.org/i/maestro:e019eff33641f280144d13719cbbf59eb379327c , by KernelCI bot introduced: b126f6f5940f614cc06bba61c77dec2d75e8ceaf..5808ac188949d7b49ed9e51f1ffcd096cac57006 , by KernelCI bot When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Reported-by: KernelCI bot <bot@kernelci.org> Link: https://lore.kernel.org/r/178711194407.380.4108589457572337694@kernelci.org/
a98db518dde2..c376a3456d8b (within v6.12-rc3..v6.13-rc1)	*GPU passes into VM improperly after c376a3456d8b or a98db518dde2* by 70sp Earliest & latest activity: & . Noteworthy: [1], [patch]. [1]: Re: [REGRESSION] GPU passes into VM improperly after c376a3456d8b or a98db518dde2 , by Baolu Lu (monitored) Latest patch: Re: [REGRESSION] GPU passes into VM improperly after c376a3456d8b or a98db518dde2 , by Baolu Lu; simple patch Earlier patches: 1 Latest five known activities: Re: [REGRESSION] GPU passes into VM improperly after c376a3456d8b or a98db518dde2 , by Baolu Lu Re: [REGRESSION] GPU passes into VM improperly after c376a3456d8b or a98db518dde2 , by 70sp Re: [REGRESSION] GPU passes into VM improperly after c376a3456d8b or a98db518dde2 , by Baolu Lu Re: [REGRESSION] GPU passes into VM improperly after c376a3456d8b or a98db518dde2 , by 70sp Re: [REGRESSION] GPU passes into VM improperly after c376a3456d8b or a98db518dde2 , by Baolu Lu Regzbot command history: relate: https://lore.kernel.org/lkml/56ce85d5-e0b9-407c-9a86-708111a8a509@linux.intel.com/ , by Thorsten Leemhuis introduced: a98db518dde246e01ead53617dc0a30d6aaa3752..c376a3456d8bef43ec556a98c0a04c35086c2737 , by 70sp When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Reported-by: 70sp <70sp@protonmail.com> Link: https://lore.kernel.org/r/HYhMd0Klo0XE_yiVY7XmsgyKKFDwKHfKRy22KrycLcYd0V_ykA4xdbBMJXkA07YX3os6qK-NhMIVi6ITo-CkNIIF0e-GcI0UwwZmdDhAJ0I=@protonmail.com/
v7.0.14..v7.1-rc1	*回复: [REGRESSION] snd_hda_intel: 15s audio resume delay on AMD Conexant SN6140* by Demon Player, Demon Player, and Mingyou Chen Earliest & latest activity: & . Latest five known activities: drm/amd, issue 5529: new comment (#38) , by Mario Limonciello [via dup] drm/amd, issue 5529: new comment (#37) , by Mingyou Chen [via dup] drm/amd, issue 5529: new comment (#36) , by Mario Limonciello [via dup] drm/amd, issue 5529: new comment (#35) , by Mingyou Chen [via dup] drm/amd, issue 5529: new comment (#34) , by Mario Limonciello [via dup] Regzbot command history: duplicate: https://gitlab.freedesktop.org/drm/amd/-/issues/5529 [implicit via duplicate] , by Thorsten Leemhuis introduced: v7.0.14..v7.1-rc1 , by Demon Player When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Reported-by: Demon Player <DemonPlayer0@outlook.com> Link: https://lore.kernel.org/r/MWHPR04MB1029801AFD77D790D33C53E1592CF2@MWHPR04MB10298.namprd04.prod.outlook.com/ Reported-by: Demon Player <DemonPlayer> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/5529 Reported-by: Mingyou Chen <qby140326@gmail.com> Link: https://lore.kernel.org/r/20260807091047.9264-1-qby140326@gmail.com/
on back burner with activity in the past six months
none known by regzbot

[compiled by regzbot on 2026-10-07 11:02:51 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

[recently 113 events occurred that regzbot was unable to handle]