On 4/12/25 04:35, Nicklas SB Karlsson wrote:
Think I had some similar problem with a computer years ago. Might have been
something with the graphics card I had to
disable but can't remember.
OK, I have had a similar problem on a Beagle Bone computer.
The issue was tracked down to bad times left in the system
log, and the computer booting up with ancient time of day
settings that dated back to when it was compiled. This was
on a point-to-point network where we were not permitted to
get onto the hospital's internal network. Do you have a
network time server on your network, that can provide
correct time to the computer when it boots up? If not, can
the computer reach a network time server on the wide area
net? Is that address programmed in?
The issue seems to be when the system starts with an ancient
time setting, runs for a couple hours and is then shut
down. the clock at shutdown is ancient + 2 hours. Then,
next time you boot, the time is set back to "ancient", ie, 2
hours BEFORE the last time in the logs. This causes any
process that needs some privilege, like LinuxCNC, to hang
for some timeout period.
I don't know if this is Gene's problem, but it sounds like
it could be.
One manual fix was to set the clock to the actual time with
the date command.
Jon
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
