panic: rw_enter: netlock locking against myself (NFS related?)

I see this reproduceably when, eg doing cvs ops with Feb 5 snap. I found a thread from a couple of weeks ago but AFAICT the diff in that thread is already in. panic: rw_enter: netlock locking against myself Stopped at Debugger+0x9: leave TIDPIDUID PRFLAGS PFLAGS CPU

Re: SSD read performance benchmark OpenBSD 6.0 vs. Linux 4.7: OpenBSD will benefit of multiqueueing and also a speedup for sequential reads, and Linux' mmap() is extremely slow for random reads.

2017-02-09 Mikael : > Dear misc@, > > *## Intro, environment* > Find below a comparative benchmark of OpenBSD 6.0 vs Linux 4.7 read speeds > on a 3.3Ghz Xeon E3 server with a Samsung 850 Pro 256GB SATA SSD, which is > one of the very fastest SSD:s in the sub-1000USD/TB

Per-device multiqueuing would be fantastic. Are there any plans? Are donations a matter here?

Hi misc@, The SSD reading benchmark in the previous email shows that per-device multiqueuing will boost multithreaded random read performance very much e.g. by ~7X+, e.g. the current 50MB/sec will increase to ~350MB/sec+. (I didn't benchmark yet but I suspect the current 50MB/sec is system-wide,

SSD read performance benchmark OpenBSD 6.0 vs. Linux 4.7: OpenBSD will benefit of multiqueueing and also a speedup for sequential reads, and Linux' mmap() is extremely slow for random reads.

Dear misc@, *## Intro, environment* Find below a comparative benchmark of OpenBSD 6.0 vs Linux 4.7 read speeds on a 3.3Ghz Xeon E3 server with a Samsung 850 Pro 256GB SATA SSD, which is one of the very fastest SSD:s in the sub-1000USD/TB price range. dmesg below. No dual-disk case was tested.

Re: relayd send/expect syntax

On Tue, Feb 07, 2017 at 05:04:18PM -0500, Michael W. Lucas wrote: > host 104.236.197.233, check send expect (9020ms,tcp read timeout), state > unknown -> down, availability 0.00% The send/expect code looses its error because of its async nature - it goes like: 1. "we got data, let's verify it"

Re: Funding for Skylake support

On 01/07, Jordon wrote: > > On Jan 7, 2017, at 2:19 PM, Peter Membrey wrote: > > > > Hi all, > > > > I've gotten OpenBSD up and running on a new Intel NUC, but unfortunately > Skylake isn't supported. I was able to get X working in software accelerated > mode, but it would be

collecting relayd check scripts?

Hi, I'm collecting relayd check scripts for the httpd/relayd book. If you have a check script that you don't mind sharing, please send it to me. Regards, ==ml -- Michael W. LucasTwitter @mwlauthor nonfiction: https://www.michaelwlucas.com/ fiction: https://www.michaelwarrenlucas.com/

Re: splassert: yield message on 5 Feb snapshot (amd64)

On 8.2.2017. 17:51, Scott Vanderbilt wrote: > Updated a machine to latest (5 Feb.) snapshot of amd64. I'm now seeing > the following message after booting that I've not recalled seeing before: > >splassert: yield: want 0 have 1 add sysctl kern.splassert=2 ...

splassert: yield message on 5 Feb snapshot (amd64)

Updated a machine to latest (5 Feb.) snapshot of amd64. I'm now seeing the following message after booting that I've not recalled seeing before: splassert: yield: want 0 have 1 Looking in the list archives, I see a thread from Sept. 2016 where the following response from Theo Buehler is

Re: relayd send/expect syntax

> Running the most recent amd64 snapshot on ESXi. > > OpenBSD r1.mwlucas.org 6.0 GENERIC#162 amd64 > > I'm trying to use relayd's check send/expect support to verify a > daemon's banner comes up. After problems I've stripped this down to > the simplest possible config, a single known good mail

Re: sendsyslog: dropped 4 messages, error 55

Hi, Am 30.01.2017 um 18:17 schrieb Peter Fraser: > My /var/log/messages is filling up with messages like the following: > > Jan 30 10:28:06 gateway sendsyslog: dropped 4 messages, error 55 > Jan 30 10:28:06 gateway sendsyslog: dropped 2 messages, error 55 > Jan 30 10:28:06 gateway sendsyslog:

jme0: watchdog timeout

Hi, I use OpenBSD 6.0 amd64 (stable) on a Shuttle XS35v2. I've installed "ushare" but same problem with "minidlna" and I don't think the problem comes from these apps... When I try to read a big file (ex.: a 1Go video) from my DLNA player, nothing starts playing and the jme driver on the Shuttle