Date: Wed, 11 Mar 2015 16:21:10 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 195458] Hang on shutdown/root unmount after FreeBSD 10.1R upgrade Message-ID: <bug-195458-8-VTSzMF3H4i@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-195458-8@https.bugs.freebsd.org/bugzilla/> References: <bug-195458-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=195458 --- Comment #55 from Glen Barber <gjb@FreeBSD.org> --- (In reply to Konstantin Belousov from comment #53) > (In reply to Glen Barber from comment #52) > It is physically impossible to hang on a line which is not loop. > Yes, understood. > I suspect that it is either the buffer flush code, or softdep worker thread > which loop and cause shutdown thread to wait. It is good that you have > reproducable case and willing to move it further, previous reporters only > bother to whine. > > See > https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ > kerneldebug-deadlocks.html for the instructions on how to configure your > kernel and what information to get. The test machine now has INVARIANTS, INVARIANT_SUPPORT, WITNESS, DEBUG_LOCKS, DEBUG_VFS_LOCKS, DIAGNOSTIC, and ALT_BREAK_TO_DEBUGGER. Unfortunately, it panics on boot now, so I cannot proceed to the 'freebsd-update install; reboot' phase. Just prior to this, I left out DIAGNOSTIC and saw a lock order reversal after the "All buffers synced." message. (I will provide screenshots in a separate update.) It looks like I will need to remove DIAGNOSTIC to get the system to boot. -- 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-195458-8-VTSzMF3H4i>