Re: vmt(4) module does not correctly report IP address to vCenter

2021-01-07 Thread Klemens Nanni
On Wed, Jan 06, 2021 at 11:46:04PM -0700, Alex Long wrote: > Software in use: > ESXi / vCenter 7.0U1 > OpenBSD 6.8 I'm not using Packer or OpenBSD on ESXi, but I just installed the latest snapshot on ESXi/vCenter 7.0U1 to see. > It seems like the vmt module is populating the legacy

select performance regression

2021-01-07 Thread Alexander Bluhm
Hi, As you can see here, the iperf3 udp performance dropped by 29% at 22nd December. http://bluhm.genua.de/perform/results/2021-01-05T15%3A48%3A19Z/gnuplot/udp.png All numbers for each commit at that day are here: http://bluhm.genua.de/perform/results/2021-01-05T15%3A48%3A19Z/perform.html It is

Re: A sparc oddity (hair-pulling bug)

2021-01-07 Thread Miod Vallat
> However, are there any other similar fallouts outside this initmsgbuf() > situation? There is only a risk on platforms where initmsgbuf() is invoked in (or before) pmap_bootstrap(), and where curcpu() will not necessarily point into the kernel data section for the boot processor. That

Re: doas: Fix null-pointer dereference

2021-01-07 Thread Quentin Rameau
> Hi, Hello again, > Here's a patch fixing a null pointer dereference when PATH is unset in > doas env. > This doesn't get triggered by OpenBSD libc strdup on amd64 though. Actually scratch that, this bug appeared in a “portable” version of doas, but this isn't reproducible in OpenBSD because

Re: A sparc oddity (hair-pulling bug)

2021-01-07 Thread Visa Hankala
On Thu, Jan 07, 2021 at 11:51:02AM -, Miod Vallat wrote: > > >> Indeed. Wrappinge the mutex operations in msgbuf_putchar with if (!cold) > >> makes the kernel boot again. > > > > Here is a diff for that. > > After a bit more thinking, it might be worth introduce a > msgbuf_putchar_unlocked()

Re: Fwd: Re: Protectli FW1 with Intel 82583V - Interfaces errors and latency spike issue

2021-01-07 Thread Mark Kettenis
> Date: Thu, 7 Jan 2021 22:03:15 +1000 > From: Jonathan Matthew > > On Wed, Jan 06, 2021 at 12:53:45PM +0100, Mark Kettenis wrote: > > > Date: Wed, 6 Jan 2021 21:29:52 +1000 > > > From: Jonathan Matthew > > > > > > On Wed, Jan 06, 2021 at 10:52:48AM +0100, Mark Kettenis wrote: > > > > > Date:

Re: A sparc oddity (hair-pulling bug)

2021-01-07 Thread Mark Kettenis
> From: Miod Vallat > Date: Thu, 7 Jan 2021 11:51:02 - (UTC) > > >> Indeed. Wrappinge the mutex operations in msgbuf_putchar with if (!cold) > >> makes the kernel boot again. > > > > Here is a diff for that. > > After a bit more thinking, it might be worth introduce a >

Re: Fwd: Re: Protectli FW1 with Intel 82583V - Interfaces errors and latency spike issue

2021-01-07 Thread Jonathan Matthew
On Wed, Jan 06, 2021 at 12:53:45PM +0100, Mark Kettenis wrote: > > Date: Wed, 6 Jan 2021 21:29:52 +1000 > > From: Jonathan Matthew > > > > On Wed, Jan 06, 2021 at 10:52:48AM +0100, Mark Kettenis wrote: > > > > Date: Wed, 6 Jan 2021 20:29:09 +1100 > > > > From: Jonathan Gray > > > > > > > > On

Re: A sparc oddity (hair-pulling bug)

2021-01-07 Thread Miod Vallat
>> Indeed. Wrappinge the mutex operations in msgbuf_putchar with if (!cold) >> makes the kernel boot again. > > Here is a diff for that. After a bit more thinking, it might be worth introduce a msgbuf_putchar_unlocked() routine for the inner part only, and have initmsgbuf() use it, since: - it

Re: Fwd: Re: Protectli FW1 with Intel 82583V - Interfaces errors and latency spike issue

2021-01-07 Thread steve
On 2021-01-05 23:52, Mark Kettenis wrote: Date: Wed, 6 Jan 2021 20:29:09 +1100 From: Jonathan Gray On Tue, Jan 05, 2021 at 10:28:20PM -1000, st...@wdwd.me wrote: > I tested with a Protectli FW1 router (dmesg below) forwarding packets > between two test machines. The latency spikes occur when

Re: A sparc oddity (hair-pulling bug)

2021-01-07 Thread Visa Hankala
On Thu, Jan 07, 2021 at 07:08:05AM +, Miod Vallat wrote: > > The per-CPU struct is mapped using a 64K locked TLB entry. That TLB > > entry is installed by sun4u_bootstrap_cpu(), which gets called *after* > > initsmgbuf() is called. So this issue was introduced when locking was > > added to

Re: Fwd: Re: Protectli FW1 with Intel 82583V - Interfaces errors and latency spike issue

2021-01-07 Thread steve
The drmwq processes are more active without a monitor connected: load averages: 0.09, 0.05, 0.01 test2.lan.local 22:50:50 73 processes: 69 idle, 4 on processor up 0:39 CPU0: 0.0% user, 0.0% nice, 3.8% sys, 0.0% spin, 0.2% intr,