Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

2017-05-13 Thread Clemens Ladisch
Randy Dunlap wrote: > On 05/12/17 19:30, PGNet Dev wrote: >> dmesg | grep -i hpet >> [8.491738] hpet_acpi_add: no address or irqs in _CRS > > Above line marks a big failure. > ^^^ > >> Disassembling the firmware acpi tables >>

Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

2017-05-13 Thread Clemens Ladisch
Randy Dunlap wrote: > On 05/12/17 19:30, PGNet Dev wrote: >> dmesg | grep -i hpet >> [8.491738] hpet_acpi_add: no address or irqs in _CRS > > Above line marks a big failure. > ^^^ > >> Disassembling the firmware acpi tables >>

Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

2017-05-13 Thread PGNet Dev
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

Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

2017-05-13 Thread PGNet Dev
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

Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

2017-05-13 Thread Randy Dunlap
On 05/13/17 11:26, PGNet Dev wrote: > On 5/13/17 10:41 AM, Randy Dunlap wrote: >> [adding HPET driver maintainer] > > Thanks > >> A couple of comments below... > >>> In BIOS, HPET's enabled. >> >> How about if you just boot Linux without Xen? Does HPET show up then? > > yes, it appears so: >

Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

2017-05-13 Thread Randy Dunlap
On 05/13/17 11:26, PGNet Dev wrote: > On 5/13/17 10:41 AM, Randy Dunlap wrote: >> [adding HPET driver maintainer] > > Thanks > >> A couple of comments below... > >>> In BIOS, HPET's enabled. >> >> How about if you just boot Linux without Xen? Does HPET show up then? > > yes, it appears so: >

Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

2017-05-13 Thread PGNet Dev
On 5/13/17 10:41 AM, Randy Dunlap wrote: [adding HPET driver maintainer] Thanks A couple of comments below... In BIOS, HPET's enabled. How about if you just boot Linux without Xen? Does HPET show up then? yes, it appears so: cat devices/system/clocksource/clocksource0/available

Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

2017-05-13 Thread PGNet Dev
On 5/13/17 10:41 AM, Randy Dunlap wrote: [adding HPET driver maintainer] Thanks A couple of comments below... In BIOS, HPET's enabled. How about if you just boot Linux without Xen? Does HPET show up then? yes, it appears so: cat devices/system/clocksource/clocksource0/available

Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

2017-05-13 Thread Randy Dunlap
[adding HPET driver maintainer] A couple of comments below... On 05/12/17 19:30, PGNet Dev wrote: > I run kernel 4.11.0-4 on a Supermicro X10SAT motherboard. > > HPET's enabled in BIOS, and apparently firmware table data is available. > > But, hpet is not an available_clocksource. > >

Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

2017-05-13 Thread Randy Dunlap
[adding HPET driver maintainer] A couple of comments below... On 05/12/17 19:30, PGNet Dev wrote: > I run kernel 4.11.0-4 on a Supermicro X10SAT motherboard. > > HPET's enabled in BIOS, and apparently firmware table data is available. > > But, hpet is not an available_clocksource. > >