From: <ja...@as...> - 2023-06-21 21:44:21
|
Miroslav, Thanks for the suggestions- Found chrony running so I stopped and disabled chronyd. Still see the problem. I have another older computer running RHEL 7.9 with an Asus mb and a I219-LM chip on the same local net and it works properly. I tried the RHEL 8.8 OS that was not working with the Supermicro mb on the Asus mb with an I219-LM chip and it worked. I tried the RHEL 8.8 OS on a third computer that has the new Supermicro mb with the same hardware as the original and I still saw the error. Based on the testing steps above, the three main differences are motherboard, cpu and the I219-LM rev. The working 219 chip reports rev 10 where the one that reports an error is rev 11. It seems like a driver would be the most likely problem. A quick look at the Intel website indicates that the e1000e drivers have changed to a kernel-only support model. Jason On 2023-06-20 09:24, Miroslav Lichvar wrote: > On Tue, Jun 20, 2023 at 09:05:10AM -0600, ja...@as... wrote: >> ptp4l[1068.939]: clockcheck: clock jumped forward or running faster >> than >> expected! >> ptp4l[1068.939]: rms 630332770 max 822762571 freq +23999999 +/- 0 >> delay >> -27609959 +/- 3559790 > > This shows the frequency being stuck at the maximum. The server, HW or > driver > is broken, or something else is adjusting the clock. |