From owner-freebsd-bugs@freebsd.org  Wed Jul  8 09:19:31 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 6BD259959C0
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed,  8 Jul 2015 09:19:31 +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 5818C1CEC
 for <freebsd-bugs@FreeBSD.org>; Wed,  8 Jul 2015 09:19:31 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t689JVbf008029
 for <freebsd-bugs@FreeBSD.org>; Wed, 8 Jul 2015 09:19:31 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 194654] 10.1-RC3 hangs with simultanious writes
Date: Wed, 08 Jul 2015 09:19:31 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: misc
X-Bugzilla-Version: 10.1-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: FreeBSD@ShaneWare.Biz
X-Bugzilla-Status: Closed
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: resolution bug_status
Message-ID: <bug-194654-8-CmUfal7GWO@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-194654-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-194654-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: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jul 2015 09:19:31 -0000

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

FreeBSD@ShaneWare.Biz changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |Unable to Reproduce
             Status|Open                        |Closed

--- Comment #10 from FreeBSD@ShaneWare.Biz ---
I am currently running 10.2-PRERELEASE #13 r285123

Testing in single user mode I still see wired allocation jump from 1500M to
7300M within a few seconds, but there is still a few hundred MB left free.

While I think there could be improvement on the sudden wired allocation I don't
see it locking up in this situation.

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