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 21:16:17 +0100
From:   Andrew Cooper <>
To:, Randy Dunlap <>,
        "" <>,
        Clemens Ladisch <>,, Juergen Gross <>
Cc:     Jan Beulich <>
Subject: Re: [Xen-devel] HPET enabled in BIOS, not presented as
 available_clocksource -- config, kernel code, &/or BIOS?

On 13/05/2017 21:05, PGNet Dev wrote:
> On 5/13/17 12:59 PM, Andrew Cooper wrote:
>> Ok.  Lack of a clocksource is to be expected.
>> The reason why the HPETs are unavailable is that dom0 is not a position
>> to program them; dom0 doesn't know what Xen has set up in the IDT.
>> Use `xl dmesg` to get to the hypervisor dmesg log.  You should see
>> mention of the HPET in there if Xen has found it.
> 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.

We don't have code like that in upstream Xen.  No function with that
name, or a string which looks like that error message. indicates that
you are using a SuSE hypervisor.

Jan/Juergen: Any ideas? This looks as if it is something local to your
patch queue.


Powered by blists - more mailing lists