linux-kernel - Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

lists.openwall.net		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 14:06:28 -0700
From:   PGNet Dev <pgnet.dev@...il.com>
To:     Valentin Vidic <Valentin.Vidic@...Net.hr>
Cc:     Andrew Cooper <andrew.cooper3@...rix.com>,
        Randy Dunlap <rdunlap@...radead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Clemens Ladisch <clemens@...isch.de>,
        xen-devel@...ts.xenproject.org
Subject: Re: [Xen-devel] HPET enabled in BIOS, not presented as
 available_clocksource -- config, kernel code, &/or BIOS?

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