<div dir="ltr"><div>Acked-by: Luke Nowakowski-Krijger <<a href="mailto:luke.nowakowskikrijger@canonical.com">luke.nowakowskikrijger@canonical.com</a>> </div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 22, 2023 at 8:50 PM Cory Todd <<a href="mailto:cory.todd@canonical.com">cory.todd@canonical.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">From: Cory Todd <<a href="mailto:cory.todd@canonical.com" target="_blank">cory.todd@canonical.com</a>> SRU Justification: BugLink: <a href="https://bugs.launchpad.net/bugs/2011854" rel="noreferrer" target="_blank">https://bugs.launchpad.net/bugs/2011854</a> [Impact] On amd64, the RTC alarm interrupt and update interrupt can be enabled but will never fire. [Fix] Revert the commit that disables the use of HPET. These systems do not have a functional CMOS RTC and have been relying on HPET for these interrupts to work. [Test Plan] 1. Provision three vms: both instance types reporting the regression and another instance type not reporting a regression. 2. Install and boot test kernel 3. Run ltp rtc01 regression test, all cases pass [Where Problems Could Occur] The BIOS on these systems could be updated and these interrupts would continue to use HPET even though a functional CMOS RTC might be available. Cory Todd (1): UBUNTU: SAUCE: Revert "rtc: rtc-cmos: Do not check ACPI_FADT_LOW_POWER_S0" drivers/rtc/rtc-cmos.c | 3 +++ 1 file changed, 3 insertions(+) -- 2.40.0 -- kernel-team mailing list <a href="mailto:kernel-team@lists.ubuntu.com" target="_blank">kernel-team@lists.ubuntu.com</a> <a href="https://lists.ubuntu.com/mailman/listinfo/kernel-team" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/kernel-team</a> </blockquote></div></div>