Re: suspend / resume on skylake doesn't work (on -current)

* Mark Kettenis [2017-07-06 15:31:34 +0200]: Date: Thu, 6 Jul 2017 00:01:41 -0700 From: Pratik Vyas >Synopsis: suspend / resume on skylake machine doesn't work >Category: system (inteldrm) >Environment: System : OpenBSD 6.1

Re: canaries can cause malloc with a size of 0 to hang

The end of the problem is that in malloc_bytes(), malloc.c line 981, the code enters the double for loop with a bp having the inconvenient property that in bp->bits, all sixteen entries are 0, causing the inner for loop to spin indefinitely. I must admit, though, that i have no idea what that

canaries can cause malloc with a size of 0 to hang

>Synopsis: when canaries are enabled `malloc(0)' sometimes hangs >Category: system >Environment: System : OpenBSD 6.1 Details : OpenBSD 6.1-current (GENERIC.MP) #88: Wed Jul 5 23:16:11 MDT 2017

Re: panic: Stopped at kqueue_scan

On Thu, Jul 06, 2017 at 08:29:39AM -0600, Aaron Bieber wrote: > Hola, > > For roughly a week I have been able to reliably produce panics on > amd64 (virtual machine and physical machine) using disk IO heavy > applications (gitea, syncthing). > > Unfortunately on the physical machine - the one I

Re: flow queue problem on -current : not able to send packets anymore

Remove "default" from the rule. On 6 July 2017 18:43:47 Sebastien Marie wrote: Hi, With last snapshot (Jul 5), I experimented problems with networking: I couldn't send packets. As example: # ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes ping: sendmsg: No buffer

Re: panic: Stopped at kqueue_scan

On Thu, Jul 06, 2017 at 01:25:38PM -0400, Ted Unangst wrote: > Aaron Bieber wrote: > > For roughly a week I have been able to reliably produce panics on > > amd64 (virtual machine and physical machine) using disk IO heavy > > applications (gitea, syncthing). > > these are also network

flow queue problem on -current : not able to send packets anymore

Hi, With last snapshot (Jul 5), I experimented problems with networking: I couldn't send packets. As example: # ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes ping: sendmsg: No buffer space available ping: wrote 8.8.8.8 64 chars, ret=-1 ^C My previous (working) snap was Jun 26. I tracked

Re: panic: Stopped at kqueue_scan

Aaron Bieber wrote: > For roughly a week I have been able to reliably produce panics on > amd64 (virtual machine and physical machine) using disk IO heavy > applications (gitea, syncthing). these are also network applications, no? i think that's the io that causes trouble.

panic: Stopped at kqueue_scan

Hola, For roughly a week I have been able to reliably produce panics on amd64 (virtual machine and physical machine) using disk IO heavy applications (gitea, syncthing). Unfortunately on the physical machine - the one I can reliably panic within < 1 minute - I don't have a serial console, so

Re: suspend / resume on skylake doesn't work (on -current)

> Date: Thu, 6 Jul 2017 00:01:41 -0700 > From: Pratik Vyas > > >Synopsis:suspend / resume on skylake machine doesn't work > >Category:system (inteldrm) > >Environment: > System : OpenBSD 6.1 > Details : OpenBSD 6.1-current (GENERIC.MP) #87: Wed Jul 5

Re: dhcrelay problem (Re: relayctl problem)

On 05/07/17 17:47, Reyk Floeter wrote: > On Wed, Jul 05, 2017 at 03:23:34PM +0300, Kapetanakis Giannis wrote: >> Yes this patch seems to solve my problem. >> >> My test client which previously didn't get an IP, got one immediately. >> >> I'd like to point out however that some clients on some

inteldrm(4) regression and multi screen at boot

Hi, I have a problem in screen initialisation with latest update of inteldrm(4) (amd64). I have the problem since snap Jun 27 and it is still present on snap of Jul 5. On my laptop (dmesg below), I use an external monitor on VGA1 port (and xrandr to make VGA1 left-of LVDS1). 1. When booting