[DragonFlyBSD - Bug #3299] DragonFlyBSD reports utterly wrong uptime (most of the time, right after booting in)
bugtracker-admin at leaf.dragonflybsd.org
bugtracker-admin at leaf.dragonflybsd.org
Wed Aug 20 00:06:46 PDT 2025
Issue #3299 has been updated by liweitianux.
I'm not sure whether TSC would work with the legacy i440fx machine.
On the other hand, please try and enable the HPET timer in libvirt:
<pre>
$ virsh edit <guest>
<clock offset='utc'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='yes'/>
</clock>
</pre>
Basically, set the @hpet@ timer to @present='yes'@.
In addition, the new q35 machine should work, except that QEMU may choose the new v1 virtio devices, which is not yet supported, meh :(
See also the bug: https://bugs.dragonflybsd.org/issues/3323
----------------------------------------
Bug #3299: DragonFlyBSD reports utterly wrong uptime (most of the time, right after booting in)
http://bugs.dragonflybsd.org/issues/3299#change-14599
* Author: adrian
* Status: In Progress
* Priority: Normal
* Category: Userland
* Target version: 6.4
* Start date: 2021-10-25
----------------------------------------
System environment:
<pre>
root at dragonflybsd /home/adrian
# uname -a
DragonFly dragonflybsd.v-zone.lan.dac 6.0-RELEASE DragonFly v6.0.1-RELEASE #1: Thu Oct 14 18:25:27 CEST 2021 adrian at dragonflybsd.v-zone.lan.dac:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64
</pre>
Running DragonFlyBSD inside a Debian KVM(qemu) virtualization as a guest with hardware acceleration,
the system reports a very wrong uptime, issuing "uptime".
Gkrellm even reports a negative, very strange uptime! Check by running gkrellm from the pkg system.
After ~2 days of uptime, I see this wrong uptime:
<pre>
root at dragonflybsd /home/adrian
# uptime
6:35PM up 42954 days, 10:01, 2 users, load averages: 0,00 0,00 0,00
</pre>
The error also was present with Version 6.0.0. This is now Version 6.0.1 and the bug is still there.
Happens about three of four times, the bug is present right after booting into the system.
Thank you for taking the time reading this.
Sincerely,
Adrian Kieß
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
More information about the Bugs
mailing list