[Bug 1802233] Comment bridged from LTC Bugzilla

2019-06-07 Thread bugproxy
--- Comment From youh...@us.ibm.com 2019-06-07 14:04 EDT--- I don't know if this is a BMC issue either. With your latest note, I still do not understand the problem on Boston. Whether this is a HWCLOCK setting issue or HWCLOCK setting is working but have a long delay... Can you help

[Bug 1802233] Comment bridged from LTC Bugzilla

2019-06-06 Thread bugproxy
--- Comment From youh...@us.ibm.com 2019-06-06 13:19 EDT--- bugproxy, I did see the command. However, it was not clear if that what trigger the failure. The details of the problem isn't clear. Any way, you have not answer my first question yet... is there github issue associate with

[Bug 1802233] Comment bridged from LTC Bugzilla

2019-06-04 Thread bugproxy
--- Comment From youh...@us.ibm.com 2019-06-04 16:47 EDT--- is there issue associate with this problem? How does one recreate this problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1802233] Comment bridged from LTC Bugzilla

2019-05-21 Thread bugproxy
--- Comment From sesm...@au1.ibm.com 2019-05-21 21:46 EDT--- (In reply to comment #25) > (In reply to comment #24) > > 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. > > > Hi Stewart, > >

[Bug 1802233] Comment bridged from LTC Bugzilla

2019-05-21 Thread bugproxy
--- Comment From vipar...@in.ibm.com 2019-05-21 11:58 EDT--- (In reply to comment #24) > 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. Hi Stewart, Please let know if a BMC firmware release

[Bug 1802233] Comment bridged from LTC Bugzilla

2019-05-17 Thread bugproxy
--- Comment From vipar...@in.ibm.com 2019-05-17 15:22 EDT--- We had bugs reported in past also about hwclock not working on P9. LTC 155321 is one of such bugs. Its likely openBMC issue here. As per latest comment in bug 155321 The issue if already fixed by