From owner-freebsd-amd64@freebsd.org  Fri Mar  9 11:50:20 2018
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C278F464CB
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Fri,  9 Mar 2018 11:50:20 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::19:3])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mxrelay.ysv.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id F135D72C02
 for <freebsd-amd64@FreeBSD.org>; Fri,  9 Mar 2018 11:50:19 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 2A4BF6A2B
 for <freebsd-amd64@FreeBSD.org>; Fri,  9 Mar 2018 11:50:19 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w29BoJBD057839
 for <freebsd-amd64@FreeBSD.org>; Fri, 9 Mar 2018 11:50:19 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
 by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w29BoJVY057836
 for freebsd-amd64@FreeBSD.org; Fri, 9 Mar 2018 11:50:19 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: www set sender to
 bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 209421] Processes hangs in D state, suspfs or vofflock wchan
 under FreeBSD 10.X
Date: Fri, 09 Mar 2018 11:50:18 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: work+freebsd@vvv.kiev.ua
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-209421-6-qPxjQLaxvs@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209421-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-209421-6@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-amd64@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2018 11:50:20 -0000

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

--- Comment #9 from vvv <work+freebsd@vvv.kiev.ua> ---
It isn't a problem of controller, because the behavior is randomly observed=
 at
different servers with different hardware.

Yes, SU+J is enabled. Is it a known problem?

Disabling SU+J is undesirable because fsck will take a very long time on
unclean file systems. But I'll try.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=