Messages in this thread | | | Subject | Re: Early boot regression from f0551af0213 ("x86/topology: Ignore non-present APIC IDs in a present package") | From | Lyude Paul <> | Date | Thu, 18 Apr 2024 13:20:05 -0400 |
| |
Just gave it a try, unfortunately I'm still seeing the same result on that branch.
One more piece of information I apparently missed when reporting this yesterday btw: I noticed one more kernel message that comes before the panic that's probably relevant:
.TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
On Thu, 2024-04-18 at 10:27 +0200, Borislav Petkov wrote: > On Wed, Apr 17, 2024 at 05:21:43PM -0400, Lyude Paul wrote: > > Hi! I just wanted to let you know that one of the desktops I use > > for > > testing no longer seems to boot after this commit (just finished > > bisecting and confirming). The machine hangs before it gets to > > fbcon, > > and the error I'm seeing in the early boot console is as such: > > > > Kernel panic - not syncing: timer doesn't work through > > Interrupt-remapped IO-APIC > > CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.8.0-rc5Lyude-Test+ > > #20 > > Hardware name: MSI MS-7A39/A320M GAMING PRO (MS-7A39), BIOS 1.10 > > 01/22/2019 > > Looks like an AMD chipset. Thomas did fix some fallout from the topo > rework on AMD, can you test the tip/master branch pls? > > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/ > > Thx. >
-- Cheers, Lyude Paul (she/her) Software Engineer at Red Hat
| |