From owner-freebsd-current Sun Feb 25 5: 1: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D6FB637B503 for ; Sun, 25 Feb 2001 05:01:03 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id OAA60007; Sun, 25 Feb 2001 14:00:54 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Matt Dillon Cc: Kirk McKusick , current@FreeBSD.ORG Subject: Giving up on buffers References: <200102231206.EAA12234@beastie.mckusick.com> <200102231756.f1NHuAX83112@earth.backplane.com> From: Dag-Erling Smorgrav Date: 25 Feb 2001 14:00:53 +0100 In-Reply-To: Matt Dillon's message of "Fri, 23 Feb 2001 09:56:10 -0800 (PST)" Message-ID: Lines: 13 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon writes: > (2) the I/O for the buffer synchronization is initiated but interrupts > are winding up being disabled by the halt code due to holding Giant > and not sleeping (more likely). That all I can think of. We've hit > the interrupt disablement problem before in -current, it's probably > something simliar. Sounds likely. On my laptop, the "giving up on n buffers" message is usually accompanied by an ata0 timeout. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message