From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757978AbdEMTwR (ORCPT ); Sat, 13 May 2017 15:52:17 -0400 Received: from mail-pg0-f66.google.com ([74.125.83.66]:36662 "EHLO mail-pg0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753347AbdEMTwP (ORCPT ); Sat, 13 May 2017 15:52:15 -0400 Reply-To: pgnet.dev@gmail.com Subject: Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? To: Clemens Ladisch Cc: Randy Dunlap , "linux-kernel@vger.kernel.org" References: <61d510e2-0353-ddf2-f63c-8a1688a6b6ed@gmail.com> <9ff8ca5a-727d-13c3-7c39-6383e00d2edf@infradead.org> From: PGNet Dev Message-ID: Date: Sat, 13 May 2017 12:52:13 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:53.0) Gecko/20100101 Thunderbird/53.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.