Date: Fri, 21 Aug 2020 17:23:11 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 248811] panic: deadlres_td_sleep_q: possible deadlock detected Message-ID: <bug-248811-227-WVwroCfBWk@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-248811-227@https.bugs.freebsd.org/bugzilla/> References: <bug-248811-227@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=3D248811 --- Comment #4 from Conrad Meyer <cem@freebsd.org> --- Looking at core.txt.8: These prints are not the problem, but it would be nice to fix the drm driver not to do lock asserts during panic: WARNING !drm_modeset_is_locked(&plane->mutex) failed at /usr/local/sys/modules/drm-current-kmod/drivers/gpu/drm/drm_atomic_helper.c= :821 #0 0xffffffff82ebb673 at linux_dump_stack+0x23 It's a shame deadlkres doesn't do something like print_lockchain(). That'd help diagnose these things. ps shows the only find process is blocked on nfs: 0 61433 61429 0 52 0 18540 5752 nfs D - 0:13.33 [fi= nd] There are several nfscl threads sleeping on nfscl, which indicates renewthr= ead, i.e., probably we're waiting on a server that went away. I'd guess that's = what find is also waiting on. --=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-248811-227-WVwroCfBWk>