From owner-freebsd-bugs@freebsd.org Wed Feb 15 07:53:18 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92D4DCDFF6C; Wed, 15 Feb 2017 07:53:18 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from frv71.fwdcdn.com (frv71.fwdcdn.com [212.42.77.71]) by mx1.freebsd.org (Postfix) with ESMTP id 46DA7AE8; Wed, 15 Feb 2017 07:53:17 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from [10.10.17.73] (helo=frv158.fwdcdn.com) by frv71.fwdcdn.com QID:1cdu8Y-000Dc5-WB/RC:2; Wed, 15 Feb 2017 09:36:27 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=fsm; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=6fP8EhkC51TDHAsRTImUQYcJni27ALYuzyTNvwcyXn8=; b=BSDRYbp7QtteA3aU38J+cDk7lg IA24yMlvJZbXYlPi9k7rDTfe21G4oUjSF27EIiVeADzDVwJ+T/rkWKrW+ipZQJ6kqTClX0XijqIQR /SmtgeNtwQ5+bWJJKdel1sITXu5y8QIYMEI37zjpuxkb6CgoRsf1fCUpZczPiHBVJXUU=; Received: from [46.119.57.93] (helo=nonamehost) by frv158.fwdcdn.com with esmtpsa ID 1cdu8I-000PNX-Q6 ; Wed, 15 Feb 2017 09:36:10 +0200 Date: Wed, 15 Feb 2017 09:36:09 +0200 From: Ivan Klymenko To: hiren panchasara Cc: freebsd-bugs@freebsd.org, freebsd-stable@freebsd.org, "Andrey V. Elsukov" Subject: Re: [SOLVED] [#2] panics collections on FreeBSD 11.0-RC1 RC2 PRERELEASE RELEASE STABLE Message-ID: <20170215093609.78a77ead@nonamehost> In-Reply-To: <20170127003310.15c5a828@nonamehost> References: <20161021220413.1d130f5c@nonamehost> <20161228095808.64d617de@nonamehost> <20161228174142.GB17818@strugglingcoder.info> <20161228195333.120e844f@nonamehost> <20161228175729.GC17818@strugglingcoder.info> <20170127003310.15c5a828@nonamehost> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWpqak/Pz/i4uIfHx8GBwZwcHAQEBA6o92AAAACHElEQVQ4jWWUTY7bMAyF6QzUPSEoa8PFHEBgqwuM4bVVg7MvZOj+R+ijpMTpjIwgkT7z75EKrdfattpXERG6zqvUOtAr2LCRYfEKcB4l/Q+2cc6XjQH7hv+2YZYreIk5nevZEPvuzUzptizHLzgDMnC5Wpbl7ewJlOEqlQF+DlCjgVLki0WV6FMDMsBxjlJiQulIznwZ+DxHiQyDyIg0wN3Oo6o6ZQ5s5AIfar+W2Wlmz+kCcb8tg6j3voMEwNrBQk69dDBDqw/urpqJH+m+Q6u/4QnoAeYpnUXC/s1iup9rhCd6xMgAqdDyAyFegbKkVAHeLCcOulPLawaoUIDos4M88iLNrVkU7uu5ccTDO6naJzWLum51C6Yb7y4HKKbdArLWir0PBiS8glJRBZHeyHl7J9lENpAC6qT9NlNG4u5hsVYDyJP6mlJJtY3oVju4WSUzHal1sDU17NASoBWSk40J2eBLBJhYrVmzC5gVALGpNIAiQgN6eGstOp9Oa6zFbbLTISYi28BGZDRUJKWeroECkCEkzXjUtbmmaKMfAx2RfbT69/cO+tgHcmx6AfyZOmj3NDIah0F0GB66d4CrdIoplNFFGHSpSheRxbo0W4S8azNItEoMWbw3uXAeJgCrmX5joz7CGXqSg6PcryEhnFr/C1C2ntPxBOYbdwY+8dO3+wZJyFlbMX9s8zNnvp/tLwAv03NB4j3HVpn8Awwm+GrlP6MVAAAAAElFTkSuQmCC MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Authentication-Result: IP=46.119.57.93; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net X-Ukrnet-Yellow: 0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2017 07:53:18 -0000 On Fri, 27 Jan 2017 00:33:10 +0200 Ivan Klymenko wrote: > On Wed, 28 Dec 2016 09:57:29 -0800 > hiren panchasara wrote: > > > On 12/28/16 at 07:53P, Ivan Klymenko wrote: > > > On Wed, 28 Dec 2016 09:41:42 -0800 > > > hiren panchasara 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, The next problem of panic was associated with https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 Feb 3 10:22:37 ns kernel: panic: sbsndptr: sockbuf 0xfffff802077c5bd8 and mbuf 0xfffff80019f26d00 clashing Feb 3 10:22:37 ns kernel: cpuid = 4 Feb 3 10:22:37 ns kernel: KDB: stack backtrace: Feb 3 10:22:37 ns kernel: #0 0xffffffff80b3ebb7 at kdb_backtrace+0x67 Feb 3 10:22:37 ns kernel: #1 0xffffffff80af39b6 at vpanic+0x186 Feb 3 10:22:37 ns kernel: #2 0xffffffff80af3823 at panic+0x43 Feb 3 10:22:37 ns kernel: #3 0xffffffff80b8e3da at sbsndptr+0xda Feb 3 10:22:37 ns kernel: #4 0xffffffff80d34119 at tcp_output+0x1129 Feb 3 10:22:37 ns kernel: #5 0xffffffff80d301ee at tcp_do_segment+0x288e Feb 3 10:22:37 ns kernel: #6 0xffffffff80d2d1f2 at tcp_input+0x14d2 Feb 3 10:22:37 ns kernel: #7 0xffffffff80c94372 at ip_input+0x192 Feb 3 10:22:37 ns kernel: #8 0xffffffff80c2a4fd at netisr_dispatch_src+0xad Feb 3 10:22:37 ns kernel: #9 0xffffffff80c124f9 at ether_demux+0x149 Feb 3 10:22:37 ns kernel: #10 0xffffffff82b6971c at vboxNetFltFreeBSDinput+0x27c Feb 3 10:22:37 ns kernel: #11 0xffffffff80b5204a at taskqueue_run_locked+0x14a Feb 3 10:22:37 ns kernel: #12 0xffffffff80b51e3f at taskqueue_run+0xbf Feb 3 10:22:37 ns kernel: #13 0xffffffff80aad33f at intr_event_execute_handlers+0x20f Feb 3 10:22:37 ns kernel: #14 0xffffffff80aad5a6 at ithread_loop+0xc6 Feb 3 10:22:37 ns kernel: #15 0xffffffff80aa9de5 at fork_exit+0x85 Feb 3 10:22:37 ns kernel: #16 0xffffffff8101022e at fork_trampoline+0xe Feb 3 10:22:37 ns kernel: Uptime: 21h36m52s Feb 3 10:22:37 ns kernel: Dumping 7804 out of 32688 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% I have added an option hw.igb.num_queues=1 to /boot/loader.conf and the server is running without panic over a few weeks is stable. Panic my servers have multiple causes. Best regards,