On Saturday, 1 April 2023 10:09:09 CEST Guy Durrieu wrote: > Le 01/04/2023 à 09:25, Bjørn Mork a écrit : > > Guy Durrieu <guy.durrieu@cegetel.net> writes: > >> ---- > >> [ 0.117782] Kernel panic — not syncing: timer doesn’t work through > >> Interrupt- > >> remapped I0-APIC > >> [ 0.117848] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-and64 #1 > >> Debian > >> 6.1.20-1 > >> [ 0.117913] Hardware name: Gigabyte Technology Co., Ltd. ABS50M-Gaming > >> 3/AB350M-Gaming 3-CF, BIOS F50d 07/02/2020 > >> [ 0.117982] Call Trace: > >> [ 0.118634] <TASK> > >> [ 0.118685] dump_stack_lvl+0x44/0x5c > >> [ 0.118143] panic+0x118/0x2ed > >> [ 0.118198] panic_if_irq_remap.cold+0x5/0x5 > >> [ 0.118256] setup_I0_APIC+0x3db/0x64b > >> [ 0.118313] ? _raw_spin_unlock_irqrestore+0x23/0x40 > >> [ 0.118372] ? clear_IO_APIC_pin+0x169/0x240 > >> [ 0.118429] apic_intr_node_init+0x101/0x106 > >> [ 0.118485] x86_late_time_init+0x20/0x34 > >> [ 0.118542] start_kerne1+0x667/0x727 > >> [ 0.118598] secondary_startup_64_no_verify+0xe5/0xeb > >> [ 0.118658] </TASK> > >> [ 0.118711] ---[ end Kernel panic - not syncing: timer doesn’t work > >> through > >> Interrupt-remapped IO-APIC J--- > >> ---- > > > > Extremely suspiscious commit in the v6.1.15..v6.1.20 update: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git > > /commit/?id=ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b > > I am not sure I understand everything that is said in your link, except > I must wait for the next updates... Right ? When triaging a bug, we usually try to find the upstream commit which *caused* the issue and Bjørn thinks it's the one referenced. To test whether that's indeed the case, there's a procedure here: https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.1 These are preliminary steps to the actual one which is para 4.2.2 and I have attached a patch which reverts the referenced commit and that .patch file is what you give as an argument to `bash debian/bin/test-patches`. If you could try that to see if that indeed fixes the issue, that would be very helpful. HTH
>From 2e6223080905caf4c775680201700b243caa91a9 Mon Sep 17 00:00:00 2001
From: Diederik de Haas <didi.debian@cknow.org>
Date: Sat, 1 Apr 2023 10:32:31 +0200
Subject: [PATCH] Revert "x86/acpi/boot: Do not register processors that cannot
be onlined for x2APIC"
This reverts commit ce7d894bed1a539a8d6cff42f6f78f9db0c9c26b.
---
arch/x86/kernel/acpi/boot.c | 19 +++----------------
1 file changed, 3 insertions(+), 16 deletions(-)
diff --git a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
index 518bda50068c..907cc98b1938 100644
--- a/arch/x86/kernel/acpi/boot.c
+++ b/arch/x86/kernel/acpi/boot.c
@@ -188,17 +188,6 @@ static int acpi_register_lapic(int id, u32 acpiid, u8 enabled)
return cpu;
}
-static bool __init acpi_is_processor_usable(u32 lapic_flags)
-{
- if (lapic_flags & ACPI_MADT_ENABLED)
- return true;
-
- if (acpi_support_online_capable && (lapic_flags & ACPI_MADT_ONLINE_CAPABLE))
- return true;
-
- return false;
-}
-
static int __init
acpi_parse_x2apic(union acpi_subtable_headers *header, const unsigned long end)
{
@@ -223,10 +212,6 @@ acpi_parse_x2apic(union acpi_subtable_headers *header, const unsigned long end)
if (apic_id == 0xffffffff)
return 0;
- /* don't register processors that cannot be onlined */
- if (!acpi_is_processor_usable(processor->lapic_flags))
- return 0;
-
/*
* We need to register disabled CPU as well to permit
* counting disabled CPUs. This allows us to size
@@ -265,7 +250,9 @@ acpi_parse_lapic(union acpi_subtable_headers * header, const unsigned long end)
return 0;
/* don't register processors that can not be onlined */
- if (!acpi_is_processor_usable(processor->lapic_flags))
+ if (acpi_support_online_capable &&
+ !(processor->lapic_flags & ACPI_MADT_ENABLED) &&
+ !(processor->lapic_flags & ACPI_MADT_ONLINE_CAPABLE))
return 0;
/*
--
2.40.0
Attachment:
signature.asc
Description: This is a digitally signed message part.