From owner-freebsd-bugs@FreeBSD.ORG Thu Nov 15 11:20:02 2007 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 376AC16A41B for ; Thu, 15 Nov 2007 11:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 292C613C458 for ; Thu, 15 Nov 2007 11:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id lAFBK2nN013418 for ; Thu, 15 Nov 2007 11:20:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id lAFBK2vE013417; Thu, 15 Nov 2007 11:20:02 GMT (envelope-from gnats) Date: Thu, 15 Nov 2007 11:20:02 GMT Message-Id: <200711151120.lAFBK2vE013417@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Punkey Funky Cc: Subject: Re: kern/103455: "swap_pager: indefinite wait buffer" with page file enabled (causes lockups) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Punkey Funky List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2007 11:20:02 -0000 The following reply was made to PR kern/103455; it has been noted by GNATS. From: Punkey Funky To: bug-followup@FreeBSD.org, nick@nickwithers.com Cc: Subject: Re: kern/103455: "swap_pager: indefinite wait buffer" with page file enabled (causes lockups) Date: Thu, 15 Nov 2007 10:36:29 +0000 "Me too"... Running 7.0-CURRENT, although I've seen this issue since 6.x. I note that many online resources claim that this error arises with either disks about to fail and/or bad cables/controller. In order to rule this out, I purchased brand new hardware: atapci2: port 0xdb00-0xdb07,0xdc00-0xdc03,0xdd00-0xdd07,0xde00-0xde03,0xdf00-0xdfff irq 17 at device 11.0 on pci0 atapci3: port 0xe000-0xe007,0xe100-0xe103,0xe200-0xe207,0xe300-0xe303,0xe400-0xe4ff irq 17 at device 11.1 on pci0 [..] ad8: 238475MB at ata4-master UDMA133 ad10: 238475MB at ata5-master UDMA133 ad12: 238475MB at ata6-master UDMA133 [..] ar0: 476950MB status: READY ar0: disk0 READY using ad8 at ata4-master ar0: disk1 READY using ad10 at ata5-master ... and despite the new hardware, the issue still occurs. I have checked the drives with smartmontools and see no issues reported. This leads me to believe that it's not (in this case) related to failing hardware. This particular machine is a home system that performs filesharing, firewall, DNS and mail server duties. It's by no means heavily loaded. When the issue does occur, the server is unresponsive on the console, and no other access (ssh, www, etc) is possible. The server does respond to a ping. -L