From owner-freebsd-current@FreeBSD.ORG Tue Aug 17 04:43:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 917DC16A4CE for ; Tue, 17 Aug 2004 04:43:29 +0000 (GMT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10BBD43D2D for ; Tue, 17 Aug 2004 04:43:29 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i7H4hMYV005062 for ; Mon, 16 Aug 2004 21:43:26 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200408170443.i7H4hMYV005062@gw.catspoiler.org> Date: Mon, 16 Aug 2004 21:43:21 -0700 (PDT) From: Don Lewis To: current@FreeBSD.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Subject: thoughts on system hangs after panic() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Aug 2004 04:43:29 -0000 I suspect the cause of the system hangs after a panic that are keeping crash dumps from working is one of the shutdown_pre_sync handlers getting wedged. The most likely culprit is syncer_shutdown(), but I think any of the handlers could get wedged in kthread_suspend(). Either we should skip shutdown_pre_sync entirely if RB_NOSYNC is set, or the handlers should obey this bit as appropriate. The latter would require a little more code to be touched, but would allow for more flexibility.