From owner-freebsd-stable@FreeBSD.ORG Sun Oct 24 17:58:45 2004 Return-Path: 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 8025016A4CE; Sun, 24 Oct 2004 17:58:45 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FDA343D45; Sun, 24 Oct 2004 17:58:45 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id i9OHwLcN089094; Sun, 24 Oct 2004 13:58:21 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i9OHwLQP089091; Sun, 24 Oct 2004 18:58:21 +0100 (BST) (envelope-from robert@fledge.watson.org) Date: Sun, 24 Oct 2004 18:58:21 +0100 (BST) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd-hubs@freebsd.org In-Reply-To: <20041024150130.GN6156@droso.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org Subject: Re: ftp.freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Oct 2004 17:58:45 -0000 On Sun, 24 Oct 2004, Erwin Lansing wrote: > > The Danish part of ftp.freebsd.org (ftp.beastie.tdk.net) does not seem > > to respond, I have poked one of the admins, but since it's late night > > here in Denmark, it will probably be some hours before anyone can look > > at the problem. > > > beatie paniced at about 3 am CEST and was rebooted. > > I don't know what caused the panic, but I see quite a lot of: > Oct 23 04:51:29 ftp /kernel: swap_pager: indefinite wait buffer: device: > #da/0x2 0001, blkno: 544, size: 4096 > Oct 23 04:52:07 ftp /kernel: swap_pager: indefinite wait buffer: device: > #da/0x2 0001, blkno: 544, size: 4096 The swap pager will wait hz*20 (20 seconds) for pages to be read back in from the swap space -- if it doesn't hear back in that time, it generates the above warning and then continue waiting. Typically, that kind of wait might occur because of a hardware problem. Did you see any related console output from the controller/device driver? Typically having swap space disappear out from under the system is not good for the health of the system... Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research