| Summary: | hpet: number irqs doesn't agree with number of timers | ||
|---|---|---|---|
| Product: | [Hardware Platforms] MinnowBoard MAX Firmware | Reporter: | Marcel Holtmann <marcel> |
| Component: | minnowboard-uefi-firmware | Assignee: | Lu_Shifei <shifeix.a.lu> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | danders, david.wei, dvhart, shifeix.a.lu, sjolley.yp.pm, yoctoproject |
| Version: | 2C A1 | ||
| Target Milestone: | Production Release | ||
| Hardware: | MinnowBoard Max | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
I'm trying to get more detail on this issue from the SoC experts... will report back. It appears this impacts s0ix only, so not Baytrail-I/M. We need to investigate how to ensure this is supported in the OS. 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)? Assign to Shifei to invesitgate. We are no longer tracking in Yocto Project Bugzilla MinnowBoard and MinnowBoard-MAX HW and firmware bugs. |
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.