linux-kernel - x86: HPET as CPU-local timer + interrupt remapping = lockup

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>] [day] [month] [year] [list]

Date:	Mon, 11 Aug 2014 21:29:51 +0200
From:	Jan Kiszka <jan.kiszka@...mens.com>
To:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>, x86 <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: x86: HPET as CPU-local timer + interrupt remapping = lockup

Hi all,

just noticed an apparent regression of x86-64 on CPUs without ARAT but a
sufficient number if HPET timers: If you have interrupt remapping
enabled, the kernel will lock up during boot, apparently waiting for
some never-arriving interrupts.

I'm currently adding VT-d interrupt emulation to QEMU and stumbled over
this behavior. It didn't turn out to be an emulation issue, I just
reproduced on real hardware (ARAT patched out) and found some old 3.0
kernel booting fine inside my QEMU version.

FWIW, some further details I found out under QEMU: the HPET timers do
not seem to be switched to MSI mode yet when the lockup happens.

I suppose the issue is uncritical as the combination of hardware feature
(or their absence) is probably untypical, correct? I can't invest much
into bisecting or debugging right now unfortunately. But maybe someone
has an idea what could case this.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/