linux-kernel - Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

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: <d547e939-3e41-4ad8-e6fe-fc1680169c5f@gmail.com>
Date:   Sat, 13 May 2017 12:52:13 -0700
From:   PGNet Dev <pgnet.dev@...il.com>
To:     Clemens Ladisch <clemens@...isch.de>
Cc:     Randy Dunlap <rdunlap@...radead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: HPET enabled in BIOS, not presented as available_clocksource --
 config, kernel code, &/or BIOS?

On 5/13/17 12:45 PM, Clemens Ladisch wrote:
> That table is not used by hpet_acpi_add; you have to check for the device
> that mentions "PNP0103" in the DSDT table.
> 
> But anyway, as far as I can tell from my own machine, the _CRS in the
> DSDT table never lists the HPET interrupts, and the HPET registration is
> always done by hpet_reserve_platform_timers() in arch/x86/kernel/hpet.c.
> Try adding logging to hpet_late_init() to find out why it aborts.

I assume you mean in kernel source code?

I'm using distro packages for both kernel & Xen -- not DIY building.