Date: Fri, 23 Jun 2017 10:58:16 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220217] deadlock on enc and pf Message-ID: <bug-220217-8-fPjFSDcn2r@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220217-8@https.bugs.freebsd.org/bugzilla/> References: <bug-220217-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220217-8-fPjFSDcn2r>