cmos_interrupt not getting called
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
New
|
Undecided
|
Unassigned | ||
linux-oracle-5.15 (Ubuntu) |
Fix Committed
|
Medium
|
Cory Todd | ||
Focal |
Fix Released
|
Medium
|
Cory Todd | ||
Jammy |
Fix Released
|
Medium
|
Cory Todd |
Bug Description
The ubuntu_
This was observed on jammy:linux-
- 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.
sudo bpftrace -e 'kprobe:
Attaching 1 probe...
kprobe:
On -1031 no interrupt is detected for both the alarm and update tests.
CVE References
tags: |
added: sru-20230227 removed: sr20230227 |
description: | updated |
affects: | linux-oracle (Ubuntu) → linux-oracle-5.15 (Ubuntu) |
Changed in linux-oracle-5.15 (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Cory Todd (corytodd) |
importance: | Undecided → Medium |
Changed in linux-oracle-5.15 (Ubuntu Focal): | |
assignee: | nobody → Cory Todd (corytodd) |
Changed in linux-oracle-5.15 (Ubuntu Jammy): | |
assignee: | nobody → Cory Todd (corytodd) |
Changed in linux-oracle-5.15 (Ubuntu Focal): | |
status: | New → In Progress |
Changed in linux-oracle-5.15 (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in linux-oracle-5.15 (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in linux-oracle-5.15 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux-oracle-5.15 (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in linux-oracle-5.15 (Ubuntu Focal): | |
importance: | Undecided → Medium |
Changed in linux-oracle-5.15 (Ubuntu Jammy): | |
importance: | Undecided → Medium |
Changed in linux-oracle-5.15 (Ubuntu Jammy): | |
status: | Fix Committed → Fix Released |
tags: | added: sru-20230515 |
After some more debugging I found that the AIE bits are getting set which agrees with our attempt to set the alarm. We also see that the pnp probe is completing successfully as evident by this dmesg entry:
[ 1.715329] rtc_cmos 00:00: RTC can wake from S4
[ 1.721453] rtc_cmos 00:00: registered as rtc0
[ 1.727449] rtc_cmos 00:00: setting system clock to 2023-03-16T21:43:47 UTC (1679003027)
[ 1.736086] rtc_cmos 00:00: alarms up to one day, y3k, 114 bytes nvram
That would only show if cmos_do_probe completely normally. It appears that acpi_cmos_ wake_setup (formerly rtc_wake_setup) is not called on the same code paths as it previously was.