Date: Fri, 27 Jan 2017 00:33:10 +0200 From: Ivan Klymenko <fidaj@ukr.net> To: hiren panchasara <hiren@strugglingcoder.info> Cc: freebsd-bugs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: [SOLVED] panics collections on FreeBSD 11.0-RC1 RC2 PRERELEASE RELEASE STABLE Message-ID: <20170127003310.15c5a828@nonamehost> In-Reply-To: <20161228175729.GC17818@strugglingcoder.info> References: <20161021220413.1d130f5c@nonamehost> <20161228095808.64d617de@nonamehost> <20161228174142.GB17818@strugglingcoder.info> <20161228195333.120e844f@nonamehost> <20161228175729.GC17818@strugglingcoder.info>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 28 Dec 2016 09:57:29 -0800 hiren panchasara <hiren@strugglingcoder.info> wrote: > On 12/28/16 at 07:53P, Ivan Klymenko wrote: > > On Wed, 28 Dec 2016 09:41:42 -0800 > > hiren panchasara <hiren@strugglingcoder.info> wrote: > > > > > Can you open a bug report at https://bugs.freebsd.org/bugzilla/ > > > with necessary details? Looks like virtualbox is involved here? > > > > I can not, because that does not make sense. > > PR are not considered for months and years. > > It was the last hope for the mail lists. > > Probably i must to change the operating system. > > Apologies for that. As you know people get busy in such opensource > projects. > > The panic appears in tcp land so if you provide enough information, > I'll try to look at it. Again, I cannot promise anything more than an > honest attempt. > > Cheers, > Hiren The reason most panics served as tuning Netisr: net.isr.numthreads=4 net.isr.maxthreads=4 net.isr.bindthreads=1 Apparently, this subsystem at some moment had been broken. Best regards,
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170127003310.15c5a828>