-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clock_settime03 #712
Comments
That is a bit strange, the syscall that fails is timer_create() with CLOCK_REALTIME_ALARM. I guess that there may be missing support for RTC wakeup either in kernel or hardware. Does the test work if you change the CLOCK_REALTIME_ALARM into just CLOCK_REALTIME? |
From what I recall, the report was from ppc kvm guest. |
Well yes, but I do not see anything that would actually require the _ALARM clock, we do not suspend the OS in the middle, so it may be better to just change to plain CLOCK_REALTIME. |
For the record, we're seeing this failures on the following kernels as well (not fully tested on various releases yet): |
CLOCK_REALTIME_ALARM requires an RTC with alarm support, which may not be present on a system. In that case, the kernel will return EOPNOTSUPP, which is defined as ENOTSUP in userspace. Here use CLOCK_REALTIME instead of the CLOCK_REALTIME_ALARM because we do NOT need suspend the SUT during test. For issue #712: #712 Signed-off-by: Li Wang <liwang@redhat.com> Cc: Viresh Kumar<viresh.kumar@linaro.org> Cc: Cyril Hrubis <chrubis@suse.cz> Cc: Jan Stancek <jstancek@redhat.com> Tested-by: Li Wang <liwang@redhat.com> Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
this has been solved in 21721a3 |
While we updated to a recent commit for CKI, newly onboarded clock_settime03 test is failing with BROK: timer_create() failed: EOPNOTSUPP (95) error for all non x86_64 arches, see below:
The text was updated successfully, but these errors were encountered: