6723 2014-09-13 19:01:58 +0000 hpet: number irqs doesn't agree with number of timers 2017-06-13 18:04:22 +0000 1 1 12 Hardware Platforms MinnowBoard MAX Firmware minnowboard-uefi-firmware 2C A1 MinnowBoard Max Multiple RESOLVED MOVED Medium normal Production Release 1 marcel shifeix.a.lu danders david.wei dvhart shifeix.a.lu sjolley.yp.pm yoctoproject --- --- No (bug/feature does not impact docs) oldest_to_newest 45607 0 marcel 2014-09-13 19:01:58 +0000 I am seeing this message in the boot logs: x86/hpet: Will disable the HPET for this platform because it's not reliable Is this a general Baytrail issue or is something wrong here? I assumed every modern platform has HPET these days. According to kernel sources, we have this comment in there: /* * HPET on current version of Baytrail platform has accuracy * problems, disable it for now: */ { PCI_VENDOR_ID_INTEL, 0x0f00, PCI_CLASS_BRIDGE_HOST, PCI_ANY_ID, 0, force_disable_hpet}, So does this also affect the Baytrail version that is in the Minnowboard or has this been fixed? If HPET is of course disabled, then this causes also this from the driver: [ 1.927750] hpet: number irqs doesn't agree with number of timers Maybe it would be safer to not expose the HPET at all if it is broken anyway. 45615 1 dvhart 2014-09-15 16:11:28 +0000 I'm trying to get more detail on this issue from the SoC experts... will report back. 45638 2 dvhart 2014-09-16 20:29:28 +0000 It appears this impacts s0ix only, so not Baytrail-I/M. We need to investigate how to ensure this is supported in the OS. 50753 3 dvhart 2015-05-04 15:46:23 +0000 Mike, can your team do some initial triage/investigation on this? Are we deliberately disabling the HPET or are we falling back to some default policy which may not apply to this SoC (E38XX)? 52608 4 david.wei 2015-07-27 02:04:06 +0000 Assign to Shifei to invesitgate. 74095 5 sjolley.yp.pm 2017-06-13 18:04:22 +0000 We are no longer tracking in Yocto Project Bugzilla MinnowBoard and MinnowBoard-MAX HW and firmware bugs.