From owner-freebsd-fs@FreeBSD.ORG  Sun May 17 18:03:35 2015
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5357C1FA
 for <freebsd-fs@FreeBSD.org>; Sun, 17 May 2015 18:03:35 +0000 (UTC)
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 3D01F1C1F
 for <freebsd-fs@FreeBSD.org>; Sun, 17 May 2015 18:03:35 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t4HI3ZIF078669
 for <freebsd-fs@FreeBSD.org>; Sun, 17 May 2015 18:03:35 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 197789] (zfs+i386 No PAE) panic: kmem_malloc(36864): kmem_map
 too small: 431976448 total allocated
Date: Sun, 17 May 2015 18:03:35 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 9.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: michelle@sorbs.net
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-197789-3630-yGE4zlnfFy@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-197789-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-197789-3630@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-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 17 May 2015 18:03:35 -0000

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

--- Comment #4 from Michelle Sullivan <michelle@sorbs.net> ---
Ok got it down to something a little more clearer...

No changing of vm.kmem_size_max has any effect except delaying the issue...
just as vm.kmem_size doesn't.

What does stop the panic (so far I've build 800+ packages using poudriere -
with 'svn update' prior - which before the update didn't even complete and
after going through several boots it manages around 20 packages before panicing
- if it even gets past the checking sanity phase)....

Reduce the CPU count to one cpu ....

Interestingly setting max ARC size to 40M and within minutes of multiple CPUs
it's over 400M ... before it panics...  With one CPU it grows to 80(ish)M and
doesn't panic...

some 40 or 50 cores publicly available at the link i post earlier...

both 9.2 and 9.3 are affected... lets hope someone will see to patch it before
9.4..  I wouldn't have a clue where to look for the issue or I'd take a shot at
it myself.

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