[DragonFlyBSD - Bug #3299] DragonFlyBSD reports utterly wrong uptime (most of the time, right after booting in)

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #3299 has been updated by liweitianux.


I could reproduce this issue with the following simpler qemu command:

<pre>
qemu-system-x86_64 \
-machine type=pc-i440fx-7.2,accel=kvm,hpet=off \
-smp cpus=2 -m 4G \
-cdrom dfly.iso -boot d \
-drive file=disk1.qcow2,if=none,id=disk0 -device virtio-blk-pci,drive=disk0 \
-netdev user,id=net0,hostfwd=tcp:127.0.0.1:6033-:22 \
-device virtio-net-pci,netdev=net0 \
-object rng-random,id=rng0,filename=/dev/urandom -device virtio-rng-pci,rng=rng0 \
-display gtk,window-close=off \
-vga qxl -spice addr=127.0.0.1,port=5900,ipv4=on,disable-ticketing=on,seamless-migration=on
</pre>

The wrong uptime could happen on first boot, but more likely happen after one/two reboots.

By the way, enabling HPET (by removing the @-no-hpet@ or the @hpet=off@) should also fix the uptime.

----------------------------------------
Bug #3299: DragonFlyBSD reports utterly wrong uptime (most of the time, right after booting in)
http://bugs.dragonflybsd.org/issues/3299#change-14606

* 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