From owner-freebsd-questions@FreeBSD.ORG Mon May 9 17:20:19 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA9E316A4E9 for ; Mon, 9 May 2005 17:20:19 +0000 (GMT) Received: from fedde.littleton.co.us (fedde.littleton.co.us [216.17.139.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 302F343D81 for ; Mon, 9 May 2005 17:20:19 +0000 (GMT) (envelope-from cfedde@fedde.littleton.co.us) Received: from fedde.littleton.co.us (localhost [127.0.0.1]) j49HKHAM097093 for ; Mon, 9 May 2005 11:20:17 -0600 (MDT) Message-Id: <200505091720.j49HKHAM097093@fedde.littleton.co.us> To: freebsd-questions@freebsd.org From: Chris Fedde Date: Mon, 09 May 2005 11:20:17 -0600 Sender: cfedde@fedde.littleton.co.us X-Spam-Status: No, score=-4.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on fedde.littleton.co.us Subject: swap space problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2005 17:20:19 -0000 Occasionaly my system hangs for a few seconds while loading a process from swap that has been idle for some time. It could be that I'm actualy out of swap space in these conditions, because I see this frequently in dmesg output: swap_pager_getswapspace(8): failed. But I also see other failures that indicate that there may be a hardware issue going on: swap_pager: I/O error - pageout failed; blkno 20114,size 45056, error 0 ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=161663 ad0: FAILURE - WRITE_DMA timed out Boot message for the device controller is: atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 And the disk is ad0: 14648MB [29762/16/63] at ata0-master UDMA66 Is there some issue relating to the configuration that I can repair? Or am I seeing a real hardware problem? -- Chris Fedde