Virtio Viocon driver - possible to backport from OpenBSD?

2022-08-04 Thread Matthias Petermann
Hello, according: https://man.openbsd.org/virtio.4 the OpenBSD virtio driver has its origin in NetBSD. Viocon Support was added later and not ported back yet. I am wondering how much effort it would take to merge it from

daily CVS update output

2022-08-04 Thread NetBSD source update
Updating src tree: P src/common/lib/libprop/prop_object.c P src/sys/dev/fdt/fdt_memory.c P src/sys/dev/pci/if_bnx.c Updating xsrc tree: Killing core files: Updating file list: -rw-rw-r-- 1 srcmastr netbsd 40660970 Aug 5 03:03 ls-lRA.gz

Re: Weird clock behaviour with current (amd64) kernel

2022-08-04 Thread Robert Elz
Date:Thu, 4 Aug 2022 12:49:35 - (UTC) From:mlel...@serpens.de (Michael van Elst) Message-ID: | The measurement runs with enabled interrupts. If you have lots of interrupts | or interrupts that take some time, the measurement is biased. | | Console output

Re: Weird clock behaviour with current (amd64) kernel

2022-08-04 Thread Michael van Elst
k...@munnari.oz.au (Robert Elz) writes: >The issue only occurs when I boot a kernel with options PCI_CONFIG_DUMP >enabled, which is (one way or the other) almost certainly responsible for >the issue - though the problem you mention may be involved in the kernel's >failure to detect that the TSC

Re: Checksum mismatch of -HEAD and -STABLE sets on nycdn

2022-08-04 Thread Martin Husemann
On Wed, Aug 03, 2022 at 11:21:40PM +, RVP wrote: > Obviously, (most of) the checksums fail: > > $ printf '%s\n' *.xz | fgrep -f- SHA512 | sha1 -c > (SHA512) base.tar.xz: FAILED I can reproduce this and will file an admin ticket. A good way to get more information is to use curl like this:

Re: Weird clock behaviour with current (amd64) kernel

2022-08-04 Thread Robert Elz
Date:Wed, 3 Aug 2022 22:30:34 + From:David Holland Message-ID: | so if your previous kernel was fairly old and you | still have older boot logs lying around you might check them for | such notices. This is an entirely new system, the oldest kernel it has

Re: Weird clock behaviour with current (amd64) kernel

2022-08-04 Thread Michael van Elst
dholland-curr...@netbsd.org (David Holland) writes: >On Thu, Jul 14, 2022 at 08:59:25PM +0700, Robert Elz wrote: > > I just booted a kernel that I built (from up to date at the time) > > HEAD sources about 24 hours ago. > > > > Everything seemed to be working fine - until I noticed that all of >