lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 13 May 2024 19:18:29 -0400
From: Lyude Paul <lyude@...hat.com>
To: Thomas Gleixner <tglx@...utronix.de>, "Linux regression tracking
 (Thorsten Leemhuis)" <regressions@...mhuis.info>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, Mario Limonciello
	 <mario.limonciello@....com>, Borislav Petkov <bp@...en8.de>, Linux kernel
 regressions list <regressions@...ts.linux.dev>
Subject: Re: Early boot regression from f0551af0213 ("x86/topology: Ignore
 non-present APIC IDs in a present package")

On Mon, 2024-05-13 at 16:08 +0200, Thomas Gleixner wrote:
> On Wed, May 08 2024 at 19:21, Lyude Paul wrote:
> > Regarding the test results - I tried possible_cpus all the way up to 17
> > and nothing got the machine to boot. However, possible_cpus=8
> > intremap=off did get the machine to boot successfully
> 
> Oh. That's interesting.
> 
> Does v6.9 (released yesterday) boot with just 'intremap=off' too?

Yes - it still boots. As well I finally got the serial console adapter in, but
I don't see any additional output:

[    0.146896] printk: legacy console [tty0] enabled
[    0.147433] printk: legacy console [ttyS0] enabled
[    1.951453] ACPI: Core revision 20230628
[    1.955466] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484873504 ns
[    1.964698] APIC: Switch to symmetric I/O mode setup
[    1.970973] AMD-Vi: Using global IVHD EFR:0xf77ef22294ada, EFR2:0x0
[    1.978491] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    1.996945] Kernel panic - not syncing: timer doesn't work through Interrupt-remapped IO-APIC
[    2.005376] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.9.0Lyude-Test+ #7
[    2.012248] Hardware name: MSI MS-7A39/A320M GAMING PRO (MS-7A39), BIOS 1.I0 01/22/2019
[    2.020160] Call Trace:
[    2.022584]  <TASK>
[    2.024666]  dump_stack_lvl+0x5d/0x80
[    2.028499]  panic+0x118/0x2c8
[    2.031522]  ? timer_irq_works+0x54/0xf0
[    2.035408]  panic_if_irq_remap.cold+0x5/0x9
[    2.039631]  setup_IO_APIC+0x398/0x860
[    2.043475]  ? _raw_spin_unlock_irqrestore+0x1d/0x40
[    2.048393]  ? clear_IO_APIC_pin+0x125/0x1e0
[    2.052617]  apic_intr_mode_init+0xcc/0xe0
[    2.056672]  x86_late_time_init+0x24/0x40
[    2.060820]  start_kernel+0x8be/0x960
[    2.064446]  x86_64_start_reservations+0x24/0x30
[    2.069015]  x86_64_start_kernel+0x95/0xa0
[    2.073069]  common_startup_64+0x13e/0x141
[    2.077280]  </TASK>
[    2.079447] ---[ end Kernel panic - not syncing: timer doesn't work through Interrupt-remapped IO-APIC ]---


> 
> Thanks,
> 
>         tglx
> 

-- 
Cheers,
 Lyude Paul (she/her)
 Software Engineer at Red Hat


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ