You are not logged in.
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.12.r1507.g3f02039-1-x86_64.pkg.tar.zst
Offline
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.12.r1507.g3f02039-1-x86_64.pkg.tar.zst
This one's good
Offline
Does adding the kernel parameter split_lock_detect=off have any effect on a kernel with the issue?
Offline
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.12.rc1.r18.g14077b9-1-x86_64.pkg.tar.zst
Offline
Does adding the kernel parameter split_lock_detect=off have any effect on a kernel with the issue?
YES, this was it. Did its default value change within 6.12?
Offline
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.12.rc1.r18.g14077b9-1-x86_64.pkg.tar.zst
This one works too
Offline
YES, this was it. Did its default value change within 6.12?
https://lore.kernel.org/all/20240808062937.1149-3-ravi.bangoria@amd.com/ was added as part of 6.13 and has not been ruled out by the bisection so far.
Offline
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.12.r1518.ga5c93bf-1-x86_64.pkg.tar.zst
Offline
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.12.r1518.ga5c93bf-1-x86_64.pkg.tar.zst
This one's broken
Offline
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.12.r1514.g89c45f3-1-x86_64.pkg.tar.zst
Offline
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.12.r1514.g89c45f3-1-x86_64.pkg.tar.zst
Broken too
Offline
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.12.rc4.r3.g97ecb26-1-x86_64.pkg.tar.zst
Offline
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.12.rc4.r3.g97ecb26-1-x86_64.pkg.tar.zst
This one works
Offline
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.11.rc2.r2.g408eb74-1-x86_64.pkg.tar.zst
Offline
loqs wrote:Does adding the kernel parameter split_lock_detect=off have any effect on a kernel with the issue?
YES, this was it. Did its default value change within 6.12?
I think we can also change it without rebooting by using:
sysctl kernel.split_lock_mitigate=0
This will still print some messages in the journal, but won't slow down the application.
Offline
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.11.rc2.r2.g408eb74-1-x86_64.pkg.tar.zst
This one's broken
Offline
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.11.rc2.r1.g350afa8-1-x86_64.pkg.tar.zst
Offline
Please try:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-v6.11.rc2.r1.g350afa8-1-x86_64.pkg.tar.zst
This one works.
Offline
This is the first bad commit:
commit 408eb7417a92c5354c7be34f7425b305dfe30ad9
Author: Ravi Bangoria <ravi.bangoria@amd.com>
Date: Thu Aug 8 06:29:35 2024 +0000
x86/bus_lock: Add support for AMD
Add Bus Lock Detect (called Bus Lock Trap in AMD docs) support for AMD
platforms. Bus Lock Detect is enumerated with CPUID Fn0000_0007_ECX_x0
bit [24 / BUSLOCKTRAP]. It can be enabled through MSR_IA32_DEBUGCTLMSR.
When enabled, hardware clears DR6[11] and raises a #DB exception on
occurrence of Bus Lock if CPL > 0. More detail about the feature can be
found in AMD APM[1].
[1]: AMD64 Architecture Programmer's Manual Pub. 40332, Rev. 4.07 - June
2023, Vol 2, 13.1.3.6 Bus Lock Trap
https://bugzilla.kernel.org/attachment.cgi?id=304653
Signed-off-by: Ravi Bangoria <ravi.bangoria@amd.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
Link: https://lore.kernel.org/all/20240808062937.1149-3-ravi.bangoria@amd.com
Documentation/arch/x86/buslock.rst | 3 ++-
arch/x86/Kconfig | 2 +-
arch/x86/kernel/cpu/common.c | 2 ++
arch/x86/kernel/cpu/intel.c | 1 -
4 files changed, 5 insertions(+), 3 deletions(-)
How do we go about the bug reporting to the upstream kernel devs? Do you want to file a bug or should I do it?
Offline
This is the first bad commit:
commit 408eb7417a92c5354c7be34f7425b305dfe30ad9 Author: Ravi Bangoria <ravi.bangoria@amd.com> Date: Thu Aug 8 06:29:35 2024 +0000 x86/bus_lock: Add support for AMD Add Bus Lock Detect (called Bus Lock Trap in AMD docs) support for AMD platforms. Bus Lock Detect is enumerated with CPUID Fn0000_0007_ECX_x0 bit [24 / BUSLOCKTRAP]. It can be enabled through MSR_IA32_DEBUGCTLMSR. When enabled, hardware clears DR6[11] and raises a #DB exception on occurrence of Bus Lock if CPL > 0. More detail about the feature can be found in AMD APM[1]. [1]: AMD64 Architecture Programmer's Manual Pub. 40332, Rev. 4.07 - June 2023, Vol 2, 13.1.3.6 Bus Lock Trap https://bugzilla.kernel.org/attachment.cgi?id=304653 Signed-off-by: Ravi Bangoria <ravi.bangoria@amd.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com> Link: https://lore.kernel.org/all/20240808062937.1149-3-ravi.bangoria@amd.com Documentation/arch/x86/buslock.rst | 3 ++- arch/x86/Kconfig | 2 +- arch/x86/kernel/cpu/common.c | 2 ++ arch/x86/kernel/cpu/intel.c | 1 - 4 files changed, 5 insertions(+), 3 deletions(-)
How do we go about the bug reporting to the upstream kernel devs? Do you want to file a bug or should I do it?
Thank you so much for your help Gromit! I want to try doing the reporting myself. Do I just send the bug report w/ affected diff to the author + those that signed off and reviewed it? Or should I include linux-kernel@vger.kernel.org & kvm@vger.kernel.org mailing lists as well as all others involved as part of this commit?
Offline
You're welcome! Nice, please have a look at the "Reporting regressions" document: https://docs.kernel.org/admin-guide/rep … sions.html
Also you may want to have a look at one of my recent reports: https://lore.kernel.org/all/3cd82004-c5 … heusel.eu/
I usually try to put the patch authors in "To:" and CC the relevant maintainer list, any involved people and the regressions list.
$ ./scripts/get_maintainer.pl --no-rolestats -f arch/x86/kernel/cpu/common.c
Thomas Gleixner <tglx@linutronix.de>
Ingo Molnar <mingo@redhat.com>
Borislav Petkov <bp@alien8.de>
Dave Hansen <dave.hansen@linux.intel.com>
x86@kernel.org
"H. Peter Anvin" <hpa@zytor.com>
"Xin Li (Intel)" <xin@zytor.com>
Tony Luck <tony.luck@intel.com>
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Juergen Gross <jgross@suse.com>
linux-kernel@vger.kernel.org
In this case this is quite some people ... Also it would be nice if you could credit me in your report for the efforts that I have put into building all these kernels, you can cc me with "christian@heusel.eu"
Last edited by gromit (2025-03-04 17:04:15)
Offline
Upstream response to the report https://lore.kernel.org/regressions/Z8j … oogle.com/ @gromit could you build a test kernel with the series from https://lore.kernel.org/all/20250227222 … oogle.com/ applied?
Offline
Please test the the following kernel build which has the series mentioned by @loqs applied:
https://pkgbuild.com/~gromit/linux-bisection-kernels/linux-mainline-6.14rc5-3-x86_64.pkg.tar.zst
Last edited by gromit (2025-03-06 15:50:06)
Offline