From: PGNet Dev <pgnet.dev@gmail.com>
To: Valentin Vidic <Valentin.Vidic@CARNet.hr>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Randy Dunlap <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Clemens Ladisch <clemens@ladisch.de>,
xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?
Date: Sat, 13 May 2017 14:06:28 -0700 [thread overview]
Message-ID: <df6ea7bf-43f7-d331-a37e-802f3d984a96@gmail.com> (raw)
In-Reply-To: <20170513202811.j5mhumhvow3gadms@gavran.carpriv.carnet.hr>
On 5/13/17 1:28 PM, Valentin Vidic wrote:
> On Sat, May 13, 2017 at 01:05:22PM -0700, PGNet Dev wrote:
>> back to the error at hand ...
>>
>> xl dmesg | grep -i hpet
>> [ 1.365876] hpet_acpi_add: no address or irqs in _CRS
>> [ 1.365876] hpet_acpi_add: no address or irqs in _CRS
>>
>> again, only present when booting with Xen.
>>
>> same kernel, no Xen, no such error.
>
> Are you sure this is `xl dmesg`
yep.
xl dmesg | grep -i hpet | grep -vi command
[ 1.365876] hpet_acpi_add: no address or irqs in _CRS
[ 1.365876] hpet_acpi_add: no address or irqs in _CRS
> and not `dmesg` output?
AND
dmesg | grep -i hpet | grep -vi command
[ 0.000000] ACPI: HPET 0x000000009E8298F8 000038 (v01 SUPERM
SMCI--MB 01072009 AMI. 00000005)
[ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[ 1.365876] hpet_acpi_add: no address or irqs in _CRS
next prev parent reply other threads:[~2017-05-13 21:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 2:30 HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? 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:38 ` Andrew Cooper
2017-05-13 19:49 ` [Xen-devel] " PGNet Dev
2017-05-13 19:59 ` Andrew Cooper
2017-05-13 20:05 ` PGNet Dev
2017-05-13 20:05 ` PGNet Dev
2017-05-13 20:16 ` [Xen-devel] " Andrew Cooper
2017-05-13 21:07 ` PGNet Dev
2017-05-13 21:07 ` [Xen-devel] " PGNet Dev
2017-05-14 17:13 ` Juergen Gross
2017-05-14 17:13 ` Juergen Gross
2017-05-13 20:16 ` Andrew Cooper
2017-05-13 20:28 ` [Xen-devel] " Valentin Vidic
2017-05-13 21:06 ` PGNet Dev
2017-05-13 21:06 ` PGNet Dev [this message]
2017-05-13 21:32 ` Valentin Vidic
2017-05-13 21:32 ` [Xen-devel] " 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 15:39 ` [Xen-devel] " Andrew Cooper
2017-05-14 17:41 ` Randy Dunlap
2017-05-14 17:41 ` [Xen-devel] " Randy Dunlap
2017-05-15 18:06 ` Austin S. Hemmelgarn
2017-05-17 0:12 ` PGNet Dev
2017-05-17 0:12 ` [Xen-devel] " PGNet Dev
2017-05-17 0:15 ` PGNet Dev
2017-05-17 0:15 ` [Xen-devel] " PGNet Dev
2017-05-15 18:06 ` Austin S. Hemmelgarn
2017-05-13 23:17 ` PGNet Dev
2017-05-13 22:15 ` Valentin Vidic
2017-05-13 21:58 ` PGNet Dev
2017-05-13 20:28 ` Valentin Vidic
2017-05-13 19:59 ` Andrew Cooper
2017-05-13 19:49 ` PGNet Dev
2017-05-13 19:28 ` Randy Dunlap
2017-05-13 19:45 ` Clemens Ladisch
2017-05-13 19:52 ` PGNet Dev
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=df6ea7bf-43f7-d331-a37e-802f3d984a96@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=Valentin.Vidic@CARNet.hr \
--cc=andrew.cooper3@citrix.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.