From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 07:30:21 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 12E1B16A4CE for ; Wed, 10 Mar 2004 07:30:21 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id D55C943D53 for ; Wed, 10 Mar 2004 07:30:19 -0800 (PST) (envelope-from mw@theatre.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id QAA07312 for freebsd-current@freebsd.org; Wed, 10 Mar 2004 16:30:18 +0100 (CET) Received: from theatre.sax.de (mw@localhost [127.0.0.1]) by theatre.sax.de (8.12.10/8.12.10) with ESMTP id i2AFNdSa012137 for ; Wed, 10 Mar 2004 16:23:39 +0100 (CET) (envelope-from mw@theatre.sax.de) Received: (from mw@localhost) by theatre.sax.de (8.12.10/8.12.9/Submit) id i2AFNdRw012136 for freebsd-current@freebsd.org; Wed, 10 Mar 2004 16:23:39 +0100 (CET) (envelope-from mw) Date: Wed, 10 Mar 2004 16:23:39 +0100 From: Martin Welk To: freebsd-current@freebsd.org Message-ID: <20040310152339.GA2722@theatre.sax.de> References: <20040310103020.Y69923@fw.reifenberger.com> <39679.1078911516@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <39679.1078911516@critter.freebsd.dk> User-Agent: Mutt/1.5.6i Subject: Re: got "swap_pager: indefinite wait buffe" under -current 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: Wed, 10 Mar 2004 15:30:21 -0000 On Wed, Mar 10, 2004 at 10:38:36AM +0100, Poul-Henning Kamp wrote: > That a disk-I/O request did not complete. > > Likely cause is disk hardware or media error. > > Check for console messages from ata driver. The same here since upgrading to 5.2.1-RELEASE(-p1) when there's heavy disk activity, but without any ata driver messages at all. In some cases, the situation recovers, in others, only reboot (pressing reset button) helps. Details in my mail on -current from last Saturday, no reply yet *sigh* Regards, Martin -- ,,Oh, there's a lot of opportunities, if you're knowing to take them, you know, there's a lot of opportunities, if there aren't you can make them, make or break them!'' (Tennant/Lowe)