From owner-freebsd-bugs@freebsd.org  Sat Aug 12 18:00:31 2017
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 561D5DB7EDB
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sat, 12 Aug 2017 18:00: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 4486D6AFE5
 for <freebsd-bugs@FreeBSD.org>; Sat, 12 Aug 2017 18:00:31 +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 v7CI0Thj015005
 for <freebsd-bugs@FreeBSD.org>; Sat, 12 Aug 2017 18:00:31 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 220971] Freebsd 11.0p11 - system freeze on intensive I/O
Date: Sat, 12 Aug 2017 18:00:29 +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: 11.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: execve@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-220971-8-8IddGZVPVx@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-220971-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-220971-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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.23
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: Sat, 12 Aug 2017 18:00:31 -0000

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

--- Comment #7 from execve@gmail.com ---
I do not think there is any need to increase the memory usage. Like I menti=
oned
in the original PR description, even without X running on the same system w=
ith
8GB RAM, I could reproduce this using a split command on a 6-7GB file via t=
he
console.=20

>> running split on a 6.4G file (filesystem dump of disk using dump) -- som=
ething like=20
>> split -d -b 200M -a 4 - part=20
>> This would then freeze at one point - making the system unusable. I trie=
d this 2-3 times.=20

It is very clear there is an issue - and from my experience it is narrowed =
to
when the ULE scheduler and swapfile is in use.

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