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  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]
Date:   Sat, 13 May 2017 22:28:11 +0200
From:   Valentin Vidic <>
To:     PGNet Dev <>
Cc:     Andrew Cooper <>,
        Randy Dunlap <>,
        "" <>,
        Clemens Ladisch <>,
Subject: Re: [Xen-devel] HPET enabled in BIOS, not presented as
 available_clocksource -- config, kernel code, &/or BIOS?

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` and not `dmesg` output?

On Debian jessie it looks like the hypervisor is using
HPET by default as expected:

# xl dmesg | grep -i hpet
(XEN) ACPI: HPET 7986E860, 0038 (r1 SUPERM SMCI--MB        1 INTL 20091013)
(XEN) Platform timer is 14.318MHz HPET

# dmesg | grep -i hpet
[    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[   64.157167] hpet_acpi_add: no address or irqs in _CRS


Powered by blists - more mailing lists