From owner-freebsd-stable@FreeBSD.ORG Tue Dec 19 14:09:53 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DD72816A415 for ; Tue, 19 Dec 2006 14:09:53 +0000 (UTC) (envelope-from ken@astro.ufl.edu) Received: from milton.astro.ufl.edu (milton.astro.ufl.edu [128.227.184.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F5C043CA3 for ; Tue, 19 Dec 2006 14:09:53 +0000 (GMT) (envelope-from ken@astro.ufl.edu) Received: from localhost (localhost.astro.ufl.edu [127.0.0.1]) by milton.astro.ufl.edu (Postfix) with ESMTP id F09D939BDD for ; Tue, 19 Dec 2006 09:09:39 -0500 (EST) Received: from milton.astro.ufl.edu ([127.0.0.1]) by localhost (mailhost.astro.ufl.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81301-05 for ; Tue, 19 Dec 2006 09:09:37 -0500 (EST) Received: from fugu.astro.ufl.edu (fugu.astro.ufl.edu [128.227.184.12]) by milton.astro.ufl.edu (Postfix) with ESMTP id 8BF5F39BDC for ; Tue, 19 Dec 2006 09:09:37 -0500 (EST) Date: Tue, 19 Dec 2006 09:09:37 -0500 (EST) From: Ken Sallot To: freebsd-stable@FreeBSD.ORG In-Reply-To: <200612191351.kBJDpMpB058787@lurza.secnetix.de> Message-ID: References: <200612191351.kBJDpMpB058787@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by UF Astronomy Mail Virus Scanner ks/14/4/2005 Cc: Subject: Re: "swap_pager" loop? 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: Tue, 19 Dec 2006 14:09:53 -0000 On Tue, 19 Dec 2006, Oliver Fromme wrote: > Ken Sallot wrote: > > Yesterday morning I came in to find a 6.2-RC1 server deadlocked in a loop > > with the following error messages on the console: > > > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 5, size: 4096 > > That message is printed when a timeout appears while waiting > for the swap device. I've seen such problems when the disk > or the controller was dead or malfunctioning. Are you sure > that your hardware is OK, i.e. no disk errors, good cables > etc.? Reasonably sure, but I could always double check the cabling. The chassis & drives are new (6 weeks old), and I've not seen any other errors in the hardware. Ken