User Details
- User Since
- Jul 27 2015, 9:08 PM (559 w, 3 d)
Yesterday
Tue, Apr 14
Mon, Apr 13
Damn, I forgot about this review. But fixing those compilation errors from the PR and the one reported here is only one part of the problem. Another one is that the built binary crashes (still before the package is built). I needed to sync os_bsd_ppc.cpp with os_linux_ppc.cpp to fix that. I'm not sure which single change actually fixed the crash.
Sun, Apr 12
Thu, Apr 9
Tue, Apr 7
Sat, Apr 4
Thu, Apr 2
Mon, Mar 30
Sun, Mar 29
Wed, Mar 25
Tue, Mar 24
Mar 16 2026
Mar 9 2026
Mar 7 2026
Mar 6 2026
Mar 4 2026
Mar 2 2026
Feb 25 2026
Feb 24 2026
Feb 23 2026
Feb 21 2026
Feb 18 2026
Feb 16 2026
Feb 11 2026
Feb 3 2026
Feb 1 2026
Jan 30 2026
Jan 22 2026
Jan 21 2026
Jan 20 2026
Jan 19 2026
Jan 15 2026
Jan 14 2026
Jan 12 2026
Jan 9 2026
Jan 8 2026
Jan 5 2026
Dec 31 2025
Dec 30 2025
Dec 27 2025
Dec 22 2025
Dec 16 2025
That's ok for me, but I thought that things work by default.
The real problem is mentioned here: https://wiki.freebsd.org/BjoernZeeb/Ten64
If loaded as module from multi-user we do not get the time set even if manually triggering a sysctl debug.clock_do_io=1. Reason for this is that vfs_moutroot() is responsible to have the clock set and calls CLOCK_GETTIME() indirectly so that log files or other timestamps do not appear to go backwards (if no RTC is found it'll use the vfs root node date?). Look for the inittodr() call.
