From owner-freebsd-questions@FreeBSD.ORG Fri May 23 21:08:54 2008 Return-Path: Delivered-To: questions@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id EE5351065678; Fri, 23 May 2008 21:08:54 +0000 (UTC) Date: Fri, 23 May 2008 21:08:54 +0000 From: Kris Kennaway To: paul beard Message-ID: <20080523210854.GB20868@hub.freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: questions@freebsd.org Subject: Re: kernel debugging: seeing swap issues in 7.0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2008 21:08:55 -0000 On Fri, May 23, 2008 at 01:02:35PM -0700, paul beard wrote: > I see a lot of these as my system grinds to a halt. It never crashes > (I reboot it when it gets really boggy . . . > > > May 23 11:41:13 stinky kernel: swap_pager: indefinite wait buffer: > bufobj: 0, blkno: 49155, size: 4096 > May 23 11:41:21 stinky kernel: swap_pager: indefinite wait buffer: > bufobj: 0, blkno: 48905, size: 4096 > > This is the top of the kernel debug > > Unread portion of the kernel message buffer: > <118>May 23 12:48:46 stinky syslogd: exiting on signal 15 > Waiting (max 60 seconds) for system process `vnlru' to stop...done > Waiting (max 60 seconds) for system process `bufdaemon' to stop...done > Waiting (max 60 seconds) for system process `syncer' to stop... > Syncing disks, vnodes remaining...1 0 0 done > All buffers synced. > swap_pager: I/O error - pagein failed; blkno 35668,size 4096, error 5 > panic: swap_pager_force_pagein: read from swap failed > Uptime: 14h20m56s > Physical memory: 115 MB > Dumping 37 MB: 22 6 > #0 doadump () at pcpu.h:195 > 195 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); > > I have partition-based swap and swap files I set up after gcc was > running out of memory. > > Device: 1048576-blocks Used: > /dev/ad0s2b 139 0 > /dev/md0 128 0 > > Any ideas what I can do (besides buy more hardware)? You can try increasing the timeout by editing the relevant kernel source, but if it's failing to reply to the I/O after 30 seconds then something is drastically overloaded on your system. Kris