From owner-freebsd-stable@FreeBSD.ORG Fri Dec 16 19:39:50 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6FDF16A41F; Fri, 16 Dec 2005 19:39:50 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34A5943D69; Fri, 16 Dec 2005 19:39:46 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 53DAD1A3C27; Fri, 16 Dec 2005 11:39:43 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9C42151257; Fri, 16 Dec 2005 14:39:42 -0500 (EST) Date: Fri, 16 Dec 2005 14:39:42 -0500 From: Kris Kennaway To: delphij@delphij.net Message-ID: <20051216193942.GA92029@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable , sos@FreeBSD.org Subject: Re: indefinite wait buffer: Does this indicate hardware issue? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 19:39:51 -0000 --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 17, 2005 at 12:49:48AM +0800, Xin LI wrote: > Dear folks, >=20 > I have a box indicating the following sometimes: > "swap_pager: indefinite wait buffer: bufobj: 0, blkno: 262169, size: 4096" >=20 > It's running FreeBSD 6.0-RELEASE, with two Maxtor 7Y250P0 hard disks > attached to Intel ICH5 UDMA100 controller with hw.ata.wc disabled. >=20 > Does this indicate a hardware issue, or some bugs elsewhere? In that configuration, probably a hardware issue. Is it always the same block? This message triggers as a false positive in other cases when swapping is too slow, like if you swap to a swapfile on a heavily loaded filesystem. Kris --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDoxf+Wry0BWjoQKURAjQwAKCRcvdVJh75OZ/SJcf9Ap0wo8qMfgCfQR86 TqTSggIjTa5JKLGT45CGEi4= =2nfS -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA--