From owner-freebsd-bugs@freebsd.org Fri Jun 23 10:58:16 2017 Return-Path: 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 5C84BDA1F98 for ; Fri, 23 Jun 2017 10:58:16 +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 4B295812D1 for ; Fri, 23 Jun 2017 10:58:16 +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 v5NAwGI5049036 for ; Fri, 23 Jun 2017 10:58:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220217] deadlock on enc and pf Date: Fri, 23 Jun 2017 10:58:16 +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: vegeta@tuxpowered.net 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: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 10:58:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220217 --- Comment #2 from vegeta@tuxpowered.net --- Under normal circumstances the kernel does not panic, it just goes 100% usa= ge on bird or on interrupt. The packet which causes it is bird connecting to B= GP router on the other side, at least on the dump I obtained from this particu= lar crash. I have the screenshot of crash with debug-enabled kernel but the stack trac= e is so long, that the original message is not visible anymore. Does kernel debu= gger console support scrolling? Pressing scroll-lock did not have any effect. The line 411 where the error happens is: 372 __rw_rlock(volatile uintptr_t *c, const char *file, int line) ... 411 KASSERT(rw_wowner(rw) !=3D curthread, 412 ("rw_rlock: wlock already held for %s @ %s:%d",=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 413 rw->lock_object.lo_name, file, line)); Can I obtain information about the other process holding the lock? (struct thread)*inp->inp_lock->rw_lock points to the same process "swi4: clock (0)"= . I know the live debugger has some helpers to show locks, but I would need to = kill the machine again for that and set up serial console. I would prefer to use existing memory dump if possible. --=20 You are receiving this mail because: You are the assignee for the bug.=