Linux kernel regression status

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

current cycle (v7.1.. aka v7.2-rc), culprit identified
334f3f6d7a16 (v7.2-rc1)	*powerpc/entry: indefinitely warnings and system never completes boot* by Venkat Rao Bagalkote Earliest & latest activity: & . Noteworthy: [1], [patch]. [1]: [PATCH] powerpc/entry: Use hard_irq_disable() in arch_interrupt_exit_prepare() [implicit due to Link/Closes tag] , by Mukesh Kumar Chaurasiya (IBM) (monitored) Latest patch: Re: [PATCH] powerpc/entry: Use hard_irq_disable() in arch_interrupt_exit_prepare() , by Mukesh Kumar Chaurasiya; simple patch Earlier patches: 1 Latest five known activities: Re: [PATCH] powerpc/entry: Use hard_irq_disable() in arch_interrupt_exit_prepare() , by Mukesh Kumar Chaurasiya; contains a simple patch Re: [PATCH] powerpc/entry: Use hard_irq_disable() in arch_interrupt_exit_prepare() , by Mukesh Kumar Chaurasiya Re: [PATCH] powerpc/entry: Use hard_irq_disable() in arch_interrupt_exit_prepare() , by Shrikanth Hegde Re: [PATCH] powerpc/entry: Use hard_irq_disable() in arch_interrupt_exit_prepare() , by Venkat Rao Bagalkote Re: [PATCH] powerpc/entry: Use hard_irq_disable() in arch_interrupt_exit_prepare() , by Christophe Leroy (CS GROUP) Regzbot command history: relate: https://lore.kernel.org/lkml/20260812152035.1661781-1-mkchauras@gmail.com/ [PATCH] powerpc/entry: Use hard_irq_disable() in arch_interrupt_exit_prepare() [implicit due to Link/Closes tag] , by Mukesh Kumar Chaurasiya (IBM) summary: powerpc/entry: indefinitely warnings and system never completes boot , by Thorsten Leemhuis introduced: 334f3f6d7a1660 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 334f3f6d7a16 ("powerpc/entry: Disable interrupts before irqentry_exit") Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com> Link: https://lore.kernel.org/r/6f9bfb0f-b14c-468e-bb9f-c157d120d0dc@linux.ibm.com/
0a4bb2abc3e5 (v7.2-rc6)	*i2c: designware: ThinkPad touchpad broke* by Thorsten Leemhuis Earliest & latest activity: & . Noteworthy: [1], [patch (SOB)]. [1]: [PATCH] Revert "i2c: designware: defer probe if child GpioInt controllers are not bound" [implicit due to Link/Closes tag] , by Hardik Prakash (monitored) Latest patch: [PATCH] Revert "i2c: designware: defer probe if child GpioInt controllers are not bound" , by Hardik Prakash; signed-off-by present Latest five known activities: Re: [PATCH] Revert "i2c: designware: defer probe if child GpioInt controllers are not bound" , by Andi Shyti Re: [PATCH] Revert "i2c: designware: defer probe if child GpioInt controllers are not bound" , by Mario Limonciello Re: [PATCH] Revert "i2c: designware: defer probe if child GpioInt controllers are not bound" , by Thorsten Leemhuis Re: i2c designware change broke touchpad of a thinkpad , by Hardik Prakash [PATCH] Revert "i2c: designware: defer probe if child GpioInt controllers are not bound" , by Hardik Prakash; contains a signed-off patch Regzbot command history: relate: https://lore.kernel.org/lkml/20260814100719.9548-1-hardikprakash.official@gmail.com/ [PATCH] Revert "i2c: designware: defer probe if child GpioInt controllers are not bound" [implicit due to Link/Closes tag] , by Hardik Prakash note: https://lore.kernel.org/all/b4a4eadb-282f-464c-843a-19d415a34d0c@leemhuis.info/ Re: [PATCH 7.1 326/438] i2c: designware: defer probe if child GpioInt controllers are not bound [implicit due to link] , by Thorsten Leemhuis summary: i2c: designware: ThinkPad touchpad broke , by Thorsten Leemhuis introduced: 0a4bb2abc3e56d , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 0a4bb2abc3e5 ("i2c: designware: defer probe if child GpioInt controllers are not bound") Reported-by: Thorsten Leemhuis <linux@leemhuis.info> Link: https://lore.kernel.org/r/b4a4eadb-282f-464c-843a-19d415a34d0c@leemhuis.info/
610fa91d9863 (v7.2-rc1)	*PCI: imx6: PCI link creation fails on Apalis iMX6* by Leonardo Costa Earliest & latest activity: & . Noteworthy: [1], [2], [3], [4], [5], [6], [7], [fix incoming]. [1]: Re: [PATCH v2] PCI: imx6: Fix i.MX6Q/DL boot hang by separating PHY power and reference clock control [implicit due to Link/Closes tag] , by Francesco Dolcini (monitored) [2]: [PATCH v3] PCI: imx6: Fix i.MX6Q/DL boot hang caused by improper PHY power sequencing [implicit due to Link/Closes tag] , by hongxing.zhu (monitored) [3]: [PATCH v4] PCI: imx6: Fix i.MX6Q/DL boot hang caused by improper PHY power sequencing [implicit due to Link/Closes tag] , by hongxing.zhu (monitored) [4]: [PATCH v5] PCI: imx6: Fix i.MX6Q/DL boot hang caused by improper PHY power sequencing [implicit due to Link/Closes tag] , by hongxing.zhu (monitored) [5]: mainline/master: PCI link creation fails on Apalis iMX6 [implicit due to Link/Closes tag] , by Leonardo Costa (monitored) [6]: [PATCH v2] PCI: imx6: Move clock enable after core reset assertion , by hongxing.zhu (monitored) [7]: [PATCH v1] PCI: imx6: Move clock enable after core reset assertion [implicit due to Link/Closes tag] , by hongxing.zhu (monitored) Fix incoming: PCI: imx6: Move clock enable after core reset assertion Latest five known activities: Re: [PATCH v2] PCI: imx6: Move clock enable after core reset assertion , by sashiko-bot Re: [PATCH v2] PCI: imx6: Move clock enable after core reset assertion , by sashiko-bot [PATCH v2] PCI: imx6: Move clock enable after core reset assertion , by hongxing.zhu; contains a signed-off patch [PATCH v2] PCI: imx6: Move clock enable after core reset assertion , by hongxing.zhu; contains a signed-off patch RE: [PATCH v1] PCI: imx6: Move clock enable after core reset assertion , by Hongxing Zhu (OSS) Regzbot command history: relate: https://lore.kernel.org/all/20260813095003.356062-1-hongxing.zhu@oss.nxp.com/ , by Thorsten Leemhuis fix: PCI: imx6: Move clock enable after core reset assertion , by Thorsten Leemhuis summary: PCI: imx6: PCI link creation fails on Apalis iMX6 , by Thorsten Leemhuis introduced: 610fa91d9863 , by Thorsten Leemhuis relate: https://lore.kernel.org/lkml/20260813095003.356062-1-hongxing.zhu@oss.nxp.com/ [PATCH v2] PCI: imx6: Move clock enable after core reset assertion [implicit due to Link/Closes tag] , by hongxing.zhu relate: https://lore.kernel.org/lkml/20260813082900.270003-1-hongxing.zhu@oss.nxp.com/ [PATCH v1] PCI: imx6: Move clock enable after core reset assertion [implicit due to Link/Closes tag] , by hongxing.zhu summary: PCI: imx6: PCIe is not longer working after boot regression was fixed , by Thorsten Leemhuis introduced: 7678e81498e2 , by Thorsten Leemhuis relate: https://lore.kernel.org/lkml/bl7i3obu2clzsgeoct2a4mtfhv6typcjdqmgneropf3hpgwve6@n2m5uhlduw57/ mainline/master: PCI link creation fails on Apalis iMX6 [implicit due to Link/Closes tag] , by Leonardo Costa fix: 7678e81498e2 [implicit, due to a Link/Closes tag] , by Richard Zhu fixed: 'fix' commit '7678e81498e2' now in 'mainline' , by Richard Zhu fix: 7678e81498e2 in next referred to this regression , by Richard Zhu relate: https://lore.kernel.org/lkml/20260728035159.2702021-1-hongxing.zhu@oss.nxp.com/ [PATCH v5] PCI: imx6: Fix i.MX6Q/DL boot hang caused by improper PHY power sequencing [implicit due to Link/Closes tag] , by hongxing.zhu relate: https://lore.kernel.org/lkml/20260722071030.2504711-1-hongxing.zhu@oss.nxp.com/ [PATCH v4] PCI: imx6: Fix i.MX6Q/DL boot hang caused by improper PHY power sequencing [implicit due to Link/Closes tag] , by hongxing.zhu relate: https://lore.kernel.org/lkml/20260722030935.2328278-1-hongxing.zhu@oss.nxp.com/ [PATCH v3] PCI: imx6: Fix i.MX6Q/DL boot hang caused by improper PHY power sequencing [implicit due to Link/Closes tag] , by hongxing.zhu relate: https://lore.kernel.org/lkml/20260717061024.GA362793@francesco-nb/ Re: [PATCH v2] PCI: imx6: Fix i.MX6Q/DL boot hang by separating PHY power and reference clock control [implicit due to Link/Closes tag] , by Francesco Dolcini summary: PCI: imx6: Apalis iMX6 stopped booting , by Thorsten Leemhuis introduced: 610fa91d9863 , by Thorsten Leemhuis
bee25f97ad24 (v7.2-rc1)	*powerpc: Power9 pseries boot hang* by Venkat Rao Bagalkote Earliest & latest activity: & . Noteworthy: [patch]. Latest patch: Re: [REGRESSION] Power9 pseries boot hang in v7.2-rc6, narrowed to PowerPC GENERIC_ENTRY conversion window , by Mukesh Kumar Chaurasiya; simple patch Latest five known activities: Re: [REGRESSION] Power9 pseries boot hang in v7.2-rc6, narrowed to PowerPC GENERIC_ENTRY conversion window , by Venkat Rao Bagalkote Re: [REGRESSION] Power9 pseries boot hang in v7.2-rc6, narrowed to PowerPC GENERIC_ENTRY conversion window , by Mukesh Kumar Chaurasiya; contains a simple patch Re: [REGRESSION] Power9 pseries boot hang in v7.2-rc6, narrowed to PowerPC GENERIC_ENTRY conversion window , by Mukesh Kumar Chaurasiya Re: [REGRESSION] Power9 pseries boot hang in v7.2-rc6, narrowed to PowerPC GENERIC_ENTRY conversion window , by Venkat Rao Bagalkote Re: [REGRESSION] Power9 pseries boot hang in v7.2-rc6, narrowed to PowerPC GENERIC_ENTRY conversion window , by Shrikanth Hegde Regzbot command history: 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/
516403d4d856 (v7.2-rc1)	*nfs: soft lockup* by Wolfgang Walter Earliest & latest activity: & . Noteworthy: [1], [2], [3], [4], [fix incoming]. [1]: [RFC PATCH] NFSD: Prevent lock owner use-after-free during client teardown [implicit due to Link/Closes tag] , by Chuck Lever (monitored) [2]: [PATCH v2 1/6] NFSD: Prevent lock owner use-after-free during client teardown [implicit due to Link/Closes tag] , by Chuck Lever (monitored) [3]: [PATCH v3 1/9] NFSD: Prevent lock owner use-after-free during client teardown [implicit due to Link/Closes tag] , by Chuck Lever (monitored) [4]: [PATCH v4 1/9] NFSD: Prevent lock owner use-after-free during client teardown [implicit due to Link/Closes tag] , by Chuck Lever (monitored) Fix incoming: 5e2fa29d223a ("NFSD: Prevent lock owner use-after-free during client teardown") Latest five known activities: Commit 5e2fa29d223a in next , by Chuck Lever 5e2fa29d223a, the fix specified through '#regzbot fix:' earlier landed in next , by Chuck Lever Commit 74e5356347c2 in next , by Chuck Lever Re: [PATCH v4 1/9] NFSD: Prevent lock owner use-after-free during client teardown , by Wolfgang Walter Re: [PATCH v4 1/9] NFSD: Prevent lock owner use-after-free during client teardown , by Thorsten Leemhuis Regzbot command history: fix: 5e2fa29d223a in next referred to this regression , by Chuck Lever note: 'fix' commit '5e2fa29d223a' now in 'next' , by Chuck Lever fix: 74e5356347c2 in next referred to this regression , by Chuck Lever introduced: 516403d4d85607 , by Thorsten Leemhuis relate: https://lore.kernel.org/linux-nfs/20260709-cel-v4-1-1d519d9be0cb@kernel.org/ [PATCH v4 1/9] NFSD: Prevent lock owner use-after-free during client teardown [implicit due to Link/Closes tag] , by Chuck Lever relate: https://lore.kernel.org/linux-nfs/20260707-cel-v3-1-7c0cc16fd54f@kernel.org/ [PATCH v3 1/9] NFSD: Prevent lock owner use-after-free during client teardown [implicit due to Link/Closes tag] , by Chuck Lever relate: https://lore.kernel.org/linux-nfs/20260705-cel-v2-1-d88c3b68e8bc@kernel.org/ [PATCH v2 1/6] NFSD: Prevent lock owner use-after-free during client teardown [implicit due to Link/Closes tag] , by Chuck Lever relate: https://lore.kernel.org/linux-nfs/20260703173943.3242873-1-cel@kernel.org/ [RFC PATCH] NFSD: Prevent lock owner use-after-free during client teardown [implicit due to Link/Closes tag] , by Chuck Lever summary: nfs: soft lockup , by Thorsten Leemhuis introduced: 95f9eb19d5e6 , by Thorsten Leemhuis
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: 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; contains a simple patch [via dup] Re: [PATCH v3] PCI: Skip Target Speed quirk on clamped ports with no link , by Aoxtj [via dup] bugzilla.kernel.org, issue 221801: new comment (#16) , by The Linux kernel's regression tracker (Thorsten Leemhuis) bugzilla.kernel.org, issue 221801: new comment (#15) , by The Linux kernel's regression tracker (Thorsten Leemhuis) Re: [PATCH v3] PCI: Skip Target Speed quirk on clamped ports with no link , by Andreas Wild; contains a simple patch [via dup] Regzbot command history: 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
e88098133ed4 (v7.2-rc1)	*wifi: mt76: mt7921: sessions pile up due to self-deadlocks and the machine has to be reset* by Devin Wittmayer Earliest & latest activity: & . Noteworthy: [fix incoming]. Fix incoming: 1f83a8378eb2 ("wifi: mt76: mt7921: refactor regd update to fix recursive mutex deadlock") All known activities: 1f83a8378eb2, the fix specified through '#regzbot fix:' earlier landed in next , by Charlie-cy Wu Re: [PATCH] wifi: mt76: mt7921: refactor regd update to fix recursive mutex deadlock , by Devin Wittmayer Regzbot command history: note: https://lore.kernel.org/linux-wireless/20260804185118.19705-1-lucid_duck@justthetip.ca/ Re: [REGRESSION] mt7925: MLO connectivity silently stalls with 6GHz link active [implicit due to link] , by Thorsten Leemhuis note: https://lore.kernel.org/linux-wireless/20260804185118.19705-1-lucid_duck@justthetip.ca/ wifi fixes that might be good to have in 7.2 final [implicit due to link] , by Thorsten Leemhuis fix: wifi: mt76: mt7921: refactor regd update to fix recursive mutex deadlock , by Thorsten Leemhuis note: 'fix' commit '1f83a8378eb2' now in 'next' , by Charlie-cy Wu summary: wifi: mt76: mt7921: sessions pile up due to self-deadlocks and the machine has to be reset , by Thorsten Leemhuis introduced: e88098133ed4 , by Thorsten Leemhuis note: '1f83a8378eb2' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Charlie-cy Wu
current cycle (v7.1.. aka v7.2-rc), unknown culprit
none known by regzbot
previous cycle (v7.0..v7.1), culprit identified, with activity in the past three months
86aa1ea1f15c (v7.1-rc1)	*ALSA: usb-audio: Logitech PRO X Wireless 046d:0aba playback volume rejected as sticky* by Alexander N. Earliest & latest activity: & . All known activities: Re: [REGRESSION] ALSA: usb-audio: Logitech PRO X Wireless 046d:0aba playback volume rejected as sticky , by Alexander Niemeyer Re: [REGRESSION] ALSA: usb-audio: Logitech PRO X Wireless 046d:0aba playback volume rejected as sticky , by Rong Zhang Re: [REGRESSION] ALSA: usb-audio: Logitech PRO X Wireless 046d:0aba playback volume rejected as sticky , by Takashi Iwai ALSA: usb-audio: Logitech PRO X Wireless 046d:0aba playback volume rejected as sticky , by Alexander N. Regzbot command history: note: '885c22d259c8' in 'mainline' contains a 'Fixes:' tag for the culprit of this regression , by Takashi Iwai note: 'aa2f4addab44' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Rong Zhang note: 'c973e61895db' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Rong Zhang note: 'a8934c2c6dfd' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Takashi Iwai note: '885c22d259c8' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Takashi Iwai introduced: 86aa1ea1f15ce6b56ac1b4c0d9b88a07a5b9bf03 , by Alexander N. When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 86aa1ea1f15c ("ALSA: usb-audio: Do not expose sticky mixers") Reported-by: Alexander N. <adventureFAN@gmx.de> Link: https://lore.kernel.org/r/6262cbbd-d1f2-4c9d-a1c7-9c5d12636f4b@gmx.de/
48fe2cddc85c (v7.1-rc1)	*no TPM device after "tpm_crb: Convert ACPI driver to a platform one"* by Julien Earliest & latest activity: & . Noteworthy: [1], [2], [3], [fix incoming]. [1]: [PATCH v1] ACPI: scan: Avoid registering platform devices with resource overlaps [implicit due to Link/Closes tag] , by Rafael J. Wysocki (monitored) [2]: [PATCH v2] ACPI: scan: Avoid registering platform devices with resource overlaps [implicit due to Link/Closes tag] , by Rafael J. Wysocki (monitored) [3]: [PATCH v3] ACPI: scan: Avoid registering platform devices with resource overlaps [implicit due to Link/Closes tag] , by Rafael J. Wysocki (monitored) Fix incoming: f234fdaae1ca ("ACPI: scan: Avoid registering platform devices with resource overlaps") Latest five known activities: Commit f234fdaae1ca in next , by Rafael J. Wysocki Re: [REGRESSION] no TPM device after "tpm_crb: Convert ACPI driver to a platform one" , by Julien Re: [PATCH v3] ACPI: scan: Avoid registering platform devices with resource overlaps , by Rafael J. Wysocki (Intel) Re: [PATCH v3] ACPI: scan: Avoid registering platform devices with resource overlaps , by Jarkko Sakkinen Re: [REGRESSION] no TPM device after "tpm_crb: Convert ACPI driver to a platform one" , by Jarkko Sakkinen Regzbot command history: fix: f234fdaae1ca in next referred to this regression , by Rafael J. Wysocki relate: https://lore.kernel.org/lkml/12955541.O9o76ZdvQC@rafael.j.wysocki/ [PATCH v3] ACPI: scan: Avoid registering platform devices with resource overlaps [implicit due to Link/Closes tag] , by Rafael J. Wysocki relate: https://lore.kernel.org/lkml/12954206.O9o76ZdvQC@rafael.j.wysocki/ [PATCH v2] ACPI: scan: Avoid registering platform devices with resource overlaps [implicit due to Link/Closes tag] , by Rafael J. Wysocki relate: https://lore.kernel.org/lkml/6299389.lOV4Wx5bFT@rafael.j.wysocki/ [PATCH v1] ACPI: scan: Avoid registering platform devices with resource overlaps [implicit due to Link/Closes tag] , by Rafael J. Wysocki note: 'c041d2be785f' in 'stable/linux-7.1.y' contains a 'Fixes:' tag for the culprit of this regression , by Rafael J. Wysocki note: 'fd1ac8d2bae6' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Rafael J. Wysocki note: '04171ebc4a4e' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Rafael J. Wysocki note: '474836b13ef1' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Rafael J. Wysocki note: 'bca6affd1984' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Rafael J. Wysocki note: '0b430e1cbe9f' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Rafael J. Wysocki note: 'ba8595169a00' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Rafael J. Wysocki note: 'f641b6c1a9cf' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Rafael J. Wysocki note: '500837ab81c8' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Rafael J. Wysocki note: 'ddd33806b891' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Rafael J. Wysocki introduced: 48fe2cddc85c , by Julien
f9a48549a15a (v7.1-rc1)	*btrfs: 22.6% regression of fio.write_iops* by kernel test robot Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH v2] btrfs: replace writeback inhibition xarray with a fixed inline buffer , by Leo Martins (monitored) Fix incoming: 67bd829a14b7 ("btrfs: replace writeback inhibition xarray with a fixed inline buffer") Latest five known activities: Commit 67bd829a14b7 in next , by Leo Martins 67bd829a14b7, the fix specified through '#regzbot fix:' earlier landed in next , by Leo Martins Commit 338a9f142222 in next , by Leo Martins 338a9f142222, the fix specified through '#regzbot fix:' earlier landed in next , by Leo Martins Commit 7a433ed7fc22 in next , by Leo Martins Regzbot command history: fix: 67bd829a14b7 in next referred to this regression , by Leo Martins note: 'fix' commit '67bd829a14b7' now in 'next' , by Leo Martins fix: 338a9f142222 in next referred to this regression , by Leo Martins note: 'fix' commit '338a9f142222' now in 'next' , by Leo Martins fix: 7a433ed7fc22 in next referred to this regression , by Leo Martins note: 'fix' commit '7a433ed7fc22' now in 'next' , by Leo Martins relate: https://lore.kernel.org/all/12d3c3f07b8610ca13b0f3f792d420541afb7b33.1782949130.git.loemra.dev@gmail.com/ , by Thorsten Leemhuis fix: btrfs: replace writeback inhibition xarray with a fixed inline buffer , by Thorsten Leemhuis summary: btrfs: 22.6% regression of fio.write_iops , by Thorsten Leemhuis introduced: f9a48549a15a , by Thorsten Leemhuis
3e7d63037a2b (v7.1-rc1)	*cifs: openat with O_TMPFILE returns -1 ENOENT* by Thorsten Leemhuis Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH] smb/client: return EOPNOTSUPP for unsupported O_TMPFILE , by ChenXiaoSong (monitored) Fix incoming: smb/client: return EOPNOTSUPP for unsupported O_TMPFILE All known activities: Re: [PATCH] smb/client: return EOPNOTSUPP for unsupported O_TMPFILE , by Paulo Alcantara [PATCH] smb/client: return EOPNOTSUPP for unsupported O_TMPFILE , by ChenXiaoSong; contains a signed-off patch Regzbot command history: relate: https://lore.kernel.org/linux-cifs/20260807085806.725742-1-chenxiaosong@chenxiaosong.com/ , by Thorsten Leemhuis fix: smb/client: return EOPNOTSUPP for unsupported O_TMPFILE , by Thorsten Leemhuis summary: cifs: openat with O_TMPFILE returns -1 ENOENT , by Thorsten Leemhuis introduced: 3e7d63037a2b , by Thorsten Leemhuis note: https://lore.kernel.org/linux-cifs/20260807085806.725742-1-chenxiaosong@chenxiaosong.com/ Re: [REGRESSION] cifs: openat with O_TMPFILE returns -1 ENOENT (STATUS_OBJECT_NAME_NOT_FOUND) [implicit due to link] , by ChenXiaoSong note: "[PATCH] smb/client: return EOPNOTSUPP for unsupported O_TMPFILE" contains a 'Fixes:' tag for the culprit of this regression , by ChenXiaoSong
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/
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 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
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 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/
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/
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]. [1]: Re: Bug#1141604: linux-image-6.12.94+deb13-amd64: does not detect ScreenPad on ASUS VivoBook , by Salvatore Bonaccorso Latest five known activities: Re: [PATCH v3 1/2] platform/x86: asus-wmi: adjust screenpad power/brightness handling — regression on non-DUO ScreenPad (ASUS ZenBook UX435EG) , by Denis Benato [via dup] Re: Bug#1141604: linux-image-6.12.94+deb13-amd64: does not detect ScreenPad on ASUS VivoBook , by Thorsten Leemhuis Re: Bug#1141604: linux-image-6.12.94+deb13-amd64: does not detect ScreenPad on ASUS VivoBook , by Denis Benato Re: Bug#1141604: linux-image-6.12.94+deb13-amd64: does not detect ScreenPad on ASUS VivoBook , by Salvatore Bonaccorso Re: Bug#1141604: linux-image-6.12.94+deb13-amd64: does not detect ScreenPad on ASUS VivoBook , by Ilpo Järvinen Regzbot command history: 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 When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 8d95d1f4aa5c ("platform/x86: asus-wmi: fix screenpad brightness range") Reported-by: Denis Benato <denis.benato@linux.dev> Link: https://lore.kernel.org/r/ea9c63d1-4776-49d5-9dc4-6c09498f99c9@linux.dev/ Reported-by: Salvatore Bonaccorso <carnil@debian.org> Link: https://lore.kernel.org/r/178362762638.911488.8564892548331679884@eldamar.lan/
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
older cycles (..v7.0), culprit identified, with activity in the past three months
8c9006283e4b (v6.18-rc1)	*drm/i915/dp: random screen flicker on eDP* by annoy 、 Earliest & latest activity: & . All known activities: drm/i915/kernel, issue 16743: new comment (#4) , by annoy 、 drm/i915/kernel, issue 16743: new comment (#3) , by annoy 、 drm/i915/kernel, issue 16743: new comment (#2) , by Ankit Nautiyal drm/i915/kernel, issue 16743: new comment (#1) , by Mitul Golani drm/i915/kernel, issue 16743: submission , by annoy 、 Regzbot command history: summary: drm/i915/dp: random screen flicker on eDP , by Thorsten Leemhuis introduced: 8c9006283e4b767003b2d11182d6e90f8b184c3d , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 8c9006283e4b ("Revert "drm/i915/dp: Reject HBR3 when sink doesn't support TPS4"") Reported-by: annoy 、 <annoycc> Link: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/16743
12e1480bcb49 (v3.13-rc1)	*clocksource: sun4i: boot hang on Allwinner D1* by Indrek Kruusa Earliest & latest activity: & . Noteworthy: [fix incoming]. Fix incoming: 97988070f67b ("clocksource/drivers/timer-sun4i: Advertise a real minimum delta") Latest five known activities: Commit 97988070f67b in next , by Felix Yan Re: [PATCH] clocksource/drivers/timer-sun4i: Advertise a real minimum delta , by Jernej Škrabec Re: [PATCH] clocksource/drivers/timer-sun4i: Advertise a real minimum delta , by Indrek Kruusa Re: [PATCH] clocksource/drivers/timer-sun4i: Advertise a real minimum delta , by sashiko-bot [PATCH] clocksource/drivers/timer-sun4i: Advertise a real minimum delta , by Felix Yan; contains a signed-off patch Regzbot command history: fix: 97988070f67b in next referred to this regression , by Felix Yan fix: 97988070f67b in next referred to this regression , by Felix Yan summary: clocksource: sun4i: boot hang on Allwinner D1 , by Thorsten Leemhuis introduced: 12e1480bcb49 , by Thorsten Leemhuis note: "[PATCH] clocksource/drivers/timer-sun4i: Advertise a real minimum delta" contains a 'Fixes:' tag for the culprit of this regression , by Felix Yan
7029acd8a950 (v6.13-rc1)	*io_uring MSG_RING SEND_FD fixed-file installation slowdown* by Chengfeng Lin Earliest & latest activity: . All known activities: io_uring/rsrc: MSG_RING SEND_FD fixed-file installation slowdown after 7029acd8a950 , by Chengfeng Lin Regzbot command history: 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/
c0f691388992 (v6.16-rc2)	*usb/intel_idle: ehci fails to initialize on intel s1200btl* by Julian Silver Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH v1] intel_idle: Avoid using deep idle states during initialization [implicit due to Link/Closes tag] , by Rafael J. Wysocki (monitored) Fix incoming: 9eadbed788df ("intel_idle: Avoid using deep idle states during initialization") Latest five known activities: Commit 9eadbed788df in next , by Rafael J. Wysocki Re: [REGRESSION] usb controller fails to initialize on intel s1200btl , by Julian Silver Re: [REGRESSION] usb controller fails to initialize on intel s1200btl , by Rafael J. Wysocki (Intel) [PATCH v1] intel_idle: Avoid using deep idle states during initialization , by Rafael J. Wysocki; contains a signed-off patch Re: [REGRESSION] usb controller fails to initialize on intel s1200btl , by Julian Silver Regzbot command history: fix: 9eadbed788df in next referred to this regression , by Rafael J. Wysocki relate: https://lore.kernel.org/lkml/5120454.31r3eYUQgx@rafael.j.wysocki/ [PATCH v1] intel_idle: Avoid using deep idle states during initialization [implicit due to Link/Closes tag] , by Rafael J. Wysocki summary: usb/intel_idle: ehci fails to initialize on intel s1200btl , by Thorsten Leemhuis introduced: c0f691388992c70 , by Thorsten Leemhuis introduced: c0f691388992c708436ab5f6e810865be6ddf5c6 , by Julian Silver
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 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/
e716edafedad (v7.0-rc5)	*HID: multitouch: palm rejection broke* by mayhemandcoffee Earliest & latest activity: & . Noteworthy: [1], [patch (SOB)]. [1]: [PATCH] HID: multitouch: Add report ID mismatch quirk for ASUS ROG Z13 Folio [implicit due to Link/Closes tag] , by Lovekesh Solanki (monitored) Latest patch: [PATCH] HID: multitouch: Add report ID mismatch quirk for ASUS ROG Z13 Folio , by Lovekesh Solanki; signed-off-by present Earlier patches: 1, 2 Latest five known activities: Re: [PATCH] HID: multitouch: Add report ID mismatch quirk for ASUS ROG Z13 Folio , by sashiko-bot [PATCH] HID: multitouch: Add report ID mismatch quirk for ASUS ROG Z13 Folio , by Lovekesh Solanki; contains a signed-off patch bugzilla.kernel.org, issue 221774: new comment (#17) , by mayhemandcoffee bugzilla.kernel.org, issue 221774: new comment (#16) , by Lovekesh Solanki bugzilla.kernel.org, issue 221774: new comment (#15) , by mayhemandcoffee Regzbot command history: relate: https://lore.kernel.org/lkml/20260804202031.75738-1-lovekeshsolanki00@gmail.com/ [PATCH] HID: multitouch: Add report ID mismatch quirk for ASUS ROG Z13 Folio [implicit due to Link/Closes tag] , by Lovekesh Solanki summary: HID: multitouch: palm rejection broke , by Thorsten Leemhuis introduced: e716edafedad49 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: e716edafedad ("HID: multitouch: Check to ensure report responses match the request") Reported-by: mayhemandcoffee Link: https://bugzilla.kernel.org/show_bug.cgi?id=221774
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
8f5b7e2bec1c (v6.16-rc5)	*usb: hub: total system freeze after running adb* by Slavik Dev Earliest & latest activity: & . All known activities: Re: [REGRESSION][BISECTED] usb: hub: total system freeze after running adb , by Michal Pecio Re: [REGRESSION][BISECTED] usb: hub: total system freeze after running adb , by Slavik Dev Regzbot command history: summary: usb: hub: total system freeze after running adb , by Thorsten Leemhuis introduced: 8f5b7e2bec1c , by Thorsten Leemhuis note: '60c929c85e2d' in 'stable/linux-6.1.y' contains a 'Fixes:' tag for the culprit of this regression , by Mathias Nyman note: '71f5c98d2931' in 'stable/linux-6.6.y' contains a 'Fixes:' tag for the culprit of this regression , by Mathias Nyman note: 'e11359640090' in 'stable/linux-6.12.y' contains a 'Fixes:' tag for the culprit of this regression , by Mathias Nyman note: 'f7d1af38b3f1' in 'stable/linux-6.15.y' contains a 'Fixes:' tag for the culprit of this regression , by Mathias Nyman note: 'c72cd4c92e06' in 'stable/linux-5.4.y' contains a 'Fixes:' tag for the culprit of this regression , by Mathias Nyman note: '0f94efa7f265' in 'stable/linux-5.10.y' contains a 'Fixes:' tag for the culprit of this regression , by Mathias Nyman note: '1a6fee8d8295' in 'stable/linux-5.15.y' contains a 'Fixes:' tag for the culprit of this regression , by Mathias Nyman note: 'a49e1e2e785f' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Mathias Nyman When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 8f5b7e2bec1c ("usb: hub: fix detection of high tier USB3 devices behind suspended hubs") Reported-by: Slavik Dev <developer.slavik@gmail.com> Link: https://lore.kernel.org/r/CAGQo=TJXef-QzbkFEpTcJ138j0k6WYnV4=tNY8Q7s3U7DUOY%2BQ@mail.gmail.com/
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/
079afb081c42 (v6.16-rc1)	*io_uring scalar futex wait/wake slowdown* by Chengfeng Lin Earliest & latest activity: & . Noteworthy: [fix incoming]. Fix incoming: 4d327bbd1cd2 ("io_uring/futex: only mark private futex waits as inflight") Latest five known activities: Commit 4d327bbd1cd2 in next , by Jens Axboe Commit 73e701909747 in next , by Jens Axboe Re: [REGRESSION] io_uring/futex: scalar wait/wake slowdown after 079afb081c42 , by Chengfeng Lin Re: [REGRESSION] io_uring/futex: scalar wait/wake slowdown after 079afb081c42 , by Jens Axboe Re: [REGRESSION] io_uring/futex: scalar wait/wake slowdown after 079afb081c42 , by Jens Axboe Regzbot command history: fix: 4d327bbd1cd2 in next referred to this regression , by Jens Axboe fix: 73e701909747 in next referred to this regression , by Jens Axboe summary: io_uring scalar futex wait/wake slowdown , by Chengfeng Lin introduced: 079afb081c4288e94d5e4223d3eb6306d853c68b , by Chengfeng Lin
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/
9b8b84879d4a (v6.17-rc1)	*[PATCH] scsi: megaraid_sas: fix PRP list out-of-bounds write* by me, Daniel Fernau, Mira Limbeck, and Mats Topstad / Intility AS Earliest & latest activity: & . Noteworthy: [patch]. Latest patch: Re: [PATCH] scsi: megaraid_sas: fix PRP list out-of-bounds write , by Martin K. Petersen; simple patch Earlier patches: 1 Latest five known activities: Re: [PATCH] scsi: megaraid_sas: fix PRP list out-of-bounds write , by Damien Le Moal Re: [PATCH] scsi: megaraid_sas: fix PRP list out-of-bounds write , by Mats Topstad / Intility AS Re: [PATCH] scsi: megaraid_sas: fix PRP list out-of-bounds write , by Daniel Fernau Re: [PATCH] scsi: megaraid_sas: fix PRP list out-of-bounds write , by Martin K. Petersen; contains a simple patch Re: [PATCH] scsi: megaraid_sas: fix PRP list out-of-bounds write , by Mira Limbeck Regzbot command history: duplicate: https://lore.kernel.org/linux-scsi/4FE725D3-0702-425C-AAC5-4E0AF86E5EA1@intility.no/ , by Thorsten Leemhuis duplicate: https://lore.kernel.org/linux-scsi/0CFE3F49-179D-4735-86E2-B6C1EE2FDD2A@danielfernau.com/ , by Thorsten Leemhuis duplicate: https://lore.kernel.org/lkml/d171cc76-bf25-48ce-b482-d344669dfc24@proxmox.com/ [implicit via duplicate] , by Thorsten Leemhuis introduced: 9b8b84879d4a [implicit via duplicate] , by Thorsten Leemhuis note: 'e5f9824817c6' in 'stable/linux-7.0.y' contains a 'Fixes:' tag for the culprit of this regression , by Ranjan Kumar note: '45dcc815fc55' in 'stable/linux-6.18.y' contains a 'Fixes:' tag for the culprit of this regression , by Ranjan Kumar note: '04631f55afc5' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Ranjan Kumar note: 'edc4dde9b9a5' in 'stable/linux-6.19.y' contains a 'Fixes:' tag for the culprit of this regression , by Niklas Cassel note: '2e9832713631' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Niklas Cassel note: '876965de0a04' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Niklas Cassel note: '5f64ae1ef639' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Niklas Cassel When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 9b8b84879d4a ("block: Increase BLK_DEF_MAX_SECTORS_CAP") Reported-by: Daniel Fernau <mail@danielfernau.com> Link: https://lore.kernel.org/r/0CFE3F49-179D-4735-86E2-B6C1EE2FDD2A@danielfernau.com/ Reported-by: Mats Topstad / Intility AS <Mats.topstad@intility.no> Link: https://lore.kernel.org/r/4FE725D3-0702-425C-AAC5-4E0AF86E5EA1@intility.no/ Reported-by: Mira Limbeck <m.limbeck@proxmox.com> Link: https://lore.kernel.org/r/d171cc76-bf25-48ce-b482-d344669dfc24@proxmox.com/ Reported-by: me <me@magik.net> Link: https://lore.kernel.org/r/GPhsSM0vkgyIrs0DIZ62qeUZX7X4RxwQXVKiuvMx-lHQVSPDxpztUyQOGS0xikqvJ-Z94hMV-dW_5KN_0CX2hsfV7kTf_t0MTf6vdAAaSEc=@magik.net/
0a46ef234756 (v6.10-rc1)	*ext4: exercising xattr with stress-ng on ext4 when it's been created with ea_inode option causes a kernel hang* by Colin Ian King Earliest & latest activity: & . Noteworthy: [1], [2], [3], [4], [5], [6], [fix incoming]. [1]: [PATCH] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() [implicit due to Link/Closes tag] , by Aditya Srivastava (monitored) [2]: [PATCH v2] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() [implicit due to Link/Closes tag] , by Aditya Srivastava (monitored) [3]: [PATCH v3] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() [implicit due to Link/Closes tag] , by Aditya Srivastava (monitored) [4]: [PATCH v4] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() [implicit due to Link/Closes tag] , by Aditya Srivastava (monitored) [5]: [PATCH v5] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() [implicit due to Link/Closes tag] , by Aditya Srivastava (monitored) [6]: [PATCH v6] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() [implicit due to Link/Closes tag] , by Aditya Srivastava (monitored) Fix incoming: 03438084a7b8 ("ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find()") Latest five known activities: Commit 03438084a7b8 in next , by Aditya Prakash Srivastava Re: [PATCH v6] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() , by Theodore Ts'o Re: [PATCH v6] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() , by Colin King (gmail) Re: [PATCH v6] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() , by Jan Kara [PATCH v6] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() , by Aditya Srivastava; contains a signed-off patch Regzbot command history: fix: 03438084a7b8 in next referred to this regression , by Aditya Prakash Srivastava note: https://lore.kernel.org/all/20260626054821.1729-1-aditya.ansh182@gmail.com/ Re: [PATCH] ext4: fix deadlock in ext4_evict_ea_inode() vs cache_find() [implicit due to link] , by Jan Kara relate: https://lore.kernel.org/lkml/20260626054821.1729-1-aditya.ansh182@gmail.com/ [PATCH v6] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() [implicit due to Link/Closes tag] , by Aditya Srivastava relate: https://lore.kernel.org/lkml/20260625065010.2332-1-aditya.ansh182@gmail.com/ [PATCH v5] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() [implicit due to Link/Closes tag] , by Aditya Srivastava relate: https://lore.kernel.org/lkml/20260625060331.2189-1-aditya.ansh182@gmail.com/ [PATCH v4] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() [implicit due to Link/Closes tag] , by Aditya Srivastava relate: https://lore.kernel.org/lkml/20260625040935.2244-1-aditya.ansh182@gmail.com/ [PATCH v3] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() [implicit due to Link/Closes tag] , by Aditya Srivastava relate: https://lore.kernel.org/lkml/20260623095911.2372-1-aditya.ansh182@gmail.com/ [PATCH v2] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() [implicit due to Link/Closes tag] , by Aditya Srivastava relate: https://lore.kernel.org/lkml/20260623090519.2239-1-aditya.ansh182@gmail.com/ [PATCH] ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find() [implicit due to Link/Closes tag] , by Aditya Srivastava summary: ext4: exercising xattr with stress-ng on ext4 when it's been created with ea_inode option causes a kernel hang , by Thorsten Leemhuis introduced: 0a46ef234756dca04623b7591e8ebb3440622f0b , by Thorsten Leemhuis
096bd8c679 (v6.18-rc1)	*[BISECTED] wireless networking broken on Pinephone Pro* by Oren Klopfer Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH] Revert "arm64: dts: rockchip: Further describe the WiFi for the Pinephone Pro" [implicit due to Link/Closes tag] , by Oren Klopfer (monitored) Fix incoming: 5f19535351bf ("Revert "arm64: dts: rockchip: Further describe the WiFi for the Pinephone Pro"") Latest five known activities: Commit 5f19535351bf in next , by Oren Klopfer 5f19535351bf, the fix specified through '#regzbot fix:' earlier landed in next , by Oren Klopfer Commit ee7d67291fd9 in next , by Oren Klopfer Re: [PATCH v2] Revert "arm64: dts: rockchip: Further describe the WiFi for the Pinephone Pro" , by Heiko Stuebner [PATCH v2] Revert "arm64: dts: rockchip: Further describe the WiFi for the Pinephone Pro" , by Oren Klopfer; contains a signed-off patch Regzbot command history: fix: 5f19535351bf in next referred to this regression , by Oren Klopfer note: 'fix' commit '5f19535351bf' now in 'next' , by Oren Klopfer fix: ee7d67291fd9 in next referred to this regression , by Oren Klopfer relate: https://lore.kernel.org/lkml/20260615225014.219115-1-oklopfer37@gmail.com/ [PATCH] Revert "arm64: dts: rockchip: Further describe the WiFi for the Pinephone Pro" [implicit due to Link/Closes tag] , by Oren Klopfer introduced: 096bd8c679 , by Oren Klopfer
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 (#8) , by Jaak Ristioja [via dup] drm/amd, issue 5531: new comment (#7) , by Dianne Skoll [via dup] drm/amd, issue 5531: new comment (#6) , by Mario Limonciello [via dup] drm/amd, issue 5531: new comment (#5) , by Dianne Skoll [via dup] drm/amd, issue 5531: new comment (#4) , 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/
6a5e64c75e82 (v7.0-rc1)	*PCI: problems hotplugging a virtio-net-pci device behind a XIO3130* by Eric Auger Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH 1/1] PCI: Do not add hotplug reservation multiple times [implicit due to Link/Closes tag] , by Ilpo Järvinen (monitored) Fix incoming: 5012a6953208 ("PCI: Do not add hotplug reservation multiple times") Latest five known activities: Commit 5012a6953208 in next , by Ilpo Järvinen Re: [PATCH 1/1] PCI: Do not add hotplug reservation multiple times , by Bjorn Helgaas Re: [PATCH 1/1] PCI: Do not add hotplug reservation multiple times , by Ilpo Järvinen Re: [PATCH 1/1] PCI: Do not add hotplug reservation multiple times , by sashiko-bot [PATCH 1/1] PCI: Do not add hotplug reservation multiple times , by Ilpo Järvinen; contains a signed-off patch Regzbot command history: fix: 5012a6953208 in next referred to this regression , by Ilpo Järvinen relate: https://lore.kernel.org/lkml/20260720162416.5771-1-ilpo.jarvinen@linux.intel.com/ [PATCH 1/1] PCI: Do not add hotplug reservation multiple times [implicit due to Link/Closes tag] , by Ilpo Järvinen summary: PCI: problems hotplugging a virtio-net-pci device behind a XIO3130 , by Thorsten Leemhuis introduced: 6a5e64c75e8295 , by Thorsten Leemhuis note: 'a3b93b42238b' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Ilpo Järvinen
0949c646d646 (v7.0-rc1)	*x86/xen: PV DomU ballooning driver init issue* by Yannick Martin and Yannick Martin Earliest & latest activity: & . Noteworthy: [patch]. Latest patch: Re: [regression] Bug 221745 - PV DomU ballooning driver init issue , by Roger Pau Monné; simple patch Latest five known activities: Re: [regression] Bug 221745 - PV DomU ballooning driver init issue , by Yannick Martin [via dup] Re: [regression] Bug 221745 - PV DomU ballooning driver init issue , by Yannick Martin [via dup] Re: [regression] Bug 221745 - PV DomU ballooning driver init issue , by Roger Pau Monné; contains a simple patch [via dup] Bug 221745 - PV DomU ballooning driver init issue , by Thorsten Leemhuis [via dup] bugzilla.kernel.org, issue 221745: new comment (#5) , by yannick.martin+kernelorg Regzbot command history: note: '5d00a11d484e' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Roger Pau Monne note: "[PATCH v2] x86/xen: fix init of balloon stats again" contains a 'Fixes:' tag for the culprit of this regression , by Roger Pau Monne from: Yannick Martin <yannick.martin@okazoo.eu> , by Thorsten Leemhuis duplicate: https://lore.kernel.org/all/f7fe5959-f0c6-430c-8404-927d7944c836@leemhuis.info/ , by Thorsten Leemhuis summary: x86/xen: PV DomU ballooning driver init issue , by Thorsten Leemhuis introduced: 0949c646d64697 , by Thorsten Leemhuis note: https://bugzilla.kernel.org/show_bug.cgi?id=221745 Bug 221745 - PV DomU ballooning driver init issue [implicit due to link] , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 0949c646d646 ("Partial revert "x86/xen: fix balloon target initialization for PVH dom0"") Reported-by: Yannick Martin <yannick.martin@okazoo.eu> Link: https://bugzilla.kernel.org/show_bug.cgi?id=221745 Link: https://lore.kernel.org/r/f7fe5959-f0c6-430c-8404-927d7944c836@leemhuis.info/
f5cd8a929c82 (v7.0-rc1)	*PCI: imx6: endpoints not received by iMSI-RX MSI controller* by Soeren Moch Earliest & latest activity: & . Noteworthy: [fix incoming]. Fix incoming: PCI: imx6: Keep Root Port MSI capability also for i.MX6Q Latest five known activities: Re: [PATCH] PCI: imx6: Keep Root Port MSI capability also for i.MX6Q , by Soeren Moch Re: [PATCH] PCI: imx6: Keep Root Port MSI capability also for i.MX6Q , by Manivannan Sadhasivam Re: [PATCH] PCI: imx6: Keep Root Port MSI capability also for i.MX6Q , by Soeren Moch Re: [PATCH] PCI: imx6: Keep Root Port MSI capability also for i.MX6Q , by Manivannan Sadhasivam RE: [PATCH] PCI: imx6: Keep Root Port MSI capability also for i.MX6Q , by Hongxing Zhu Regzbot command history: introduced: f5cd8a929c825 , by Thorsten Leemhuis fix: PCI: imx6: Keep Root Port MSI capability also for i.MX6Q , by Thorsten Leemhuis summary: PCI: imx6: endpoints not received by iMSI-RX MSI controller , by Thorsten Leemhuis introduced: 3a4e8302e72f , by Thorsten Leemhuis
93c97bc8d85d (v6.18-rc4)	*drm/msm: dsi: resolutions broken* by Mohit Dsor Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH] Revert "drm/msm: dsi: fix PLL init in bonded mode" [implicit due to Link/Closes tag] , by Dmitry Baryshkov (monitored) Fix incoming: 44784327815b ("Revert "drm/msm: dsi: fix PLL init in bonded mode"") Latest five known activities: Commit 44784327815b in next , by Dmitry Baryshkov Re: [PATCH] Revert "drm/msm: dsi: fix PLL init in bonded mode" , by Dmitry Baryshkov Re: [PATCH] Revert "drm/msm: dsi: fix PLL init in bonded mode" , by sashiko-bot [PATCH] Revert "drm/msm: dsi: fix PLL init in bonded mode" , by Dmitry Baryshkov; contains a signed-off patch Re: [REGRESSION] Resolutions broken after "drm/msm: dsi: fix PLL init in bonded mode" , by Dmitry Baryshkov Regzbot command history: fix: 44784327815b in next referred to this regression , by Dmitry Baryshkov fix: 44784327815b in next referred to this regression , by Dmitry Baryshkov relate: https://lore.kernel.org/lkml/20260712-msm-revert-dsi-pll-fix-v1-1-40122689ea25@oss.qualcomm.com/ [PATCH] Revert "drm/msm: dsi: fix PLL init in bonded mode" [implicit due to Link/Closes tag] , by Dmitry Baryshkov summary: drm/msm: dsi: resolutions broken , by Thorsten Leemhuis introduced: 93c97bc8d85d57 , by Thorsten Leemhuis
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
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 Matt Fleming 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 Rik van Riel; contains a simple patch Regzbot command history: 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/
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
7c405fb3279b (v7.0-rc6)	*rcu: Allwinner D1 single-core RISC-V SoC stopped booting* by Emil Renner Berthing Earliest & latest activity: & . Latest five known activities: Re: [PATCH v2] rcu: Use an intermediate irq_work to start process_srcu() , by Indrek Kruusa Re: [PATCH v2] rcu: Use an intermediate irq_work to start process_srcu() , by Thorsten Leemhuis Re: [PATCH v2] rcu: Use an intermediate irq_work to start process_srcu() , by Emil Renner Berthing Re: [PATCH v2] rcu: Use an intermediate irq_work to start process_srcu() , by Samuel Holland Re: [PATCH v2] rcu: Use an intermediate irq_work to start process_srcu() , by Emil Renner Berthing Regzbot command history: summary: rcu: Allwinner D1 single-core RISC-V SoC stopped booting , by Thorsten Leemhuis introduced: 7c405fb3279b , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 7c405fb3279b ("rcu: Use an intermediate irq_work to start process_srcu()") Reported-by: Emil Renner Berthing <emil.renner.berthing@canonical.com> Link: https://lore.kernel.org/r/CAJM55Z-hiNDuu5UwoBe7m0wq%2B_WJrRY0cwopALUgpG%2Br3ixj8g@mail.gmail.com/
db299a0c09e9 (v6.18-rc1)	*net: stmmac: network interface init fails with custom MTU* by Stefan Agner Earliest & latest activity: & . Noteworthy: [fix incoming]. Fix incoming: net: stmmac: resume PHY before reopening the interface on MTU change All known activities: Re: [PATCH net] net: stmmac: resume PHY before reopening the interface on MTU change , by Stefan Agner Re: [PATCH net] net: stmmac: resume PHY before reopening the interface on MTU change , by Stefan Agner Re: [PATCH net] net: stmmac: resume PHY before reopening the interface on MTU change , by Andrew Lunn Re: [PATCH net] net: stmmac: resume PHY before reopening the interface on MTU change , by Jakub Raczynski [PATCH net] net: stmmac: resume PHY before reopening the interface on MTU change , by Stefan Agner; contains a signed-off patch Regzbot command history: note: '06232cb44bc8' in 'mainline' contains a 'Fixes:' tag for the culprit of this regression , by Stefan Agner note: '06232cb44bc8' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Stefan Agner note: https://lore.kernel.org/netdev/20260707162146.73823-1-stefan@agner.ch/ [PATCH net v3] net: stmmac: resume PHY before hardware setup when opening the interface [implicit due to link] , by Stefan Agner fix: net: stmmac: resume PHY before reopening the interface on MTU change , by Thorsten Leemhuis summary: net: stmmac: network interface init fails with custom MTU , by Thorsten Leemhuis introduced: db299a0c09e9 , by Thorsten Leemhuis note: "[PATCH net] net: stmmac: resume PHY before reopening the interface on MTU change" contains a 'Fixes:' tag for the culprit of this regression , by Stefan Agner
7299b1b39a25 (v7.0-rc3)	*can: usb: f81604: valid interrupt URBs are rejected* by Dynetrex, Admin Earliest & latest activity: & . All known activities: Re: [REGRESSION] can: usb: f81604: TX broken with "short int URB: 9 < 12" , by Greg KH can: usb: f81604: TX broken with "short int URB: 9 < 12" , by Dynetrex, Admin Regzbot command history: 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/
1317a5e7f7b1 (v6.13-rc1)	*arch/x86: AMD F15h VA alignment offset breaks MAP_HUGETLB alignment* by Karsten Desler Earliest & latest activity: & . Noteworthy: [1], [2], [3], [4], [fix incoming]. [1]: [PATCH] arch,x86: Skip setting align_offset for hugetlb mappings [implicit due to Link/Closes tag] , by Oscar Salvador (monitored) [2]: + archx86-skip-setting-align_offset-for-hugetlb-mappings.patch added to mm-hotfixes-unstable branch [implicit due to Link/Closes tag] , by Andrew Morton (monitored) [3]: [PATCH 1/8] mm,hugetlb: Encode extra padding for aligning directly in hugetlb_get_unmapped_area [implicit due to Link/Closes tag] , by Oscar Salvador (monitored) [4]: [to-be-updated] archx86-skip-setting-align_offset-for-hugetlb-mappings.patch removed from -mm tree [implicit due to Link/Closes tag] , by Andrew Morton (monitored) Fix incoming: b1892bc6e60b ("arch,x86: skip setting align_offset for hugetlb mappings") Latest five known activities: Commit b1892bc6e60b in next , by Oscar Salvador b1892bc6e60b, the fix specified through '#regzbot fix:' earlier landed in next , by Oscar Salvador [to-be-updated] archx86-skip-setting-align_offset-for-hugetlb-mappings.patch removed from -mm tree , by Andrew Morton; contains a simple patch Commit ddcd70a2e652 in next , by Oscar Salvador ddcd70a2e652, the fix specified through '#regzbot fix:' earlier landed in next , by Oscar Salvador Regzbot command history: fix: b1892bc6e60b in next referred to this regression , by Oscar Salvador note: 'fix' commit 'b1892bc6e60b' now in 'next' , by Oscar Salvador relate: https://lore.kernel.org/stable/20260706001612.D70B81F000E9@smtp.kernel.org/ [to-be-updated] archx86-skip-setting-align_offset-for-hugetlb-mappings.patch removed from -mm tree [implicit due to Link/Closes tag] , by Andrew Morton fix: ddcd70a2e652 in next referred to this regression , by Oscar Salvador note: 'fix' commit 'ddcd70a2e652' now in 'next' , by Oscar Salvador fix: 4aeffd9f695e in next referred to this regression , by Oscar Salvador note: 'fix' commit '4aeffd9f695e' now in 'next' , by Oscar Salvador fix: 6e300b213d1b in next referred to this regression , by Oscar Salvador note: 'fix' commit '6e300b213d1b' now in 'next' , by Oscar Salvador fix: 2014e6e45ad9 in next referred to this regression , by Oscar Salvador note: 'fix' commit '2014e6e45ad9' now in 'next' , by Oscar Salvador fix: 5c3ec223d403 in next referred to this regression , by Oscar Salvador note: 'fix' commit '5c3ec223d403' now in 'next' , by Oscar Salvador fix: 9ada876dcd6b in next referred to this regression , by Oscar Salvador note: 'fix' commit '9ada876dcd6b' now in 'next' , by Oscar Salvador fix: 8a294381985c in next referred to this regression , by Oscar Salvador note: 'fix' commit '8a294381985c' now in 'next' , by Oscar Salvador fix: dd2eac310b8a in next referred to this regression , by Oscar Salvador note: 'fix' commit 'dd2eac310b8a' now in 'next' , by Oscar Salvador fix: 2e2aeb42569a in next referred to this regression , by Oscar Salvador note: 'fix' commit '2e2aeb42569a' now in 'next' , by Oscar Salvador fix: 5046adc6ecd4 in next referred to this regression , by Oscar Salvador note: 'fix' commit '5046adc6ecd4' now in 'next' , by Oscar Salvador fix: 6903648e1f4d in next referred to this regression , by Oscar Salvador note: 'fix' commit '6903648e1f4d' now in 'next' , by Oscar Salvador fix: 929a1e13f5a6 in next referred to this regression , by Oscar Salvador note: 'fix' commit '929a1e13f5a6' now in 'next' , by Oscar Salvador fix: 0495cceb2444 in next referred to this regression , by Oscar Salvador note: 'fix' commit '0495cceb2444' now in 'next' , by Oscar Salvador fix: 09a12c621393 in next referred to this regression , by Oscar Salvador note: 'fix' commit '09a12c621393' now in 'next' , by Oscar Salvador relate: https://lore.kernel.org/lkml/20260606035003.529685-2-osalvador@suse.de/ [PATCH 1/8] mm,hugetlb: Encode extra padding for aligning directly in hugetlb_get_unmapped_area [implicit due to Link/Closes tag] , by Oscar Salvador note: https://lore.kernel.org/linux-mm/20260527143643.GO31091@soohrt.org/ [PATCH 1/8] mm,hugetlb: Encode extra padding for aligning directly in hugetlb_get_unmapped_area [implicit due to link] , by Oscar Salvador note: https://lore.kernel.org/linux-mm/20260527143643.GO31091@soohrt.org/ [PATCH 0/8] Stop special-casing hugetlb mappings in get_unmapped_area [implicit due to link] , by Oscar Salvador fix: 7a3aeb271668 in next referred to this regression , by Oscar Salvador note: 'fix' commit '7a3aeb271668' now in 'next' , by Oscar Salvador fix: 5af0c56cabb6 in next referred to this regression , by Oscar Salvador note: 'fix' commit '5af0c56cabb6' now in 'next' , by Oscar Salvador fix: a07fa1650531 in next referred to this regression , by Oscar Salvador note: 'fix' commit 'a07fa1650531' now in 'next' , by Oscar Salvador fix: d9337277db4c in next referred to this regression , by Oscar Salvador relate: https://lore.kernel.org/stable/20260601200943.691CF1F00893@smtp.kernel.org/ + archx86-skip-setting-align_offset-for-hugetlb-mappings.patch added to mm-hotfixes-unstable branch [implicit due to Link/Closes tag] , by Andrew Morton relate: https://lore.kernel.org/lkml/20260601125015.216110-1-osalvador@suse.de/ [PATCH] arch,x86: Skip setting align_offset for hugetlb mappings [implicit due to Link/Closes tag] , by Oscar Salvador summary: arch/x86: AMD F15h VA alignment offset breaks MAP_HUGETLB alignment , by Thorsten Leemhuis introduced: 1317a5e7f7b1 , by Thorsten Leemhuis
9ab94a32af70 (v7.0-rc1)	*net: r8169: PCIe AER errors and recovery failure after recent driver changes* by lasse Earliest & latest activity: & . Noteworthy: [1]. [1]: Re: [Bug 221606] r8169: PCIe AER errors and recovery failure after recent driver changes , by Heiner Kallweit (monitored) Latest five known activities: Re: [Bug 221606] r8169: PCIe AER errors and recovery failure after recent driver changes , by Thorsten Leemhuis Re: [Bug 221606] r8169: PCIe AER errors and recovery failure after recent driver changes , by Lasse Bjerre Re: [Bug 221606] r8169: PCIe AER errors and recovery failure after recent driver changes , by Heiner Kallweit RE: [Bug 221606] r8169: PCIe AER errors and recovery failure after recent driver changes , by Javen Re: [Bug 221606] r8169: PCIe AER errors and recovery failure after recent driver changes , by Heiner Kallweit Regzbot command history: relate: https://lore.kernel.org/all/b1bda1da-8231-4f05-94a7-7511041ae489@gmail.com/ , by Thorsten Leemhuis summary: net: r8169: PCIe AER errors and recovery failure after recent driver changes , by Thorsten Leemhuis introduced: 9ab94a32af704fa9c873094283ae8744a07baf25 , by Thorsten Leemhuis When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Fixes: 9ab94a32af70 ("r8169: enable LTR support") Reported-by: lasse Link: https://bugzilla.kernel.org/show_bug.cgi?id=221606
337b1b566db0 (v6.19-rc1)	*pci: amdgpu completely on the SolidRun HoneyComb LX* by Liz Fong-Jones via B4 Relay Earliest & latest activity: & . Noteworthy: [fix incoming]. Fix incoming: PCI: Fix BAR resize for devices on a root bus All known activities: Re: [PATCH] PCI: Fix BAR resize for devices on a root bus , by sashiko-bot [PATCH] PCI: Fix BAR resize for devices on a root bus , by Liz Fong-Jones via B4 Relay; contains a signed-off patch Regzbot command history: note: "[PATCH v3] PCI: Fix BAR resize for devices on a root bus" contains a 'Fixes:' tag for the culprit of this regression , by Liz Fong-Jones via B4 Relay note: '2764d031efd6' in 'stable/linux-6.18.y' contains a 'Fixes:' tag for the culprit of this regression , by Ilpo Järvinen note: '2fb74141ec54' in 'stable/linux-6.18.y' contains a 'Fixes:' tag for the culprit of this regression , by Ilpo Järvinen note: "[PATCH 6.18 1605/1611] PCI: Fix Resizable BAR restore order" contains a 'Fixes:' tag for the culprit of this regression , by Greg Kroah-Hartman note: "[PATCH 6.18 1604/1611] PCI: Fix BAR resize rollback path overwriting ret" contains a 'Fixes:' tag for the culprit of this regression , by Greg Kroah-Hartman note: "[PATCH v2] PCI: Fix BAR resize for devices on a root bus" contains a 'Fixes:' tag for the culprit of this regression , by Liz Fong-Jones via B4 Relay fix: PCI: Fix BAR resize for devices on a root bus , by Thorsten Leemhuis summary: pci: amdgpu completely on the SolidRun HoneyComb LX , by Thorsten Leemhuis introduced: 337b1b566db0 , by Thorsten Leemhuis note: 'c4e07332c3bb' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Ilpo Järvinen note: '57dfeba6dbb4' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Ilpo Järvinen note: '08d9eae76b85' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Ilpo Järvinen note: '5528fd38f230' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Ilpo Järvinen note: "[PATCH] PCI: Fix BAR resize for devices on a root bus" contains a 'Fixes:' tag for the culprit of this regression , by Liz Fong-Jones via B4 Relay
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 sashiko-bot Re: [PATCH v3] drm/vblank: Don't arm vblank timer with invalid frame duration , by Roman Ilin [PATCH v3] drm/vblank: Don't arm vblank timer with invalid frame duration , by Roman Ilin; contains a signed-off patch Re: [PATCH v2] drm/vblank: Don't arm vblank timer with invalid frame duration , by sashiko-bot 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
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 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/
4d4c10f763d7 (v6.16-rc1)	*[BISECTED] HDA controller MMIO unreadable on Intel 5-series PCH (Ibex Peak) since v6.16* by Filippe Duke Earliest & latest activity: & . Latest five known activities: Re: [REGRESSION][BISECTED] HDA controller MMIO unreadable on Intel 5-series PCH (Ibex Peak) since v6.16 , by Filippe Duke Re: [REGRESSION][BISECTED] HDA controller MMIO unreadable on Intel 5-series PCH (Ibex Peak) since v6.16 , by Thorsten Leemhuis Re: [REGRESSION][BISECTED] HDA controller MMIO unreadable on Intel 5-series PCH (Ibex Peak) since v6.16 , by Lukas Wunner Re: [REGRESSION][BISECTED] HDA controller MMIO unreadable on Intel 5-series PCH (Ibex Peak) since v6.16 , by Filippe Duke Re: [REGRESSION][BISECTED] HDA controller MMIO unreadable on Intel 5-series PCH (Ibex Peak) since v6.16 , by Lukas Wunner Regzbot command history: note: https://lore.kernel.org/all/5e54aea4a97f1cbbe866d9d8f3f25f9f2958e1c9.camel@greennet.ua/ bugzilla.kernel.org, issue 221727: new comment (#7) [implicit due to link] , by Takashi Iwai note: '907a7a2e5bf4' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Mario Limonciello introduced: 4d4c10f763d7 , by Filippe Duke 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: Filippe Duke <fduke@greennet.ua> Link: https://lore.kernel.org/r/5e54aea4a97f1cbbe866d9d8f3f25f9f2958e1c9.camel@greennet.ua/
5ff3f74e145a (v6.18-rc1)	*block: virtio-blk + LVM raid1 spurious sector-0 read failures on libaio/threads submit since 5ff3f74e145a ("block: simplify direct io validity check")* by Vjaceslavs Klimovs and Dr. David Alan Gilbert Earliest & latest activity: & . Noteworthy: [1], [fix incoming]. [1]: [PATCH v3 0/5] block: validate direct I/O memory alignment , by Keith Busch (monitored) [via dup] Fix incoming: block: validate direct I/O memory alignment Latest five known activities: Re: [PATCH v3 0/5] block: validate direct I/O memory alignment , by Keith Busch [via dup] Re: [PATCH v3 0/5] block: validate direct I/O memory alignment , by Christoph Hellwig [via dup] Re: [PATCH v3 5/5] block: validate user space vectors during extraction , by Christoph Hellwig [via dup] Re: [PATCH v3 4/5] zloop: set dma_alignment from the backing files for direct I/O , by Christoph Hellwig [via dup] Re: [PATCH v3 3/5] loop: set dma_alignment from the backing file for direct I/O , by Christoph Hellwig [via dup] Regzbot command history: note: '14b007e17881' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Keith Busch note: '47a5e62f3987' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Mikulas Patocka note: '62dc37a819a5' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Keith Busch note: https://lore.kernel.org/all/CAC_j7i1R7oy+nRhxEjCTba=DUgn02w9X+p94DCu0aHv5+5tKnQ@mail.gmail.com/ [PATCH RESEND 0/5] block: validate direct I/O memory alignment [implicit due to link] , by Keith Busch fix: block: validate direct I/O memory alignment , by Thorsten Leemhuis note: https://lore.kernel.org/all/CAC_j7i1R7oy+nRhxEjCTba=DUgn02w9X+p94DCu0aHv5+5tKnQ@mail.gmail.com/ [PATCH v3 0/5] block: validate direct I/O memory alignment [implicit due to link] , by Keith Busch note: https://lore.kernel.org/all/CAC_j7i1R7oy+nRhxEjCTba=DUgn02w9X+p94DCu0aHv5+5tKnQ@mail.gmail.com/ [PATCH v3 0/5] block: validate direct I/O memory alignment [implicit due to link] , by Keith Busch note: https://lore.kernel.org/all/CAC_j7i1R7oy+nRhxEjCTba=DUgn02w9X+p94DCu0aHv5+5tKnQ@mail.gmail.com/ [PATCHv2 0/6] direct-io: validate user space vectors during extraction [implicit due to link] , by Keith Busch note: https://lore.kernel.org/all/CAC_j7i1R7oy+nRhxEjCTba=DUgn02w9X+p94DCu0aHv5+5tKnQ@mail.gmail.com/ [PATCH 0/1] direct-io: validate user space vectors during extraction [implicit due to link] , by Keith Busch duplicate: https://lore.kernel.org/all/ai7rnH20IYeSmY8s@gallifrey/ , by Thorsten Leemhuis note: '9b0c3673c885' in 'mainline' contains a 'Fixes:' tag for the culprit of this regression , by Keith Busch note: '9b0c3673c885' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Keith Busch note: https://lore.kernel.org/all/CAC_j7i1R7oy+nRhxEjCTba=DUgn02w9X+p94DCu0aHv5+5tKnQ@mail.gmail.com/ Re: Repeatable, raid1+O_DIRECT, hang/warn [implicit due to link] , by Thorsten Leemhuis note: https://lore.kernel.org/all/CAC_j7i1R7oy+nRhxEjCTba=DUgn02w9X+p94DCu0aHv5+5tKnQ@mail.gmail.com/ Re: Repeatable, raid1+O_DIRECT, hang/warn [implicit due to link] , by Thorsten Leemhuis note: 'f7b24c7b41f2' in 'next' contains a 'Fixes:' tag for the culprit of this regression , by Keith Busch introduced: 5ff3f74e145adc79b49668adb8de276446acf6be , by Vjaceslavs Klimovs
previous cycle (v7.0..v7.1), unknown culprit, with activity in the past three weeks
v7.0..v7.1	*mm/memcg: folio/lruvec mismatch after cgroup offline: lru_size underflow and list_del corruption (7.1)* by Karl Erik Hofseth Earliest & latest activity: & . Noteworthy: [1], [2], [3], [4], [5], [6], [fix incoming]. [1]: [PATCH] memcg: keep folio's objcg same as its node [implicit due to Link/Closes tag] , by Shakeel Butt (monitored) [2]: + memcg-keep-folios-objcg-same-as-its-node.patch added to mm-hotfixes-unstable branch [implicit due to Link/Closes tag] , by Andrew Morton (monitored) [3]: [PATCH v2] memcg: keep folio's objcg same as its node [implicit due to Link/Closes tag] , by Shakeel Butt (monitored) [4]: [PATCH v3] memcg: keep folio's objcg same as its node [implicit due to Link/Closes tag] , by Shakeel Butt (monitored) [5]: + memcg-keep-folios-objcg-same-as-its-node.patch added to mm-hotfixes-unstable branch [implicit due to Link/Closes tag] , by Andrew Morton (monitored) [6]: [merged mm-hotfixes-stable] memcg-keep-folios-objcg-same-as-its-node.patch removed from -mm tree [implicit due to Link/Closes tag] , by Andrew Morton (monitored) Fix incoming: e4498c4bbefc ("memcg: keep folio's objcg same as its node") Latest five known activities: Commit e4498c4bbefc in next , by Shakeel Butt e4498c4bbefc, the fix specified through '#regzbot fix:' earlier landed in next , by Shakeel Butt [merged mm-hotfixes-stable] memcg-keep-folios-objcg-same-as-its-node.patch removed from -mm tree , by Andrew Morton; contains a simple patch Commit 17f6044366d6 in next , by Shakeel Butt 17f6044366d6, the fix specified through '#regzbot fix:' earlier landed in next , by Shakeel Butt Regzbot command history: fix: e4498c4bbefc in next referred to this regression , by Shakeel Butt note: 'fix' commit 'e4498c4bbefc' now in 'next' , by Shakeel Butt relate: https://lore.kernel.org/stable/20260814010833.AF3371F000E9@smtp.kernel.org/ [merged mm-hotfixes-stable] memcg-keep-folios-objcg-same-as-its-node.patch removed from -mm tree [implicit due to Link/Closes tag] , by Andrew Morton fix: 17f6044366d6 in next referred to this regression , by Shakeel Butt note: 'fix' commit '17f6044366d6' now in 'next' , by Shakeel Butt fix: 673502e7af88 in next referred to this regression , by Shakeel Butt note: 'fix' commit '673502e7af88' now in 'next' , by Shakeel Butt fix: 17fcc6e5cb37 in next referred to this regression , by Shakeel Butt note: 'fix' commit '17fcc6e5cb37' now in 'next' , by Shakeel Butt fix: 1674223bf754 in next referred to this regression , by Shakeel Butt note: 'fix' commit '1674223bf754' now in 'next' , by Shakeel Butt relate: https://lore.kernel.org/stable/20260807192350.D856F1F000E9@smtp.kernel.org/ + memcg-keep-folios-objcg-same-as-its-node.patch added to mm-hotfixes-unstable branch [implicit due to Link/Closes tag] , by Andrew Morton relate: https://lore.kernel.org/lkml/20260807142406.443516-1-shakeel.butt@linux.dev/ [PATCH v3] memcg: keep folio's objcg same as its node [implicit due to Link/Closes tag] , by Shakeel Butt fix: 45864c144d4d in next referred to this regression , by Shakeel Butt relate: https://lore.kernel.org/lkml/20260806165813.2526415-1-shakeel.butt@linux.dev/ [PATCH v2] memcg: keep folio's objcg same as its node [implicit due to Link/Closes tag] , by Shakeel Butt relate: https://lore.kernel.org/stable/20260806063218.2A7BA1F000E9@smtp.kernel.org/ + memcg-keep-folios-objcg-same-as-its-node.patch added to mm-hotfixes-unstable branch [implicit due to Link/Closes tag] , by Andrew Morton relate: https://lore.kernel.org/lkml/20260806061830.3294679-1-shakeel.butt@linux.dev/ [PATCH] memcg: keep folio's objcg same as its node [implicit due to Link/Closes tag] , by Shakeel Butt introduced: v7.0..v7.1 , by Karl Erik Hofseth
older cycles (..v7.0), unknown culprit, with activity in the past three weeks
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 (#15) , by Demon Player [via dup] Re: [REGRESSION / HELP] sound/soc/amd: No sound after suspend/resume on RPL (merged into YC driver) , by Mukunda,Vijendar [via dup] drm/amd, issue 5529: new comment (#14) , by Vijendar Mukunda [via dup] [REGRESSION / HELP] sound/soc/amd: No sound after suspend/resume on RPL (merged into YC driver) , by Mingyou Chen [via dup] drm/amd, issue 5529: new comment (#13) , by Demon Player [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/
all others with unknown culprit and activity in the past three months
v6.12..v6.18	*mm/mprotect: shared dirty PTE toggle takes ~1.6x longer on v6.19 than v6.12* by Chengfeng Lin Earliest & latest activity: & . Latest five known activities: Re: Re: [REGRESSION] mm/mprotect: shared dirty PTE toggle takes ~1.6x longer on v6.19 than v6.12 , by Chengfeng Lin Re: [REGRESSION] mm/mprotect: shared dirty PTE toggle takes ~1.6x longer on v6.19 than v6.12 , by Pedro Falcato Re: Re: [REGRESSION] mm/mprotect: shared dirty PTE toggle takes ~1.6x longer on v6.19 than v6.12 , by Chengfeng Lin Re: [REGRESSION] mm/mprotect: shared dirty PTE toggle takes ~1.6x longer on v6.19 than v6.12 , by Chengfeng Lin Re: [REGRESSION] mm/mprotect: shared dirty PTE toggle takes ~1.6x longer on v6.19 than v6.12 , by Chengfeng Lin Regzbot command history: summary: mm/mprotect: shared dirty PTE toggle takes ~1.6x longer on v6.19 than v6.12 , by Chengfeng Lin introduced: v6.12..v6.18 , by Chengfeng Lin When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue: Reported-by: Chengfeng Lin <23020251154299@stu.xmu.edu.cn> Link: https://lore.kernel.org/r/662955ba.f499.19e3b2cf478.Coremail.23020251154299@stu.xmu.edu.cn/
on back burner with activity in the past six months
none known by regzbot

[compiled by regzbot on 2026-08-15 09:15:36 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

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