From owner-freebsd-bugs@freebsd.org Thu Dec 29 10:59:56 2016 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 2D535C964C6 for ; Thu, 29 Dec 2016 10:59:56 +0000 (UTC) (envelope-from fidaj@ukr.net) Received: from frv157.fwdcdn.com (frv157.fwdcdn.com [212.42.77.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DF6F51CFF for ; Thu, 29 Dec 2016 10:59:55 +0000 (UTC) (envelope-from fidaj@ukr.net) 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=GFowPxzo6LezgRFfqW/6UX2uJpH7lNpUWLkUPaeflSM=; b=fSH0AzT/mcMwiBsy+Ewnfxz4Po c0rxI1393fWa6EwiqNHBHgEXdjz4vvXDiQCekcLiuTDMv83gcU+3BkK6tV+KhbAYrCRbyju437k9X ztAcLpjAqc5rVGTKsLOO4bYcGLVwyXVOh7UtYqLzNUow/xo+CO65MPXFmjEWq4VkzGB8=; Received: from [46.185.1.216] (helo=nonamehost) by frv157.fwdcdn.com with esmtpsa ID 1cMYQz-000NBO-69 ; Thu, 29 Dec 2016 12:59:45 +0200 Date: Thu, 29 Dec 2016 12:59:43 +0200 From: Ivan Klymenko To: hiren panchasara Cc: freebsd-bugs@freebsd.org Subject: Re: panics collections on FreeBSD 11.0-RC1 RC2 PRERELEASE RELEASE STABLE Message-ID: <20161229125943.46ab685c@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> 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.185.1.216; mail.from=fidaj@ukr.net; dkim=pass; header.d=ukr.net 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: Thu, 29 Dec 2016 10:59:56 -0000 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 Unfortunately I do not have much information, because the system has ceased to do a dump when the panic occurred. And it happened a long time. When the current settings before the dump was created. I addition, wrote that: Panic often occur when one of the owncloud clients trying to synchronize files with the owncloud server, which has been in jail on the same server, it is running on a virtual machine in VirtualBox . The problem can be reproduced with the use of network activity in a virtual machine - and in jail.