FreeBSD 11.0-RC3 failed on hyper-v 2012r2

2016-09-16 Thread Alexander Shitov
I've found that FreeBSD 11.0-RC3 failed to install on hyperv 2012r2 on disk partitioning step Abort- |Partitioning error | || |An installation step has been aborted. Would| |you like to res

Re: nginx and FreeBSD11

2016-09-16 Thread Konstantin Belousov
On Thu, Sep 15, 2016 at 11:54:12AM -0700, John Baldwin wrote: > On Thursday, September 15, 2016 08:49:48 PM Slawa Olhovchenkov wrote: > > On Thu, Sep 15, 2016 at 10:28:11AM -0700, John Baldwin wrote: > > > > > On Thursday, September 15, 2016 05:41:03 PM Slawa Olhovchenkov wrote: > > > > On Wed, Se

Re: nginx and FreeBSD11

2016-09-16 Thread Slawa Olhovchenkov
On Fri, Sep 16, 2016 at 12:16:17PM +0300, Konstantin Belousov wrote: > > vmspace_switch_aio() allows context switching with old curpmap > and new proc->p_vmspace. This is a weird condition, where > curproc->p_vmspace->vm_pmap is not equal to curcpu->pc_curpmap. I do > not see an obvious place whi

Re: FreeBSD 11.0-RC3 failed on hyper-v 2012r2

2016-09-16 Thread Alexander Shitov
Installation fails with fixed sized and dynamically sized disks. Issue is important because it affects possibility to upgrade existing FreeBSD 10.3 production VMs to FreeBSD 11.0 On Fri, Sep 16, 2016 at 10:43 AM, Alexander Shitov wrote: > I've found that FreeBSD 11.0-RC3 failed to install on hy

Re: nginx and FreeBSD11

2016-09-16 Thread Slawa Olhovchenkov
On Fri, Sep 16, 2016 at 01:17:14PM +0300, Slawa Olhovchenkov wrote: > On Fri, Sep 16, 2016 at 12:16:17PM +0300, Konstantin Belousov wrote: > > > > > vmspace_switch_aio() allows context switching with old curpmap > > and new proc->p_vmspace. This is a weird condition, where > > curproc->p_vmspace

Re: 11.0 stuck on high network load

2016-09-16 Thread Slawa Olhovchenkov
On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: > On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: > > > On Thu, Sep 15, 2016 at 12:35:04AM +0300, Slawa Olhovchenkov wrote: > > > On Sun, Sep 04, 2016 at 06:46:12PM -0700, hiren panchasara wrote: > > > > > >

Re: 11.0 stuck on high network load

2016-09-16 Thread Eugene Grosbein
17.09.2016 1:18, Slawa Olhovchenkov пишет: ~^B don't break to debuger. Make sure your kernel config has: # Solaris implements a new BREAK which is initiated by a character # sequence CR ~ ^b which is similar to a familiar pattern used on # Sun servers by the Remote Console. There are FreeBSD

Bug 209491 (Broadcast storm with ipfw+natd+gateway) from -CURRENT is now in 11-STABLE

2016-09-16 Thread Cejka Rudolf
Hello, I have reported bug 209491 (Broadcast storm with ipfw+natd+gateway) for -CURRENT, but now it is also in 11-STABLE. It is still here, as I have tested it today with src r305790 (11.0-PRERELEASE). So please be warned. If you are using similar configuration as me with ipfw+natd+gateway, you

Re: 11.0 stuck on high network load

2016-09-16 Thread hiren panchasara
On 09/16/16 at 09:18P, Slawa Olhovchenkov wrote: > On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: > > > On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: > > > > > On Thu, Sep 15, 2016 at 12:35:04AM +0300, Slawa Olhovchenkov wrote: > > > > On Sun, Sep 04, 2

Re: 11.0 stuck on high network load

2016-09-16 Thread Slawa Olhovchenkov
On Fri, Sep 16, 2016 at 11:30:53AM -0700, hiren panchasara wrote: > On 09/16/16 at 09:18P, Slawa Olhovchenkov wrote: > > On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: > > > > > On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: > > > > > > > On Thu, Sep 15

Re: 11.0 stuck on high network load

2016-09-16 Thread Slawa Olhovchenkov
On Fri, Sep 16, 2016 at 11:30:53AM -0700, hiren panchasara wrote: > On 09/16/16 at 09:18P, Slawa Olhovchenkov wrote: > > On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: > > > > > On Thu, Sep 15, 2016 at 11:59:38AM +0300, Konstantin Belousov wrote: > > > > > > > On Thu, Sep 15

Re: 11.0 stuck on high network load

2016-09-16 Thread hiren panchasara
+ jch@ On 09/16/16 at 10:03P, Slawa Olhovchenkov wrote: > On Fri, Sep 16, 2016 at 11:30:53AM -0700, hiren panchasara wrote: > > > On 09/16/16 at 09:18P, Slawa Olhovchenkov wrote: > > > On Thu, Sep 15, 2016 at 12:06:33PM +0300, Slawa Olhovchenkov wrote: > > > > > > > On Thu, Sep 15, 2016 at 11:59

FreeBSD 11.0-RC2 to 11.0-RC3 fetching metadata signature failed

2016-09-16 Thread Lacey Powers
Hello Everyone, Whenever I try to run freebsd-update to go from 11.0-RC2 to 11.0-RC3, I get the following error: # freebsd-update upgrade -r 11.0-RC3 Looking up update.FreeBSD.org mirrors... 4 mirrors found. Fetching metadata signature for 11.0-RC2 from update5.freebsd.org... done. Fetching meta

Re: FreeBSD 11.0-RC2 to 11.0-RC3 fetching metadata signature failed

2016-09-16 Thread Glen Barber
On Fri, Sep 16, 2016 at 12:35:40PM -0700, Lacey Powers wrote: > Hello Everyone, > > Whenever I try to run freebsd-update to go from 11.0-RC2 to 11.0-RC3, I > get the following error: > > # freebsd-update upgrade -r 11.0-RC3 > > Looking up update.FreeBSD.org mirrors... 4 mirrors found. > Fetching

Re: 11.0 stuck on high network load

2016-09-16 Thread Slawa Olhovchenkov
On Fri, Sep 16, 2016 at 12:11:55PM -0700, hiren panchasara wrote: > > As I suspected, this looks like a hang trying to lock V_tcbinfo. > > I'm ccing Julien here who worked on WLOCK -> RLOCK transition to improve > performance for short-lived connections. I am not too sure if thats the > problem

Re: 11.0 stuck on high network load

2016-09-16 Thread hiren panchasara
On 09/16/16 at 11:30P, Slawa Olhovchenkov wrote: > On Fri, Sep 16, 2016 at 12:11:55PM -0700, hiren panchasara wrote: > > > > > As I suspected, this looks like a hang trying to lock V_tcbinfo. > > > > I'm ccing Julien here who worked on WLOCK -> RLOCK transition to improve > > performance for sho

Re: 11.0 stuck on high network load

2016-09-16 Thread hiren panchasara
On 09/16/16 at 02:46P, hiren panchasara wrote: > On 09/16/16 at 11:30P, Slawa Olhovchenkov wrote: > > On Fri, Sep 16, 2016 at 12:11:55PM -0700, hiren panchasara wrote: > > > > > > > > As I suspected, this looks like a hang trying to lock V_tcbinfo. > > > > > > I'm ccing Julien here who worked on