From owner-cvs-all@FreeBSD.ORG Wed Aug 25 16:41:13 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 155BE16A4CE; Wed, 25 Aug 2004 16:41:13 +0000 (GMT) Received: from mx1.originative.co.uk (freebsd.gotadsl.co.uk [81.6.249.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D8F643D39; Wed, 25 Aug 2004 16:41:10 +0000 (GMT) (envelope-from paul@mx1.originative.co.uk) Received: from localhost (unknown [127.0.0.1]) by mx1.originative.co.uk (Postfix) with ESMTP id EAFBE1556F; Wed, 25 Aug 2004 17:41:08 +0100 (BST) Received: from mx1.originative.co.uk ([127.0.0.1])port 10024) with ESMTP id 32659-05; Wed, 25 Aug 2004 17:41:06 +0100 (BST) Received: by mx1.originative.co.uk (Postfix, from userid 1000) id C28D715579; Wed, 25 Aug 2004 17:41:06 +0100 (BST) Date: Wed, 25 Aug 2004 17:41:06 +0100 From: Paul Richards To: Nate Lawson Message-ID: <20040825164106.GB5709@myrddin.originative.co.uk> References: <200408201921.i7KJLl3J035751@repoman.freebsd.org> <200408201516.32748.peter@wemm.org> <412678FC.6040009@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <412678FC.6040009@root.org> User-Agent: Mutt/1.5.6i cc: cvs-src@freebsd.org cc: src-committers@freebsd.org cc: cvs-all@freebsd.org cc: Peter Wemm 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: Wed, 25 Aug 2004 16:41:13 -0000 On Fri, Aug 20, 2004 at 03:19:40PM -0700, Nate Lawson wrote: > 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. It's been happening on one of my boxes too. I can't boot it at all with ACPI, I don't get any routing, without ACPI it runs for a while then all of a sudden box starts getting ATA DMA timeouts because interrupts stop working. I was going to send some dmesg from the two boot scenarios but it doesn't boot up at all anymore, just hangs I think just after the timecounter/cpu throttle steps messages, I think that's the point where it's probing for ATA devices - which might still be interrupt issues. It's not very useable considering it's -stable :-) Paul.