Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1641000
| From | PGNet Dev <pgnet.dev@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? |
| Date | 2017-05-13 22:10 +0200 |
| Message-ID | <tGLwt-8r2-7@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <tGJXH-7hM-3@gated-at.bofh.it> <tGKTM-7SS-15@gated-at.bofh.it> <tGLd8-82A-9@gated-at.bofh.it> <tGLd8-82A-7@gated-at.bofh.it> <tGLmN-88a-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 04:40 +0200
Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Randy Dunlap <rdunlap@infradead.org> - 2017-05-13 19:50 +0200
Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 20:30 +0200
Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Randy Dunlap <rdunlap@infradead.org> - 2017-05-13 21:30 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 21:50 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Andrew Cooper <andrew.cooper3@citrix.com> - 2017-05-13 22:00 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 22:10 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Andrew Cooper <andrew.cooper3@citrix.com> - 2017-05-13 22:20 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 23:10 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Juergen Gross <jgross@suse.com> - 2017-05-14 19:20 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Valentin Vidic <Valentin.Vidic@CARNet.hr> - 2017-05-13 22:30 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 23:10 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Valentin Vidic <Valentin.Vidic@CARNet.hr> - 2017-05-13 23:40 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-14 00:00 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Valentin Vidic <Valentin.Vidic@CARNet.hr> - 2017-05-14 00:20 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-14 01:20 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Andrew Cooper <andrew.cooper3@citrix.com> - 2017-05-14 17:50 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Randy Dunlap <rdunlap@infradead.org> - 2017-05-14 19:50 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? "Austin S. Hemmelgarn" <ahferroin7@gmail.com> - 2017-05-15 20:10 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-17 02:20 +0200
Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Andrew Cooper <andrew.cooper3@citrix.com> - 2017-05-13 22:10 +0200
Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? PGNet Dev <pgnet.dev@gmail.com> - 2017-05-13 22:00 +0200
Re: HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS? Clemens Ladisch <clemens@ladisch.de> - 2017-05-13 22:00 +0200
csiph-web