linux-kernel - Re: [BUG] Linux 5.3-rc1: timer problem on x86-64 (Pentium D)

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]

Message-ID: <alpine.DEB.2.21.1907241257240.1791@nanos.tec.linutronix.de>
Date:   Wed, 24 Jul 2019 13:02:10 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Rui Salvaterra <rsalvaterra@...il.com>
cc:     LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
        Daniel Drake <drake@...lessm.com>
Subject: Re: [BUG] Linux 5.3-rc1: timer problem on x86-64 (Pentium D)

Rui,

On Wed, 24 Jul 2019, Rui Salvaterra wrote:
> I don't know if this has been reported before, but from a cursory
> search it doesn't seem to be the case.
> I have a x86-64 Pentium (4) D machine which always worked perfectly
> with Linux 5.2 using the TSC as the clock source. With Linux 5.3-rc1 I
> can't, for the life of me, boot it with anything other than
> clocksource=jiffies, it completely hangs without even a backtrace.

The obvious candidate for this is the following section:

c8c4076723da ("x86/timer: Skip PIT initialization on modern chipsets")
dde3626f815e ("x86/apic: Use non-atomic operations when possible")
748b170ca19a ("x86/apic: Make apic_bsp_setup() static")
2420a0b1798d ("x86/tsc: Set LAPIC timer period to crystal clock frequency")
52ae346bd26c ("x86/apic: Rename 'lapic_timer_frequency' to 'lapic_timer_period'")
604dc9170f24 ("x86/tsc: Use CPUID.0x16 to calculate missing crystal frequency")

Thanks,

	tglx