[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
** Tags added: sru-20230515
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2011854
Title:
cmos_interrupt not getting called
Status in ubuntu-kernel-tests:
New
Status in linux-oracle-5.15 package in Ubuntu:
Fix Committed
Status in linux-oracle-5.15 source package in Focal:
Fix Released
Status in linux-oracle-5.15 source package in Jammy:
Fix Released
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-kernel-tests/+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
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2011854
Title:
cmos_interrupt not getting called
Status in ubuntu-kernel-tests:
New
Status in linux-oracle-5.15 package in Ubuntu:
Fix Committed
Status in linux-oracle-5.15 source package in Focal:
Fix Released
Status in linux-oracle-5.15 source package in Jammy:
Fix Released
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-kernel-tests/+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
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
This is now affecting K-oracle-5.19.0-1020.23, on these two instances like in
the bug report:
- VM.DenseIO2.8
- VM.Standard2.1
** Tags added: 5.19 kinetic oracle sru-20230320 ubuntu-ltp-kernel-misc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2011854
Title:
cmos_interrupt not getting called
Status in linux-oracle-5.15 package in Ubuntu:
Fix Committed
Status in linux-oracle-5.15 source package in Focal:
Fix Released
Status in linux-oracle-5.15 source package in Jammy:
Fix Released
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-5.15/+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
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
** Changed in: linux-oracle-5.15 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2011854
Title:
cmos_interrupt not getting called
Status in linux-oracle-5.15 package in Ubuntu:
Fix Committed
Status in linux-oracle-5.15 source package in Focal:
Fix Released
Status in linux-oracle-5.15 source package in Jammy:
Fix Released
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-5.15/+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
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
This bug was fixed in the package linux-oracle-5.15 - 5.15.0-1032.38~20.04.1 --- linux-oracle-5.15 (5.15.0-1032.38~20.04.1) focal; urgency=medium * focal/linux-oracle-5.15: 5.15.0-1032.38~20.04.1 -proposed tracker (LP: #2012656) [ Ubuntu: 5.15.0-1032.38 ] * jammy/linux-oracle: 5.15.0-1032.38 -proposed tracker (LP: #2012655) * cmos_interrupt not getting called (LP: #2011854) - SAUCE: Revert "rtc: rtc-cmos: Do not check ACPI_FADT_LOW_POWER_S0" linux-oracle-5.15 (5.15.0-1031.37~20.04.1) focal; urgency=medium * focal/linux-oracle-5.15: 5.15.0-1031.37~20.04.1 -proposed tracker (LP: #2008340) [ Ubuntu: 5.15.0-1031.37 ] * jammy/linux-oracle: 5.15.0-1031.37 -proposed tracker (LP: #2008342) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * jammy/linux: 5.15.0-68.75 -proposed tracker (LP: #2008349) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.02.27) * Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs (LP: #1987430) - SAUCE: audit: fix memory leak of audit_log_lsm() * [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release (LP: #2003267) - intel_idle: add SPR support - intel_idle: add 'preferred_cstates' module argument - intel_idle: add core C6 optimization for SPR - cpuidle: intel_idle: Drop redundant backslash at line end - intel_idle: Fix the 'preferred_cstates' module parameter - intel_idle: Fix SPR C6 optimization - intel_idle: make SPR C1 and C1E be independent * Fix speaker mute hotkey doesn't work on Dell G16 series (LP: #2003161) - platform/x86: dell-wmi: Add a keymap for KEY_MUTE in type 0x0010 table * Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares (LP: #2006077) - ACPI: bus: Avoid using CPPC if not supported by firmware - ACPI: bus: Set CPPC _OSC bits for all and when CPPC_LIB is supported - ACPI: CPPC: Only probe for _CPC if CPPC v2 is acked * rtcpie in timers from ubuntu_kernel_selftests randomly failing (LP: #1814234) - SAUCE: selftest: rtcpie: Force passing unreliable subtest * Jammy update: v5.15.87 upstream stable release (LP: #2007441) - usb: dwc3: qcom: Fix memory leak in dwc3_qcom_interconnect_init - cifs: fix oops during encryption - nvme-pci: fix doorbell buffer value endianness - nvme-pci: fix mempool alloc size - nvme-pci: fix page size checks - ACPI: resource: do IRQ override on LENOVO IdeaPad - ACPI: resource: do IRQ override on XMG Core 15 - ACPI: resource: do IRQ override on Lenovo 14ALC7 - block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq - ata: ahci: Fix PCS quirk application for suspend - nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition - nvmet: don't defer passthrough commands with trivial effects to the workqueue - fs/ntfs3: Validate BOOT record_size - fs/ntfs3: Add overflow check for attribute size - fs/ntfs3: Validate data run offset - fs/ntfs3: Add null pointer check to attr_load_runs_vcn - fs/ntfs3: Fix memory leak on ntfs_fill_super() error path - fs/ntfs3: Add null pointer check for inode operations - fs/ntfs3: Validate attribute name offset - fs/ntfs3: Validate buffer length while parsing index - fs/ntfs3: Validate resident attribute name - fs/ntfs3: Fix slab-out-of-bounds read in run_unpack - soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 - fs/ntfs3: Validate index root when initialize NTFS security - fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() - fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() - fs/ntfs3: Delete duplicate condition in ntfs_read_mft() - fs/ntfs3: Fix slab-out-of-bounds in r_page - objtool: Fix SEGFAULT - powerpc/rtas: avoid device tree lookups in rtas_os_term() - powerpc/rtas: avoid scheduling in rtas_os_term() - HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint - HID: plantronics: Additional PIDs for double volume key presses quirk - pstore: Properly assign mem_type property - pstore/zone: Use GFP_ATOMIC to allocate zone buffer - hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount - binfmt: Fix error return code in load_elf_fdpic_binary() - ovl: Use ovl mounter's fsuid and fsgid in ovl_link() - ALSA: line6: correct midi status byte when receiving data from podxt - ALSA: line6: fix stack overflow in line6_midi_transmit - pnode: terminate at peers of source - mfd: mt6360: Add bounds checking in Regmap read/write call-backs - md: fix a crash in mempool_free - mm, compaction: fix fast_isolate_around() to stay within boundaries - f2fs: should put a page when checking the summary info - f2fs: allow to read node block after shutdown - mmc: vub300: fix
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
** Changed in: linux-oracle-5.15 (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-oracle-5.15 (Ubuntu Jammy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2011854
Title:
cmos_interrupt not getting called
Status in linux-oracle-5.15 package in Ubuntu:
Fix Committed
Status in linux-oracle-5.15 source package in Focal:
Fix Committed
Status in linux-oracle-5.15 source package in Jammy:
Fix Committed
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-5.15/+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
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
** 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
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2011854
Title:
cmos_interrupt not getting called
Status in linux-oracle-5.15 package in Ubuntu:
Fix Committed
Status in linux-oracle-5.15 source package in Focal:
Fix Committed
Status in linux-oracle-5.15 source package in Jammy:
Fix Committed
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-5.15/+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
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
** Package changed: linux-oracle (Ubuntu) => linux-oracle-5.15 (Ubuntu)
** Changed in: linux-oracle-5.15 (Ubuntu)
Status: New => In Progress
** Changed in: linux-oracle-5.15 (Ubuntu)
Assignee: (unassigned) => Cory Todd (corytodd)
** Changed in: linux-oracle-5.15 (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux-oracle-5.15 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oracle-5.15 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-oracle-5.15 (Ubuntu Focal)
Assignee: (unassigned) => Cory Todd (corytodd)
** Changed in: linux-oracle-5.15 (Ubuntu Jammy)
Assignee: (unassigned) => 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
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2011854
Title:
cmos_interrupt not getting called
Status in linux-oracle-5.15 package in Ubuntu:
In Progress
Status in linux-oracle-5.15 source package in Focal:
In Progress
Status in linux-oracle-5.15 source package in Jammy:
In Progress
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-5.15/+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
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
The core issue is that with f2a7f3238777, the kernel on the affected
systems no longer uses hpet for the rtc alarm and update interrupts.
This may indicate that their non-hpet implementation is faulty. By
removing the ACPI_FADT_LOW_POWER_S0 check from use_acpi_alaram_quirks,
the kernel expects to use the acpi alarm by way of use_hpet_alarm().
Other facts:
- this patch has only been applied to Jammy. Kinetic and Focal do not have the
latest patches affecting rtc-cmos.
- applying these patches to jammy:linux-gcp work correctly on a g1-small
instance. This system is able to use the acpi alarm for both alarm and update
interrupts.
I see two options:
1) Revert f2a7f3238777 as a SAUCE patch. The justification for this commit
seems to be based on the suspend-to-idle use case, notwithstanding the alarm
from S0 use case.
2) Patch in a more specific quirk and get it upstreamed. It seems like the
quirk that was removed was hiding a bug on this particular system.
--
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
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
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
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
I confirmed that the kernel -update (-1030) does is able to pass this
test.
--
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. I think this might be caused by
017314318ad4 ("rtc: cmos: Call cmos_wake_setup() from
cmos_do_probe()")
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
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
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.
--
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. I think this might be caused by
017314318ad4 ("rtc: cmos: Call cmos_wake_setup() from
cmos_do_probe()")
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
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
** 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
+ 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
- kprobe:cmos_interrupt
- kprobe:cmos_interrupt
- kprobe:cmos_interrupt
- kprobe:cmos_interrupt
- 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()")
--
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. I think this might be caused by
017314318ad4 ("rtc: cmos: Call cmos_wake_setup() from
cmos_do_probe()")
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
[Kernel-packages] [Bug 2011854] Re: cmos_interrupt not getting called
** Tags removed: sr20230227
** Tags added: sru-20230227
--
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
sudo bpftrace -e 'kprobe:cmos_interrupt { printf("%s\n", probe) }'
Attaching 1 probe...
kprobe:cmos_interrupt
kprobe:cmos_interrupt
kprobe:cmos_interrupt
kprobe:cmos_interrupt
kprobe:cmos_interrupt
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()")
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
