Re: bpf_validate() uses BPF_RVAL() when it should use BPF_SRC()

2010-04-21 Thread Otto Moerbeek
On Tue, Apr 20, 2010 at 05:14:05PM -0700, Guy Harris wrote: > In bpf_validate, when it checks whether the divisor in a BPF_DIV instruction > is a constant 0, it does > > case BPF_DIV: > /* >* Check for constant di

Re: [openbsd][amd64][bug][shutdown] the result of the shutdown +5 -p command is unexpected

2018-02-19 Thread Otto Moerbeek
On Mon, Feb 19, 2018 at 12:09:09PM +0100, david-mau...@netdefi.com wrote: > Hello, > > the result of the shutdown +5 -p command is unexpected : > Enter pathname of shell or return for sh > > How to repeat : > in a xfce4-terminal > shutdown +5 -p > > Regards, > David MAURER Depends on you epxec

Re: [openbsd][amd64][bug][shutdown] the result of the shutdown +5 -p command is unexpected

2018-02-19 Thread Otto Moerbeek
On Mon, Feb 19, 2018 at 12:29:08PM +0100, Otto Moerbeek wrote: > On Mon, Feb 19, 2018 at 12:09:09PM +0100, david-mau...@netdefi.com wrote: > > > Hello, > > > > the result of the shutdown +5 -p command is unexpected : > > Enter pathname of shell or return for sh >

Re: [openbsd][amd64][bug][shutdown] the result of the shutdown +5 -p command is unexpected

2018-02-19 Thread Otto Moerbeek
On Mon, Feb 19, 2018 at 12:30:19PM +0100, Otto Moerbeek wrote: > On Mon, Feb 19, 2018 at 12:29:08PM +0100, Otto Moerbeek wrote: > > > On Mon, Feb 19, 2018 at 12:09:09PM +0100, david-mau...@netdefi.com wrote: > > > > > Hello, > > > > > > the resul

Re: Bus error in smtpctl spf walk

2018-03-06 Thread Otto Moerbeek
On Tue, Mar 06, 2018 at 10:46:23AM +0100, Jan Johansson wrote: > >Synopsis:Bus error in smtpctl spf walk (on certain domains) > >Category:user > >Environment: > System : OpenBSD 6.3 > Details : OpenBSD 6.3-beta (GENERIC.MP) #26: Fri Mar 2 22:56:04 > MST 2018 >

Re: Bus error in smtpctl spf walk

2018-03-07 Thread Otto Moerbeek
On Wed, Mar 07, 2018 at 08:30:25AM +0100, Gilles Chehade wrote: > On Tue, Mar 06, 2018 at 01:13:11PM +0100, Otto Moerbeek wrote: > > On Tue, Mar 06, 2018 at 10:46:23AM +0100, Jan Johansson wrote: > > > > > >Synopsis:Bus error in smtpctl spf walk (on certa

Re: NFS keeps crashing

2018-04-21 Thread Otto Moerbeek
On Sat, Apr 21, 2018 at 10:09:38AM +0100, Stuart Henderson wrote: > > On Sat, Apr 21, 2018, 1:24 AM Rupert Gallagher wrote: > > > > > This is what I observed on a controlled environment of three "windows 10 > > > pro" 1709 clients. > > > > > > The obsd nfs server had a single share: > > > > > >

Re: NFS keeps crashing

2018-04-21 Thread Otto Moerbeek
On Sat, Apr 21, 2018 at 07:20:18PM -0400, Rupert Gallagher wrote: > On Sat, Apr 21, 2018 at 19:58, Otto Moerbeek wrote: > > > What do you mean by "the server crashes"? Does the complete OS freeze? Or > > is the OS still working apart from NFS? Did one of te NF

Re: NFS keeps crashing

2018-04-27 Thread Otto Moerbeek
On Fri, Apr 27, 2018 at 02:04:35PM -0400, Rupert Gallagher wrote: > Keeps crashing. > > ktrace attached. No immediate clue pops up from the ktrace. I don't think I wil find the time to debug this futher the coming period. -Otto > ​​ > > ‐‐‐ Original Message ‐‐‐ > > On 26 Apr

Re: NFS keeps crashing

2018-04-28 Thread Otto Moerbeek
On Fri, Apr 27, 2018 at 09:12:36PM -0400, Rupert Gallagher wrote: > The lack of information originates from "mountd -d". When it terminates > because of an error, it should log the name of the last function and its > parameters. Wrap your lines. Well, ktrace does that for system calls. What I'

Re: NFS keeps crashing

2018-04-28 Thread Otto Moerbeek
On Fri, Apr 27, 2018 at 07:29:50PM -0600, Theo de Raadt wrote: > For a while it was amazing watching someone completely misunderstand > the Zeitgeist of the circumstances this is open source, you get > all the pieces from people who largely care, but you also get all > the pieces so that you

Re: NFS keeps crashing

2018-04-28 Thread Otto Moerbeek
On Sat, Apr 28, 2018 at 10:40:01AM +0200, Philip Guenther wrote: > On Sat, 28 Apr 2018, Otto Moerbeek wrote: > > On Fri, Apr 27, 2018 at 09:12:36PM -0400, Rupert Gallagher wrote: > > > > > The lack of information originates from "mountd -d". When it termina

Re: NFS keeps crashing

2018-04-28 Thread Otto Moerbeek
On Sat, Apr 28, 2018 at 11:28:50AM +0200, Otto Moerbeek wrote: > On Sat, Apr 28, 2018 at 10:40:01AM +0200, Philip Guenther wrote: > > > On Sat, 28 Apr 2018, Otto Moerbeek wrote: > > > On Fri, Apr 27, 2018 at 09:12:36PM -0400, Rupert Gallagher wrote: > > > &

Re: i386 panic in uvm_addr_linsearch

2018-05-14 Thread Otto Moerbeek
On Sun, May 13, 2018 at 10:34:13PM +0200, Alexander Bluhm wrote: > Hi, > > When executing the posixtestsuite port, the i386 kernel crashes. > It is this one: > > /usr/local/libexec/posixtestsuite/conformance/interfaces/mmap/31-1.test > > bluhm This fixes the panic. The error returned is not ex

Re: NFS keeps crashing

2018-05-25 Thread Otto Moerbeek
On Sat, Apr 28, 2018 at 05:36:31PM -0400, Rupert Gallagher wrote: > Will try it asap. (It is tax season.) > > On Sat, Apr 28, 2018 at 10:40, Philip Guenther > wrote a patch. So this was almost a moint ago. Did you try Philip's diff? -Otto

Re: NFS keeps crashing

2018-05-25 Thread Otto Moerbeek
On Fri, May 25, 2018 at 12:20:31PM +0200, Otto Moerbeek wrote: > On Sat, Apr 28, 2018 at 05:36:31PM -0400, Rupert Gallagher wrote: > > > Will try it asap. (It is tax season.) > > > > On Sat, Apr 28, 2018 at 10:40, Philip Guenther > > wrote a patch. > > So

Re: ntpd(8) adds time since epoch to system clock

2020-08-07 Thread Otto Moerbeek
On Fri, Aug 07, 2020 at 11:17:18AM -0500, Scott Cheloha wrote: > On Mon, Aug 05, 2069 at 09:33:05AM +, Toby Betts wrote: > > >Synopsis: ntpd(8) adds time since epoch to system clock > > >Category: system > > >Environment: > > System : OpenBSD 6.6 > > Details : OpenBSD 6.6 (G

Re: ntpd still fails to notice unreachable server

2020-09-01 Thread Otto Moerbeek
On Tue, Sep 01, 2020 at 06:33:34PM +0200, Christian Weisgerber wrote: > Even after otto@'s commit in -current... > > If no replies are received for a while due to connectivity issues > go into unsynced mode. The existing code to check if we're unsycned > is only done on receiving an ntp pac

Re: ntpd still fails to notice unreachable server

2020-09-02 Thread Otto Moerbeek
On Tue, Sep 01, 2020 at 07:58:44PM +0200, Otto Moerbeek wrote: > On Tue, Sep 01, 2020 at 06:33:34PM +0200, Christian Weisgerber wrote: > > > Even after otto@'s commit in -current... > > > > If no replies are received for a while due to connectivity issues >

Re: ntpd still fails to notice unreachable server

2020-09-03 Thread Otto Moerbeek
On Thu, Sep 03, 2020 at 02:02:36PM +0200, Christian Weisgerber wrote: > Otto Moerbeek: > > > Currently testing this. > > For "port unreachable" replies, this caused ntpd to become unsynced, but > the peer still remains valid. Hmm, it looks like we need to reduce

Re: ntpd still fails to notice unreachable server

2020-09-03 Thread Otto Moerbeek
On Thu, Sep 03, 2020 at 02:33:05PM +0200, Otto Moerbeek wrote: > On Thu, Sep 03, 2020 at 02:02:36PM +0200, Christian Weisgerber wrote: > > > Otto Moerbeek: > > > > > Currently testing this. > > > > For "port unreachable" replies, this cause

Re: ntpd still fails to notice unreachable server

2020-09-04 Thread Otto Moerbeek
On Fri, Sep 04, 2020 at 11:17:40PM +0200, Christian Weisgerber wrote: > Otto Moerbeek: > > > This takes the observed issue into account, > -snip- > > This works for my test case of a single peer and the two scenarios of > "can't send query" and "port

Re: ntpd still fails to notice unreachable server

2020-09-08 Thread Otto Moerbeek
On Sat, Sep 05, 2020 at 08:11:21AM +0200, Otto Moerbeek wrote: > On Fri, Sep 04, 2020 at 11:17:40PM +0200, Christian Weisgerber wrote: > > > Otto Moerbeek: > > > > > This takes the observed issue into account, > > -snip- > > > > This works

Re: 4 of 8 cores always idle on Ryzen 7 4750U Pro

2020-11-08 Thread Otto Moerbeek
On Sat, Nov 07, 2020 at 11:24:22PM -0500, Ashton Fagg wrote: > >Synopsis: Core 1, 3, 5 & 7 are always idle. > >Category: bug > >Environment: > System : OpenBSD 6.8 > Details : OpenBSD 6.8-current (GENERIC.MP) #167: Sat Nov 7 > 00:10:46 MST 2020 > > de

Re: Installer autopartition chooses too small size for root partition?

2020-11-18 Thread Otto Moerbeek
On Wed, Nov 18, 2020 at 09:25:06AM +0100, ger...@macclub-os.de wrote: > >Synopsis:Recommendation: Installer chooses to small root partition > >Category:system > >Environment: > System : OpenBSD 6.8 > Details : OpenBSD 6.8 (GENERIC.MP) #1: Tue Nov 3 09:06:04 MST 2020 >

Re: Installer autopartition chooses too small size for root partition?

2020-11-18 Thread Otto Moerbeek
On Wed, Nov 18, 2020 at 08:58:48PM +0100, Otto Moerbeek wrote: > On Wed, Nov 18, 2020 at 09:25:06AM +0100, ger...@macclub-os.de wrote: > > > >Synopsis: Recommendation: Installer chooses to small root partition > > >Category: system > > >Environment:

Re: rge(4) interrupt storm

2020-11-20 Thread Otto Moerbeek
On Fri, Nov 20, 2020 at 11:09:25AM +0100, Mark Kettenis wrote: > It's a relatively new driver. It uses MSI which pretty much rules out > an issue with shared interrupts. So I suspect this is an issue with > the rge(4) driver. In the past we have fun with packet counter > overflow interrupts. I

Re: rge(4) interrupt storm

2020-11-20 Thread Otto Moerbeek
On Fri, Nov 20, 2020 at 02:01:55PM +0100, Claudio Jeker wrote: > On Fri, Nov 20, 2020 at 11:32:18AM +0100, Otto Moerbeek wrote: > > On Fri, Nov 20, 2020 at 11:09:25AM +0100, Mark Kettenis wrote: > > > > > It's a relatively new driver. It uses MSI which pretty much

Re: rge(4) interrupt storm

2020-11-21 Thread Otto Moerbeek
On Fri, Nov 20, 2020 at 04:25:31PM +0100, Otto Moerbeek wrote: > On Fri, Nov 20, 2020 at 02:01:55PM +0100, Claudio Jeker wrote: > > > On Fri, Nov 20, 2020 at 11:32:18AM +0100, Otto Moerbeek wrote: > > > On Fri, Nov 20, 2020 at 11:09:25AM +0100, Mark Kettenis wrote:

Re: OpenBSD crashing after being setup as a router hooked up to my modem

2020-11-21 Thread Otto Moerbeek
On Sat, Nov 21, 2020 at 05:20:37PM -0500, sam wrote: > >Environment: >     System  : OpenBSD 6.8 >     Details : OpenBSD 6.8 (GENERIC.MP) #1: Tue Nov  3 09:06:04 MST 2020 >  r...@syspatch-68-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > >     Architecture: OpenBSD.amd64 >

Re: apu4 fatal protection fault in supervisor mode [Was: apu4 kernel panic]

2020-11-29 Thread Otto Moerbeek
On Sun, Nov 29, 2020 at 06:38:15PM -, Christian Weisgerber wrote: > On 2020-11-29, Theo Buehler wrote: > > > Thanks for digging into this. Your APU seems much worse off than mine, > > which takes a few weeks before crashing these days, so it's not much use > > for bisecting. > > The APU2 th

Re: pthread: segfault with user stack

2020-12-01 Thread Otto Moerbeek
On Tue, Dec 01, 2020 at 10:13:29AM -0800, guent...@openbsd.org wrote: > On Tue, 1 Dec 2020, Sebastien Marie wrote: > > I have a random segfault while using threads with custom stack. > > > > In short, I am doing: > > - allocate a stack space for the thread > > - create a thread (with custom stack

Re: pthread: segfault with user stack

2020-12-01 Thread Otto Moerbeek
On Tue, Dec 01, 2020 at 08:00:18PM +0100, Otto Moerbeek wrote: > On Tue, Dec 01, 2020 at 10:13:29AM -0800, guent...@openbsd.org wrote: > > > On Tue, 1 Dec 2020, Sebastien Marie wrote: > > > I have a random segfault while using threads with custom stack. > > &g

Re: pthread: segfault with user stack

2020-12-01 Thread Otto Moerbeek
On Tue, Dec 01, 2020 at 01:14:22PM -0800, guent...@openbsd.org wrote: > On Tue, 1 Dec 2020, Otto Moerbeek wrote: > > On Tue, Dec 01, 2020 at 08:00:18PM +0100, Otto Moerbeek wrote: > > > On Tue, Dec 01, 2020 at 10:13:29AM -0800, guent...@openbsd.org wrote: > ... > > &

Re: pthread: segfault with user stack

2020-12-01 Thread Otto Moerbeek
On Wed, Dec 02, 2020 at 07:48:07AM +0100, Otto Moerbeek wrote: > On Tue, Dec 01, 2020 at 01:14:22PM -0800, guent...@openbsd.org wrote: > > > On Tue, 1 Dec 2020, Otto Moerbeek wrote: > > > On Tue, Dec 01, 2020 at 08:00:18PM +0100, Otto Moerbeek wrote: > > > > O

Re: pthread: segfault with user stack

2020-12-03 Thread Otto Moerbeek
On Wed, Dec 02, 2020 at 10:58:14AM +0100, Sebastien Marie wrote: > On Wed, Dec 02, 2020 at 08:29:15AM +0100, Otto Moerbeek wrote: > > > > Anyway, here's a man page diff > > another man page diff. > > > Zig upstream said that OpenBSD man page for pthread_joi

Re: getaddrinfo() is not thread-safe in 6.8

2020-12-23 Thread Otto Moerbeek
On Wed, Dec 23, 2020 at 11:58:30PM -0700, Theo de Raadt wrote: > Brad Smith wrote: > > > On 12/23/2020 10:35 PM, Alexey Sokolov wrote: > > >> Synopsis:getaddrinfo() is not thread-safe in 6.8 > > >> Category:system > > >> Environment: > > > System : OpenBSD 6.8 > > > Deta

Re: getaddrinfo() is not thread-safe in 6.8

2020-12-24 Thread Otto Moerbeek
On Thu, Dec 24, 2020 at 08:28:17AM +0100, Otto Moerbeek wrote: > On Wed, Dec 23, 2020 at 11:58:30PM -0700, Theo de Raadt wrote: > > > Brad Smith wrote: > > > > > On 12/23/2020 10:35 PM, Alexey Sokolov wrote: > > > >> Synopsis: getaddrinfo() i

Re: getaddrinfo() is not thread-safe in 6.8

2020-12-24 Thread Otto Moerbeek
On Thu, Dec 24, 2020 at 08:25:45AM +0100, Uli Schlachter wrote: > Hi everyone, > > Am 24.12.20 um 04:35 schrieb Alexey Sokolov: > [...] > > Hi, getaddrinfo() crashes when multiple threads run getaddrinfo() > > concurrently. This didn't happen in 6.7. > > It looks like asr_ctx which is supposed to

Re: getaddrinfo() is not thread-safe in 6.8

2020-12-24 Thread Otto Moerbeek
On Thu, Dec 24, 2020 at 10:36:37AM +0100, Otto Moerbeek wrote: > On Thu, Dec 24, 2020 at 08:25:45AM +0100, Uli Schlachter wrote: > > > Hi everyone, > > > > Am 24.12.20 um 04:35 schrieb Alexey Sokolov: > > [...] > > > Hi, getaddrinfo() crashe

Re: getaddrinfo() is not thread-safe in 6.8

2020-12-24 Thread Otto Moerbeek
On Thu, Dec 24, 2020 at 01:59:34PM +0100, Mark Kettenis wrote: > > Date: Thu, 24 Dec 2020 12:27:01 +0100 > > From: Otto Moerbeek > > > > On Thu, Dec 24, 2020 at 10:36:37AM +0100, Otto Moerbeek wrote: > > > > > On Thu, Dec 24, 2020 at 08:25:45AM +0100,

Re: getaddrinfo() is not thread-safe in 6.8

2020-12-24 Thread Otto Moerbeek
On Thu, Dec 24, 2020 at 02:28:25PM +0100, Otto Moerbeek wrote: > On Thu, Dec 24, 2020 at 01:59:34PM +0100, Mark Kettenis wrote: > > > > Date: Thu, 24 Dec 2020 12:27:01 +0100 > > > From: Otto Moerbeek > > > > > > On Thu, Dec 24, 2020 at 10:36:37AM +01

Re: Memory leak with getaddrinfo()

2020-12-25 Thread Otto Moerbeek
On Thu, Dec 24, 2020 at 01:29:28PM +0100, Uli Schlachter wrote: > Hi, > > due to that other thread, it occurred to me that getaddrinfo() also has > another bug: It leaks memory. _asr_use_resolver() allocates memory > per-thread (via _asr_resolver()) and saves it via _THREAD_PRIVATE() in > _asr, b

Re: Memory leak with getaddrinfo()

2020-12-25 Thread Otto Moerbeek
On Fri, Dec 25, 2020 at 12:35:57PM +0100, Mark Kettenis wrote: > > Date: Fri, 25 Dec 2020 11:34:47 +0100 > > From: Otto Moerbeek > > > > On Thu, Dec 24, 2020 at 01:29:28PM +0100, Uli Schlachter wrote: > > > > > Hi, > > > > > > due

Re: Memory leak with getaddrinfo()

2020-12-25 Thread Otto Moerbeek
On Fri, Dec 25, 2020 at 12:59:10PM +0100, Otto Moerbeek wrote: > On Fri, Dec 25, 2020 at 12:35:57PM +0100, Mark Kettenis wrote: > > > > Date: Fri, 25 Dec 2020 11:34:47 +0100 > > > From: Otto Moerbeek > > > > > > On Thu, Dec 24, 2020 at 01:29:28PM +010

Re: Memory leak with getaddrinfo()

2020-12-26 Thread Otto Moerbeek
On Fri, Dec 25, 2020 at 02:04:03PM +0100, Otto Moerbeek wrote: > On Fri, Dec 25, 2020 at 12:59:10PM +0100, Otto Moerbeek wrote: > > > On Fri, Dec 25, 2020 at 12:35:57PM +0100, Mark Kettenis wrote: > > > > > > Date: Fri, 25 Dec 2020 11:34:47 +0100 > > > >

Re: Memory leak with getaddrinfo()

2020-12-26 Thread Otto Moerbeek
On Sat, Dec 26, 2020 at 11:07:00AM +0100, Otto Moerbeek wrote: > On Fri, Dec 25, 2020 at 02:04:03PM +0100, Otto Moerbeek wrote: > > > On Fri, Dec 25, 2020 at 12:59:10PM +0100, Otto Moerbeek wrote: > > > > > On Fri, Dec 25, 2020 at 12:35:57PM +0100, Mark Kettenis w

Re: Memory leak with getaddrinfo()

2020-12-26 Thread Otto Moerbeek
On Sat, Dec 26, 2020 at 11:31:32AM +0100, Otto Moerbeek wrote: > On Sat, Dec 26, 2020 at 11:07:00AM +0100, Otto Moerbeek wrote: > > > On Fri, Dec 25, 2020 at 02:04:03PM +0100, Otto Moerbeek wrote: > > > > > On Fri, Dec 25, 2020 at 12:59:10PM +0100, Otto Moerbeek w

Re: Memory leak with getaddrinfo()

2020-12-27 Thread Otto Moerbeek
Hi, So here the diff that just fixes the mem leak on thread exit. It does not contains the TLS init part, I'd like to do that differently than what I did in the version I posted earlier. As stated before, this makes the getaddrino(3) test program run in constant memory. ok? -Otto Inde

Re: Memory leak with getaddrinfo()

2020-12-28 Thread Otto Moerbeek
On Mon, Dec 28, 2020 at 08:54:46PM +0100, Theo Buehler wrote: > On Sun, Dec 27, 2020 at 08:44:52PM +0100, Otto Moerbeek wrote: > > Hi, > > > > So here the diff that just fixes the mem leak on thread exit. It does > > not contains the TLS init part, I'd like to do

Re: Memory leak with getaddrinfo()

2020-12-30 Thread Otto Moerbeek
On Mon, Dec 28, 2020 at 09:21:04PM +0100, Otto Moerbeek wrote: > On Mon, Dec 28, 2020 at 08:54:46PM +0100, Theo Buehler wrote: > > > On Sun, Dec 27, 2020 at 08:44:52PM +0100, Otto Moerbeek wrote: > > > Hi, > > > > > > So here the diff that just fix

Re: rge(4) interrupt storm

2021-01-06 Thread Otto Moerbeek
On Wed, Jan 06, 2021 at 02:34:14PM -0800, xSAPPYx wrote: > On Sun, Nov 22, 2020 at 6:19 AM Mark Kettenis > wrote: > > > > Date: Sat, 21 Nov 2020 14:14:21 +0100 > > > From: Otto Moerbeek > > > > > > On Fri, Nov 20, 2020 at 04:25:31PM +0100, Otto

Re: munmap sometimes does coredump on arm after mmap success

2021-01-19 Thread Otto Moerbeek
On Wed, Jan 20, 2021 at 07:04:08AM +0100, Christian Jullien wrote: > Hi, > > I'm running OpenBSD 6.8 on arm : > > $ sysctl | grep hw > hw.machine=armv7 > hw.model=ARM Cortex-A8 r3p2 > hw.ncpu=1 > hw.byteorder=1234 > hw.pagesize=4096 > hw.disknames= > hw.diskcount=2 > hw.cpuspeed=0 > hw.product=T

Re: munmap sometimes does coredump on arm after mmap success

2021-01-20 Thread Otto Moerbeek
m: Theo de Raadt [mailto:dera...@openbsd.org] > Sent: Wednesday, January 20, 2021 09:29 > To: jull...@eligis.com > Cc: 'Otto Moerbeek'; bugs@openbsd.org > Subject: Re: munmap sometimes does coredump on arm after mmap success > > Christian Jullien wrote: > > > My

Re: munmap sometimes does coredump on arm after mmap success

2021-01-20 Thread Otto Moerbeek
On Wed, Jan 20, 2021 at 04:54:26PM +0100, Christian Jullien wrote: > Hum! I'm not convinced as don't do anything with returned memory block > between mmap and munmap. > The offending code is similar to munmap(mmap(...)) => coredump! Sigh. You *are* doing something with the returned memory: unmapp

Re: munmap sometimes does coredump on arm after mmap success

2021-01-20 Thread Otto Moerbeek
t; Christian > > -Original Message- > From: Theo de Raadt [mailto:dera...@openbsd.org] > Sent: Wednesday, January 20, 2021 18:01 > To: jull...@eligis.com > Cc: 'Otto Moerbeek'; bugs@openbsd.org > Subject: Re: munmap sometimes does coredump on arm after mmap success

Re: LLVM error

2021-02-19 Thread Otto Moerbeek
On Fri, Feb 19, 2021 at 08:09:02PM -0500, david rosier wrote: This is not a bug. Likely you did not run sysmerge when upgrading, recently the memory limits were upped. vsweb.openbsd.org/cgi-bin/cvsweb/src/etc/etc.arm64/login.conf.diff?r1=1.7&r2=1.8&f=h -Otto > LLVM ERROR: out of memory

Re: unwind: resolver: SIGSEGV

2019-12-02 Thread Otto Moerbeek
On Sun, Dec 01, 2019 at 11:57:08PM +0100, Klemens Nanni wrote: > On Sun, Dec 01, 2019 at 11:41:51PM +0100, Klemens Nanni wrote: > > It crashed again: > > > > Dec 1 23:36:50 eru unwind[88042]: startup > > Dec 1 23:38:18 eru unwind[44830]: frontend exiting > > Dec 1 23:38:18 eru unwi

Re: ntpd(8) adds time since epoch to system clock

2019-12-02 Thread Otto Moerbeek
On Sun, Dec 01, 2019 at 02:27:42PM -0800, Chris Bennett wrote: > I am also getting the same effect using neomutt for a good while now. > Clock is correct. Timezone is correct. > mutt does not do this. > neomutt does not do this on any other boxes running same snapshots. > > This has continued thr

Re: unwind reports no signature or no DNSSEC

2020-02-05 Thread Otto Moerbeek
On Wed, Feb 05, 2020 at 04:14:41PM +0100, Florian Obser wrote: > On Tue, Feb 04, 2020 at 11:41:14AM +, Raf Czlonka wrote: > > On Mon, Feb 03, 2020 at 07:29:02PM GMT, Florian Obser wrote: > > > On Mon, Feb 03, 2020 at 07:58:24PM +0100, Solene Rapenne wrote: > > > > On Mon, Feb 03, 2020 at 07:52

Re: Incorrect RCSID value in /distrib/notes/octeon/xfer file

2020-02-17 Thread Otto Moerbeek
On Mon, Feb 17, 2020 at 09:41:35AM +0200, Andrius V wrote: > Hello, > > Noticed typo in RCSID value in /distrib/notes/octeon/xfer file. > > Patch: > > localhost$ git diff --unified > diff --git a/distrib/notes/octeon/xfer b/distrib/notes/octeon/xfer > index 548e7f9a404..e088383a1f2 100644 > ---

Re: Errors in X - Build Date Mar 14 2020 01:48:26 UTC

2020-03-14 Thread Otto Moerbeek
On Sat, Mar 14, 2020 at 03:24:16PM +, Tom Murphy wrote: > On Sat, Mar 14, 2020 at 03:53:58PM +0100, Theo Buehler wrote: > > On Sat, Mar 14, 2020 at 02:01:23PM +, Tom Murphy wrote: > > > Hi, > > > > > > I've narrowed it down. > > > Further testing shows it's not kernel, but Xenocara. I

Re: Errors in X - Build Date Mar 14 2020 01:48:26 UTC

2020-03-15 Thread Otto Moerbeek
On Sun, Mar 15, 2020 at 10:09:53AM -0400, Okan Demirmen wrote: > On Sat 2020.03.14 at 18:33 +0100, Tim van der Molen wrote: > > Stefan Sperling (2020-03-14 18:12 +0100): > > > On Sat, Mar 14, 2020 at 05:36:46PM +0100, Otto Moerbeek wrote: > > > > Looking a the d

Re: Errors in X - Build Date Mar 14 2020 01:48:26 UTC

2020-03-15 Thread Otto Moerbeek
On Sun, Mar 15, 2020 at 11:14:06AM -0400, Okan Demirmen wrote: > On Sun 2020.03.15 at 15:45 +0100, Otto Moerbeek wrote: > > On Sun, Mar 15, 2020 at 10:09:53AM -0400, Okan Demirmen wrote: > > > > > On Sat 2020.03.14 at 18:33 +0100, Tim van der Molen wrote: > > >

Re: heads up: amd64 snap

2020-03-15 Thread Otto Moerbeek
> wskbd1: connecting to wsdisplay0 > wskbd2: connecting to wsdisplay0 > wsdisplay0: screen 1-5 added (std, vt100 emulation) > wskbd1: disconnecting from wsdisplay0 > wskbd1 detached > ukbd0 detached > uhidev0 detached > ugold0 detached > uhidev1 detached > uhidev0 at uhu

Re: heads up: amd64 snap

2020-03-16 Thread Otto Moerbeek
low. Apologies > for the noise. OK, good. You syptoms match having an old installboot installing a new bisboot. Installboot is run from the ramdisk. Your issue could happen if you use and old bsd.rd to upgrade a machine. -Otto > > On Mon, Mar 16, 2020 at 07:38:04AM +0

Re: panic: ffs_update: bad link cnt

2020-04-24 Thread Otto Moerbeek
On Fri, Apr 24, 2020 at 10:06:19PM +0200, Klemens Nanni wrote: > > kern.version=OpenBSD 6.6-current (GENERIC.MP) #237: Fri Mar 6 16:53:42 MST > 2020 > dera...@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC.MP > > My primary domain paniced when I tried to remove the softdep f

Re: panic: ffs_update: bad link cnt

2020-04-25 Thread Otto Moerbeek
On Sat, Apr 25, 2020 at 08:31:14AM +0200, Otto Moerbeek wrote: > On Fri, Apr 24, 2020 at 10:06:19PM +0200, Klemens Nanni wrote: > > > > > kern.version=OpenBSD 6.6-current (GENERIC.MP) #237: Fri Mar 6 16:53:42 MST > > 2020 > > dera...@sparc64.openbsd.org:/us

Re: Mounting MFS filesystem does not preserve directory permissions of mount point

2020-05-19 Thread Otto Moerbeek
On Tue, May 19, 2020 at 05:49:23AM -0600, Todd C. Miller wrote: > Is there any advantage to mfs defaulting to ffs2? > > - todd > In 18 years, yes. But the -O2 case should work whartever the default is for mfs. -Otto

Re: Mounting MFS filesystem does not preserve directory permissions of mount point

2020-05-19 Thread Otto Moerbeek
On Tue, May 19, 2020 at 06:06:36AM -0600, Theo de Raadt wrote: > Otto Moerbeek wrote: > > > On Tue, May 19, 2020 at 05:49:23AM -0600, Todd C. Miller wrote: > > > > > Is there any advantage to mfs defaulting to ffs2? > > > > > > - todd > > &g

Re: Mounting MFS filesystem does not preserve directory permissions of mount point

2020-05-19 Thread Otto Moerbeek
On Tue, May 19, 2020 at 06:15:15AM -0600, Todd C. Miller wrote: > On Tue, 19 May 2020 14:04:37 +0200, Otto Moerbeek wrote: > > > In 18 years, yes. But the -O2 case should work whartever the default > > is for mfs. > > I agree that -O2 should work for mfs, I'm just

Re: Mounting MFS filesystem does not preserve directory permissions of mount point

2020-05-19 Thread Otto Moerbeek
On Tue, May 19, 2020 at 01:28:24PM +0100, Stuart Henderson wrote: > On 2020/05/19 06:15, Todd C. Miller wrote: > > On Tue, 19 May 2020 14:04:37 +0200, Otto Moerbeek wrote: > > > > > In 18 years, yes. But the -O2 case should work whartever the default > > > is f

Re: grep does not end

2020-06-06 Thread Otto Moerbeek
On Sat, Jun 06, 2020 at 04:11:59PM +0200, BESSOT Jean-Michel wrote: > Hello > > I have a problem with grep in the last current. grep was working instantly > and now it does not end nor give an output. This is a pretty useless report. Show at least the command line you are using. -Otto

Re: grep does not end

2020-06-06 Thread Otto Moerbeek
On Sat, Jun 06, 2020 at 07:57:35PM +0200, BESSOT Jean-Michel wrote: > yes, "reboot" That is not a file argument, that is a pattern argument. -Otto > > On 2020-06-06 17:51, Otto Moerbeek wrote: > > On Sat, Jun 06, 2020 at 05:44:24PM +0200, BESSOT Jean-Michel wr

Re: grep does not end

2020-06-07 Thread Otto Moerbeek
On Sun, Jun 07, 2020 at 06:40:41AM +0200, Sebastien Marie wrote: > On Sat, Jun 06, 2020 at 07:57:35PM +0200, BESSOT Jean-Michel wrote: > > yes, "reboot" > > > > On 2020-06-06 17:51, Otto Moerbeek wrote: > > > On Sat, Jun 06, 2020 at 05:44:24PM +0200, BE

Re: grep does not end

2020-06-07 Thread Otto Moerbeek
On Sun, Jun 07, 2020 at 02:36:31PM +0200, Otto Moerbeek wrote: > On Sun, Jun 07, 2020 at 06:40:41AM +0200, Sebastien Marie wrote: > > > On Sat, Jun 06, 2020 at 07:57:35PM +0200, BESSOT Jean-Michel wrote: > > > yes, "reboot" > > > > > > On 2020

page fault trap in connector_bad_edid with new drm code

2020-06-08 Thread Otto Moerbeek
Hi. a page fault trap happens if I boot my Thnkpad X1 6th generation in the dock or put it in the dock afterwards. The dock has two DP monitors connected. If I change connector_bad_edid() to return immediately things seems to work ok. -Otto summary of trace: connector_bad_edid+0x4d drm

Re: page fault trap in connector_bad_edid with new drm code

2020-06-08 Thread Otto Moerbeek
On Mon, Jun 08, 2020 at 09:46:23PM +0200, Mark Kettenis wrote: > > Date: Mon, 8 Jun 2020 20:27:22 +0200 > > From: Otto Moerbeek > > > > Hi. > > > > a page fault trap happens if I boot my Thnkpad X1 6th generation in the dock > > or put it in the doc

Re: page fault trap in connector_bad_edid with new drm code

2020-06-08 Thread Otto Moerbeek
On Tue, Jun 09, 2020 at 08:01:12AM +0200, Otto Moerbeek wrote: > On Mon, Jun 08, 2020 at 09:46:23PM +0200, Mark Kettenis wrote: > > > > Date: Mon, 8 Jun 2020 20:27:22 +0200 > > > From: Otto Moerbeek > > > > > > Hi. > > > > > > a pa

Re: page fault trap in connector_bad_edid with new drm code

2020-06-09 Thread Otto Moerbeek
On Tue, Jun 09, 2020 at 04:59:17PM +1000, Jonathan Gray wrote: > On Tue, Jun 09, 2020 at 08:12:17AM +0200, Otto Moerbeek wrote: > > On Tue, Jun 09, 2020 at 08:01:12AM +0200, Otto Moerbeek wrote: > > > > > On Mon, Jun 08, 2020 at 09:46:23PM +0200, Mark Kettenis wrote: &g

Re: page fault trap in connector_bad_edid with new drm code

2020-06-09 Thread Otto Moerbeek
On Tue, Jun 09, 2020 at 04:05:25PM +0200, Otto Moerbeek wrote: > On Tue, Jun 09, 2020 at 04:59:17PM +1000, Jonathan Gray wrote: > > > On Tue, Jun 09, 2020 at 08:12:17AM +0200, Otto Moerbeek wrote: > > > On Tue, Jun 09, 2020 at 08:01:12AM +0200, Otto Moerbeek wrote: > >

Re: page fault trap in connector_bad_edid with new drm code

2020-06-09 Thread Otto Moerbeek
On Tue, Jun 09, 2020 at 04:19:34PM +0200, Mark Kettenis wrote: > > Date: Tue, 9 Jun 2020 16:08:26 +0200 > > From: Otto Moerbeek > > > > On Tue, Jun 09, 2020 at 04:05:25PM +0200, Otto Moerbeek wrote: > > > > > On Tue, Jun 09, 2020 at 04:59:17PM +1000, Jon

Re: page fault trap in connector_bad_edid with new drm code

2020-06-10 Thread Otto Moerbeek
On Tue, Jun 09, 2020 at 08:28:57PM +0200, Mark Kettenis wrote: > > Date: Tue, 9 Jun 2020 20:08:42 +0200 > > From: Otto Moerbeek > > > > On Tue, Jun 09, 2020 at 04:19:34PM +0200, Mark Kettenis wrote: > > > > > > Date: Tue, 9 Jun 2020

Re: page fault trap in connector_bad_edid with new drm code

2020-06-10 Thread Otto Moerbeek
On Wed, Jun 10, 2020 at 12:52:31PM +0200, Mark Kettenis wrote: > ok, so this is using the implementation in display/intel_gmbus.c which > is a complicated one since it has code to fall back to "bit banging" > when the i2c master controller doesn't seem to work. You could dig > deeper into that an

Re: man double free

2020-06-11 Thread Otto Moerbeek
On Thu, Jun 11, 2020 at 03:15:55PM +0200, Romero Pérez, Abel wrote: > I've got a: man(13835) in free(): bogus pointer (double free?) 0x22c43c2813b > > To check please, add the following function to .kshrc and run . ./.kshrc: > > > function man { >     set -A array "$@" >     tag=${array[$#-1]}

Re: man double free

2020-06-11 Thread Otto Moerbeek
On Thu, Jun 11, 2020 at 04:53:25PM +0200, Romero Pérez, Abel wrote: > > > On 2020-06-11 16:45, Klemens Nanni wrote: > > On Thu, Jun 11, 2020 at 03:59:09PM +0200, Otto Moerbeek wrote: > > > This already trips the bug; > > > > > > man -T html -c pfct

Re: man double free

2020-06-11 Thread Otto Moerbeek
On Thu, Jun 11, 2020 at 05:15:28PM +0200, Romero Pérez, Abel wrote: > > > On 2020-06-11 17:07, Otto Moerbeek wrote: > > On Thu, Jun 11, 2020 at 04:53:25PM +0200, Romero Pérez, Abel wrote: > > > > > > > > > > > On 2020-06-11 16:45, Klemens Na

Re: NSD sendto issue

2020-06-18 Thread Otto Moerbeek
On Wed, Jun 17, 2020 at 04:57:54PM +0200, Joerg Jung wrote: > > > On 17. Feb 2020, at 15:16, Martin Pieuchot wrote: > > On 17/02/20(Mon) 14:55, Joerg Jung wrote: > >> > >>> On 26. Sep 2019, at 15:02, Stuart Henderson wrote: > >>> On 2019/09/26 13:45, Stuart Henderson wrote: > On 2019/09/2

Re: NSD sendto issue

2020-06-18 Thread Otto Moerbeek
On Thu, Jun 18, 2020 at 11:45:01AM +0200, Joerg Jung wrote: > > > On 18. Jun 2020, at 09:47, Otto Moerbeek wrote: > > On Wed, Jun 17, 2020 at 04:57:54PM +0200, Joerg Jung wrote: > >>> On 17. Feb 2020, at 15:16, Martin Pieuchot wrote: > >>> O

Re: NSD sendto issue

2020-06-21 Thread Otto Moerbeek
...@nlnetlabs.nl> > >>> <mailto:wou...@nlnetlabs.nl <mailto:wou...@nlnetlabs.nl>>> wrote: > >>> On 18/06/2020 11:49, Otto Moerbeek wrote: > >>>> On Thu, Jun 18, 2020 at 11:45:01AM +0200, Joerg Jung wrote: > >>>>>> On 18.

Re: Allow DDB to be disabled at boot time?

2016-09-03 Thread Otto Moerbeek
On Fri, Sep 02, 2016 at 02:14:20PM -0400, Adam McDougall wrote: > Would it be possible to add a method to the boot loader to disable > DDB support in the kernel, or perhaps even disable it by default? > I've encountered two different brands of servers (Dell and HP) > where the remote graphical con

Re: boggle(6) boardspec is broken (with patch)

2016-09-12 Thread Otto Moerbeek
On Sun, Sep 11, 2016 at 11:49:40PM -0700, randy hartman wrote: > >Synopsis:boggle(6) boardspec is broken > >Category:user > >Environment: > System : OpenBSD 6.0 > Details : OpenBSD 6.0-current (GENERIC.MP) #0: Wed Sep 7 18:51:12 > PDT 2016 > >

Re: accept4 w/ SOCK_NONBLOCK, blocks in 6.0...

2016-12-27 Thread Otto Moerbeek
On Wed, Dec 28, 2016 at 03:10:13AM +, Luke Small wrote: > Thanks for the help. I'm not trying to kill the process. I stated that the > process didn't die to show that it didn't reach the "got here2" because it > was blocking. > > On Tue, Dec 27, 2016 at 6:40 PM Jeremie Courreges-Anglas > wro

Re: accept4 w/ SOCK_NONBLOCK, blocks in 6.0...

2016-12-29 Thread Otto Moerbeek
Luke Small schreef op 28 december 2016 09:03:43 CET: >You have to make the socket call nonblocking > >On Wed, Dec 28, 2016, 01:11 Otto Moerbeek wrote: > >> On Wed, Dec 28, 2016 at 03:10:13AM +, Luke Small wrote: >> >> > Thanks for the help. I'm not tryi

Re: install57.iso does not recognize a burned image of itself in an attached CD-R drive

2015-05-19 Thread Otto Moerbeek
On Tue, May 19, 2015 at 03:15:25AM -0500, James Hartley wrote: > > Are you sure? > > Yes. The USB CD-R drive is plugged in once with the disc inserted. No > change is made between the booting of bsd.rd & bsd.mp. > > > What do you think this means then? > > It appears that when the boot device

Re: patch(1) wrongly applies non-applicable diff

2015-07-07 Thread Otto Moerbeek
On Wed, Jul 08, 2015 at 01:31:25AM +0200, Stefan Fritsch wrote: > Hi, > > patch's handling of diffs that change the beginning of a file is broken. > The moste severe breakage is this, where the diff says to remove a line > "aa" but patch removes a line "XX": Yeah, known issue. Checking of cont

Re: sparc64/ binary packages (pkg_add) linked on wrong libraries

2015-11-13 Thread Otto Moerbeek
On Thu, Nov 12, 2015 at 05:40:45PM -0500, michel.bell...@malaiwah.com wrote: > >Synopsis:pkg_add doesn't work on 5.8/sparc64, argues about > >missing libs > >Category:system library sparc64 > >Environment: > System : OpenBSD 5.8 > Details : OpenBSD 5.8-current (GENER

Re: posix_memalign can set *ptr = MAP_FAILED

2017-09-12 Thread Otto Moerbeek
On Tue, Sep 12, 2017 at 02:19:37PM -0400, George Koehler wrote: > >Synopsis:posix_memalign can set *ptr = MAP_FAILED > >Category:library > >Environment: > System : OpenBSD 6.1 > Details : OpenBSD 6.1 (GENERIC.MP) #19: Thu Aug 3 14:59:44 CEST > 2017 >

Re: file timestamps wrap around

2017-11-12 Thread Otto Moerbeek
On Sun, Nov 12, 2017 at 06:29:38PM +0100, Bruno Haible wrote: > >Synopsis:file timestamps wrap around > >Category: > >Environment: > System : OpenBSD 6.0 > Details : OpenBSD 6.0 (GENERIC) #1917: Tue Jul 26 12:48:33 MDT 2016 > > dera...@i386.open

Re: file timestamps wrap around

2017-11-12 Thread Otto Moerbeek
On Sun, Nov 12, 2017 at 08:12:26PM +0100, Mark Kettenis wrote: > > Date: Sun, 12 Nov 2017 19:54:24 +0100 > > From: Otto Moerbeek > > > > On Sun, Nov 12, 2017 at 06:29:38PM +0100, Bruno Haible wrote: > > > > > >Synopsis:f

  1   2   3   4   >