[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin20041 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Tags added: hwclock -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Tags added: cscc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
@cypressyew that sounds reasonable, the only word of caution here is we should not dismiss future bugs detected on this system as "expected to fail", because the problem is in the 3rd party BMC firmware *and not* in the Pnor FW or Power9 hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
>From my point of view, I think we should leave the test case as-is, it helped us to identify this firmware issue. And it might be able to catch another FW issues on other platforms in the future. For this specific HW, we can make a note for the test result by using this bug report. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
IBM indicated that they do not have an ETA for a GA release of the BMC firmware with this fix. Would the kernel team be ok with working around this issue in the testcase by adding a .5 delay? ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Changed in: ubuntu-power-systems Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
I upgraded the firmware on tiselius (boston p9) and ran the testcase and it works as expected. ubuntu@tiselius:~$ sudo /sbin/hwclock --set --date "2019/06/10 12:55:00"; sudo /sbin/hwclock 2019-06-10 12:54:59.969984+00:00 ubuntu@tiselius:~$ should I wait for the release version of the firmware before I upgrade the other boston systems? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
I tried some test fw for the boston: ubuntu@ltc-boston25:~$ sudo /sbin/hwclock --set --date "2019/06/10 12:55:00"; sudo /sbin/hwclock --verbose [sudo] password for ubuntu: hwclock from util-linux 2.33.1 System Time: 1560377530.955292 Trying to open: /dev/rtc0 Using the rtc interface to the clock. Last drift adjustment done at 1560189300 seconds after 1969 Last calibration done at 1560189300 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ioctl(4, RTC_UIE_ON, 0): Invalid argument Waiting in loop for time from /dev/rtc0 to change ...got clock tick Time read from Hardware Clock: 2019/06/10 17:55:01 Hw clock time : 2019/06/10 17:55:01 = 1560189301 seconds since 1969 Time since last adjustment is 1 second Calculated Hardware Clock drift is 0.00 seconds 2019-06-10 12:55:00.022780-05:00 ubuntu@ltc-boston25:~$ But I still have: ubuntu@ltc-boston25:~$ sudo /sbin/hwclock --set --date "2004/11/21 04:10:00"; sudo strace -e ioctl "/sbin/hwclock" ioctl(4, RTC_UIE_ON)= -1 EINVAL (Invalid argument) ioctl(4, RTC_RD_TIME, {tm_sec=0, tm_min=10, tm_hour=10, tm_mday=21, tm_mon=10, tm_year=104, ...}) = 0 ioctl(4, RTC_RD_TIME, {tm_sec=1, tm_min=10, tm_hour=10, tm_mday=21, tm_mon=10, tm_year=104, ...}) = 0 ioctl(4, RTC_RD_TIME, {tm_sec=1, tm_min=10, tm_hour=10, tm_mday=21, tm_mon=10, tm_year=104, ...}) = 0 2004-11-21 04:10:00.018862-06:00 +++ exited with 0 +++ ubuntu@ltc-boston25:~$ But it generally seems to work - if I don't include any args it does set correctly still: ubuntu@ltc-boston25:~$ sudo /sbin/hwclock --set --date "2019/06/10 12:55:00"; sudo /sbin/hwclock 2019-06-10 12:54:59.982163-05:00 ubuntu@ltc-boston25:~$ Anything else you suggest? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
Opened issue 1423 on this - unfortunately the boston openpower is closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
Sorry did not realize that all the comments were not correctly mirrored over. A launchpad bug was reported by the Ubuntu kernel team as a result of their testing in the lab. We were not sure if this was a BMC issue, a hardware issue or kernel bug, so there is no github report as of now. If you think this is related to the BMC I can open a github bug. Also please tell us how to open bugs for BMC on Bostons. == P9 Boston == There seems to be a delay between setting the hwclock and reading from it. ubuntu@tiselius:~$ sudo /sbin/hwclock --set --date "2004/11/21 04:10:00"; sudo strace -e ioctl "/sbin/hwclock" ioctl(4, RTC_UIE_ON) = -1 EINVAL (Invalid argument) ioctl(4, RTC_RD_TIME, {tm_sec=0, tm_min=10, tm_hour=4, tm_mday=21, tm_mon=10, tm_year=104, ...}) = 0 ioctl(4, RTC_RD_TIME, {tm_sec=0, tm_min=10, tm_hour=4, tm_mday=21, tm_mon=10, tm_year=104, ...}) = 0 when the hwclock command fails, the ioctl that fails is RTC_RD_TIME.. but running it with --verbose probably gives it just enough time to complete the sync. Or you could use the command as follows: ubuntu@tiselius:~$ sudo /sbin/hwclock --set --date "2004/11/22 04:10:00"; sudo /sbin/hwclock --delay=0.5 2004-11-22 04:09:59.898618+00:00 ubuntu@tiselius:~$ == P9 Witherspoon == On the Witherspoon the hwclock does not seem to set at all. ubuntu@bobone:~$ uname -a Linux bobone 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:21:11 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@bobone:~$ sudo /sbin/hwclock --set --date "2004/11/22 04:10:00"; sudo /sbin/hwclock 2019-05-15 14:36:33.802253+ ubuntu@bobone:~$ sudo /sbin/hwclock --set --date "2004/11/22 04:10:00"; sudo /sbin/hwclock --debug hwclock from util-linux 2.31.1 System Time: 1557931207.255519 Trying to open: /dev/rtc0 Using the rtc interface to the clock. Last drift adjustment done at 1101096600 seconds after 1969 Last calibration done at 1101096600 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ioctl(4, RTC_UIE_ON, 0): Invalid argument Waiting in loop for time from /dev/rtc0 to change ...got clock tick Time read from Hardware Clock: 2019/05/15 14:40:08 Hw clock time : 2019/05/15 14:40:08 = 1557931208 seconds since 1969 Time since last adjustment is 456834608 seconds Calculated Hardware Clock drift is 0.00 seconds 2019-05-15 14:40:07.171582+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
@youhour are you able to see the comments in the launchpad bug? If not you could reproduce the issue using a command like: $ sudo /sbin/hwclock --set --date "2004/10/25 04:10:00"; sudo /sbin/hwclock -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
Michael, Is there any information from supermicro that you can share with us over here? If this is not going to be fixed then we might have to modify the testcase to use a workaround. Please let us know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
Changing owner to "bugproxy" as the next steps are with IBM on the Witherspoon and Boston firmware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Changed in: ubuntu-power-systems Assignee: Canonical Kernel Team (canonical-kernel-team) => bugproxy (bugproxy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Changed in: ubuntu-power-systems Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
Would a similar BMC firmware release from AMI fix this issue for Bostons systems? and is there an ETA for when that will be available to us. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Tags added: architecture-ppc64le bugnameltc-177684 severity-high targetmilestone-inin--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
-- Witherspoon firmware -- Server: IBM-witherspoon-OP9-v2.2-9.56 BMC: ibm-v2.3-476-g2d622cb-r30-0-g862e40a -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
On the Witherspoon the hwclock does not seem to set at all. ubuntu@bobone:~$ uname -a Linux bobone 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:21:11 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@bobone:~$ sudo /sbin/hwclock --set --date "2004/11/22 04:10:00"; sudo /sbin/hwclock 2019-05-15 14:36:33.802253+ ubuntu@bobone:~$ sudo /sbin/hwclock --set --date "2004/11/22 04:10:00"; sudo /sbin/hwclock --debug hwclock from util-linux 2.31.1 System Time: 1557931207.255519 Trying to open: /dev/rtc0 Using the rtc interface to the clock. Last drift adjustment done at 1101096600 seconds after 1969 Last calibration done at 1101096600 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ioctl(4, RTC_UIE_ON, 0): Invalid argument Waiting in loop for time from /dev/rtc0 to change ...got clock tick Time read from Hardware Clock: 2019/05/15 14:40:08 Hw clock time : 2019/05/15 14:40:08 = 1557931208 seconds since 1969 Time since last adjustment is 456834608 seconds Calculated Hardware Clock drift is 0.00 seconds 2019-05-15 14:40:07.171582+ ** Description changed: The hwclock test will fail on the Power9 system "baltar" due to a <0.02 second difference. Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in run_once raise error.TestFail("Failed to set hwclock back to Warthog's birthday. Output of hwclock is '%s'" % date) TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock is '2004-10-20 04:09:59.582146+' Didn't see this on Power8 boxes Sometimes it will fail because "time out waiting for time change" on the same node: $ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock hwclock: Timed out waiting for time change. Workaround for these is to add "sleep 1". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 03:45 seq crw-rw 1 root audio 116, 33 Nov 8 03:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Thu Nov 8 06:03:54 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654 ProcLocks: 1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF 2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF 3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF 4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF 5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_dscr: DSCR is 16 cpu_freq: min: 2.862 GHz (cpu 159) max: 2.862 GHz (cpu 1) avg: 2.862 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 + + --
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
Tested with the latest mainline kernel on Baltar: ubuntu@baltar:~$ uname -a Linux baltar 5.1.1-050101-generic #201905110631 SMP Sat May 11 07:16:36 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux This issue still exist. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
So looks like it is slow to sync with RTC. ubuntu@tiselius:~$ sudo /sbin/hwclock --set --date "2004/11/21 04:10:00"; sudo strace -e ioctl "/sbin/hwclock" ioctl(4, RTC_UIE_ON)= -1 EINVAL (Invalid argument) ioctl(4, RTC_RD_TIME, {tm_sec=0, tm_min=10, tm_hour=4, tm_mday=21, tm_mon=10, tm_year=104, ...}) = 0 ioctl(4, RTC_RD_TIME, {tm_sec=0, tm_min=10, tm_hour=4, tm_mday=21, tm_mon=10, tm_year=104, ...}) = 0 when the hwclock command fails, the ioctl that fails is RTC_RD_TIME.. but running it with --verbose probably gives it just enough time to complete the sync. Or you could use the command as follows: ubuntu@tiselius:~$ sudo /sbin/hwclock --set --date "2004/11/22 04:10:00"; sudo /sbin/hwclock --delay=0.5 2004-11-22 04:09:59.898618+00:00 ubuntu@tiselius:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
If you use it in verbose mode it works. It could be that it is slow to read from the rtc and the verbose mode just enough time to sync? ubuntu@tiselius:~$ sudo /sbin/hwclock --set --date "2004/10/25 04:10:00"; sudo /sbin/hwclock --verbose hwclock from util-linux 2.33.1 System Time: 1557759815.855012 Trying to open: /dev/rtc0 Using the rtc interface to the clock. Last drift adjustment done at 1098677400 seconds after 1969 Last calibration done at 1098677400 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ioctl(4, RTC_UIE_ON, 0): Invalid argument Waiting in loop for time from /dev/rtc0 to change ...got clock tick Time read from Hardware Clock: 2004/10/25 04:10:01 Hw clock time : 2004/10/25 04:10:01 = 1098677401 seconds since 1969 Time since last adjustment is 1 second Calculated Hardware Clock drift is 0.00 seconds 2004-10-25 04:09:59.806484+00:00 ubuntu@tiselius:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
Next step is for the kernel team to assess whether this is a test case issue, or a real kernel bug. ** Changed in: ubuntu-power-systems Importance: Undecided => Medium ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: ubuntu-power-systems Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Also affects: ubuntu-power-systems Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
This issue could be found on node "dradis" as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802233 Title: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
** Description changed: - The hwclock test will fail on the Power9 system due to a <0.02 second - difference + The hwclock test will fail on the Power9 system "baltar" due to a <0.02 + second difference. Traceback (most recent call last): - File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec - _call_test_function(self.execute, *p_args, **p_dargs) - File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function - return func(*args, **dargs) - File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute - postprocess_profiled_run, args, dargs) - File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once - self.run_once(*args, **dargs) - File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in run_once - raise error.TestFail("Failed to set hwclock back to Warthog's birthday. Output of hwclock is '%s'" % date) + File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec + _call_test_function(self.execute, *p_args, **p_dargs) + File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function + return func(*args, **dargs) + File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute + postprocess_profiled_run, args, dargs) + File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once + self.run_once(*args, **dargs) + File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in run_once + raise error.TestFail("Failed to set hwclock back to Warthog's birthday. Output of hwclock is '%s'" % date) TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock is '2004-10-20 04:09:59.582146+' Didn't see this on Power8 boxes + + Sometimes it will fail because "time out waiting for time change" on the same node: + $ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock + hwclock: Timed out waiting for time change. + + Workaround for these is to add "sleep 1". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-38-generic 4.15.0-38.41 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic ppc64le AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Nov 8 03:45 seq - crw-rw 1 root audio 116, 33 Nov 8 03:45 timer + total 0 + crw-rw 1 root audio 116, 1 Nov 8 03:45 seq + crw-rw 1 root audio 116, 33 Nov 8 03:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: - + Date: Thu Nov 8 06:03:54 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. - Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd - Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. + Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd + Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: - + ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.31 0.11 0.03 1/1392 5654 ProcLocks: - 1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF - 2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF - 3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF - 4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF - 5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF + 1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF + 2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF + 3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF + 4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF + 5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF ProcSwaps: - Filename TypeSizeUsedPriority - /swap.img file 8388544 0 -2 + Filename TypeSizeUsedPriority + /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC 2018 RelatedPackageVersions: - linux-restricted-modules-4.15.0-38-generic N/A - linux-backports-modules-4.15.0-38-generic N/A - linux-firmware 1