** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin20041
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x
** Tags added: hwclock
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in 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
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in 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
Status
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x
@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
>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.
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
** Changed in: ubuntu-power-systems
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec
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
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
Opened issue 1423 on this - unfortunately the boston openpower is
closed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec
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
@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 Kernel
Packages, which is
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 Kernel
Packages, which is
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
** Changed in: ubuntu-power-systems
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: architecture-ppc64le bugnameltc-177684 severity-high
targetmilestone-inin---
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9
-- 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test
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
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 Kernel
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,
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:
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
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x
This issue could be found on node "dradis" as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
** 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
28 matches
Mail list logo
