From: PGNet Dev <pgnet.dev@gmail.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Randy Dunlap <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?
Date: Sat, 13 May 2017 12:52:13 -0700 [thread overview]
Message-ID: <d547e939-3e41-4ad8-e6fe-fc1680169c5f@gmail.com> (raw)
In-Reply-To: <c7b93327-e866-957c-a564-a92829d54197@ladisch.de>
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.
prev parent reply other threads:[~2017-05-13 19:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 2:30 PGNet Dev
2017-05-13 17:41 ` Randy Dunlap
2017-05-13 18:26 ` PGNet Dev
2017-05-13 19:28 ` Randy Dunlap
2017-05-13 19:38 ` [Xen-devel] " Andrew Cooper
2017-05-13 19:49 ` PGNet Dev
2017-05-13 19:59 ` Andrew Cooper
2017-05-13 20:05 ` PGNet Dev
2017-05-13 20:16 ` Andrew Cooper
2017-05-13 21:07 ` PGNet Dev
2017-05-14 17:13 ` Juergen Gross
2017-05-13 20:28 ` Valentin Vidic
2017-05-13 21:06 ` PGNet Dev
2017-05-13 21:32 ` Valentin Vidic
2017-05-13 21:58 ` PGNet Dev
2017-05-13 22:15 ` Valentin Vidic
2017-05-13 23:17 ` PGNet Dev
2017-05-14 15:39 ` Andrew Cooper
2017-05-14 17:41 ` Randy Dunlap
2017-05-15 18:06 ` Austin S. Hemmelgarn
2017-05-17 0:12 ` PGNet Dev
2017-05-17 0:15 ` PGNet Dev
2017-05-13 19:45 ` Clemens Ladisch
2017-05-13 19:52 ` PGNet Dev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d547e939-3e41-4ad8-e6fe-fc1680169c5f@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®