The breaking commit is
f2a7f3238777 ("rtc: rtc-cmos: Do not check ACPI_FADT_LOW_POWER_S0")
Reverting this commit restores the expected AIE and UIE behavior.
** Description changed:
The ubuntu_ltp_kernel_misc rtc01 test case has exposed a possible
regression of the RTC cmos driver on certain Oracle clouds.
This was observed on jammy:linux-oracle-5.15.0-1031.37.
- VM.DenseIO2.8
- VM.Standard2.1
rtc01 0 TINFO : RTC READ TEST:
rtc01 1 TPASS : RTC READ TEST Passed
rtc01 0 TINFO : Current RTC date/time is 16-3-2023, 17:36:04.
rtc01 0 TINFO : RTC ALARM TEST :
rtc01 0 TINFO : Alarm time set to 17:36:09.
rtc01 0 TINFO : Waiting 5 seconds for the alarm...
rtc01 2 TFAIL : rtc01.c:151: Timed out waiting for the alarm
rtc01 0 TINFO : RTC UPDATE INTERRUPTS TEST :
rtc01 0 TINFO : Waiting for 5 update interrupts...
rtc01 3 TFAIL : rtc01.c:208: Timed out waiting for the update
interrupt
rtc01 0 TINFO : RTC Tests Done!
Notice that we successfully enable RTC_AIE_ON, unlike
VM.Standard.A1.Flex-4c.8m which does not support it. I confirmed with
bpftrace on -1029 that we see the cmos interrupt (part of ltp
read_alarm_test)
sudo bpftrace -e 'kprobe:cmos_interrupt { printf("%s\n", probe) }'
Attaching 1 probe...
kprobe:cmos_interrupt
- On -1031 no interrupt is detected. I think this might be caused by
-
- 017314318ad4 ("rtc: cmos: Call cmos_wake_setup() from cmos_do_probe()")
+ On -1031 no interrupt is detected for both the alarm and update tests.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/2011854
Title:
cmos_interrupt not getting called
Status in linux-oracle package in Ubuntu:
New
Bug description:
The ubuntu_ltp_kernel_misc rtc01 test case has exposed a possible
regression of the RTC cmos driver on certain Oracle clouds.
This was observed on jammy:linux-oracle-5.15.0-1031.37.
- VM.DenseIO2.8
- VM.Standard2.1
rtc01 0 TINFO : RTC READ TEST:
rtc01 1 TPASS : RTC READ TEST Passed
rtc01 0 TINFO : Current RTC date/time is 16-3-2023, 17:36:04.
rtc01 0 TINFO : RTC ALARM TEST :
rtc01 0 TINFO : Alarm time set to 17:36:09.
rtc01 0 TINFO : Waiting 5 seconds for the alarm...
rtc01 2 TFAIL : rtc01.c:151: Timed out waiting for the alarm
rtc01 0 TINFO : RTC UPDATE INTERRUPTS TEST :
rtc01 0 TINFO : Waiting for 5 update interrupts...
rtc01 3 TFAIL : rtc01.c:208: Timed out waiting for the update
interrupt
rtc01 0 TINFO : RTC Tests Done!
Notice that we successfully enable RTC_AIE_ON, unlike
VM.Standard.A1.Flex-4c.8m which does not support it. I confirmed with
bpftrace on -1029 that we see the cmos interrupt (part of ltp
read_alarm_test)
sudo bpftrace -e 'kprobe:cmos_interrupt { printf("%s\n", probe) }'
Attaching 1 probe...
kprobe:cmos_interrupt
On -1031 no interrupt is detected for both the alarm and update tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2011854/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
