From owner-cvs-all@FreeBSD.ORG Fri Aug 20 22:19:42 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20EDA16A4CE; Fri, 20 Aug 2004 22:19:42 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1CAD43D39; Fri, 20 Aug 2004 22:19:41 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-127-84-57.dsl.snfc21.pacbell.net [67.127.84.57]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i7KMJe8U016058; Fri, 20 Aug 2004 15:19:41 -0700 Message-ID: <412678FC.6040009@root.org> Date: Fri, 20 Aug 2004 15:19:40 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7 (X11/20040702) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Wemm References: <200408201921.i7KJLl3J035751@repoman.freebsd.org> <200408201516.32748.peter@wemm.org> In-Reply-To: <200408201516.32748.peter@wemm.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern vfs_subr.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Aug 2004 22:19:42 -0000 Peter Wemm wrote: > On Friday 20 August 2004 12:21 pm, Don Lewis wrote: > >> Modified files: >> sys/kern vfs_subr.c >> Log: >> Don't attempt to trigger the syncer thread final sync code in the >> shutdown_pre_sync state if the RB_NOSYNC flag is set. This is the >> likely cause of hangs after a system panic that are keeping crash >> dumps from being done. > > > The hang that I saw was because interrupts are broken (they just stop > for no apparent reason) and the ata_shutdown sync hooks are not in > polled mode (which is correct - interrupts are supposed to be enabled > at this point, and are for normal shutdowns). Did you got the "interrupt storm for xxx" message before this happened? I think the check for this is too sensitive -- it is triggered on resume by my an0 card. That's the only way I've seen interrupts stop occuring during normal operation. -Nate