https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236702
R.L. Dane <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #6 from R.L. Dane <[email protected]> --- I've noticed that `sysctl kern.boottime` even shows different boot **times** after S3 suspend: $ uptime; sysctl kern.boottime 8:47AM up 1:54, 4 users, load averages: 0.04, 0.15, 0.15 kern.boottime: { sec = 1765284843, usec = 713731 } Tue Dec 9 06:54:03 2025 $ $ # ((( S3 sleep for almost 9 hours ))) $ $ uptime; sysctl kern.boottime 5:35PM up 1:54, 4 users, load averages: 0.30, 0.20, 0.17 kern.boottime: { sec = 1765316465, usec = 19718 } Tue Dec 9 15:41:05 2025 Note that the boot time changes from 06:54 to 15:45 after S3 resume. Surely, that's a bug. I can understand someone saying that uptime *shouldn't* count time asleep for some reason (even though I doubt it), but actually changing the boot time to move it up by the same amount the system has been in S3 sleep doesn't make any sense. Also, Linux does not behave like this, and I don't think OpenBSD or NetBSD do, either. -- You are receiving this mail because: You are the assignee for the bug.
