From owner-freebsd-bugs@freebsd.org  Sun Dec 18 02:58:47 2016
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 504CBC842CC
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sun, 18 Dec 2016 02:58:47 +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 407D61B38
 for <freebsd-bugs@FreeBSD.org>; Sun, 18 Dec 2016 02:58:47 +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 uBI2wkjL026109
 for <freebsd-bugs@FreeBSD.org>; Sun, 18 Dec 2016 02:58:47 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 214923] kqueue hangs with busy loop
Date: Sun, 18 Dec 2016 02:58:46 +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 Only Me
X-Bugzilla-Who: yjh0502@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-214923-8-HvIWrEdR9l@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-214923-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-214923-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: Sun, 18 Dec 2016 02:58:47 -0000

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

--- Comment #16 from yjh0502@gmail.com ---
(In reply to Konstantin Belousov from comment #15)

Do 'panic data' means ddb messages on panic? A Message on panic is:

panic: Bad link elm 0xfffff8003be59b00 next->prev !=3D elm

I reproduces the problem with same commands (start watchman and repeatedly
clone/delete git repos), but this time I got slightly different traces. The
message above got from new trace, and there's ddb output corresponding to t=
he
panic message.

https://gist.github.com/anonymous/bae4d503e20c5ab00ff1e513c523c9f5

Please let me know if i'm misunderstanding something.

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