From owner-freebsd-bugs@freebsd.org  Thu Sep 17 15:29:27 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
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 455959CE985
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu, 17 Sep 2015 15:29:27 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 1987C15E3
 for <freebsd-bugs@FreeBSD.org>; Thu, 17 Sep 2015 15:29:27 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8HFTQkX016407
 for <freebsd-bugs@FreeBSD.org>; Thu, 17 Sep 2015 15:29:26 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 203175] Daily kernel crashes on 10.2-p2 using VIMAGE
Date: Thu, 17 Sep 2015 15:29:27 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: girgen@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
 attachments.created
Message-ID: <bug-203175-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Sep 2015 15:29:27 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203175

            Bug ID: 203175
           Summary: Daily kernel crashes on 10.2-p2 using VIMAGE
           Product: Base System
           Version: 10.2-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: girgen@FreeBSD.org

Created attachment 161149
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=161149&action=edit
core.txt from /var/crash

Hi,

We have four jail host machines that all experience this problem. We first
suspected hardware, but since all four crash regularly, it should be  as
software (kernel?) problem.

The jail hosts are running 10.2-p2 using GENERIC+VIMAGE using netgraph bridging
and they encounter frequent kernel crashes. See attached core.txt - there is
also a core dump available if someone want to debug it.

The hosts contains around 20 jails half of them running apache2 serving a
couple of thousands of users. ZFS on root. The web servers run a java web app
(behind apache using mod_jk) process consuming a few GB of ram which frequently
executes posix_spawn(3).

We also experienced the problem when running on 10.1-p15.

The crashes do not appear on 10.1-p4 which we have temporarily reverted to.

Could the SCTP kernel memory corruption fix in 10.1-p5 be relevant? Or perhaps
the 10.1-p15 TCP resource exhaustion one?

-- 
You are receiving this mail because:
You are the assignee for the bug.