From owner-freebsd-bugs Thu Feb 11 10:11:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22827 for freebsd-bugs-outgoing; Thu, 11 Feb 1999 10:11:05 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22822 for ; Thu, 11 Feb 1999 10:11:03 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.9.2/8.9.2) id MAA17125; Thu, 11 Feb 1999 12:10:41 -0600 (CST) From: Kevin Day Message-Id: <199902111810.MAA17125@home.dragondata.com> Subject: Re: kern/10029: many vm_fault: pager read errors In-Reply-To: <199902111650.IAA83910@freefall.freebsd.org> from David Greenman at "Feb 11, 1999 8:50: 1 am" To: dg@root.com Date: Thu, 11 Feb 1999 12:10:40 -0600 (CST) Cc: freebsd-bugs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The following reply was made to PR kern/10029; it has been noted by GNATS. > > From: David Greenman > To: david@inty.net > Cc: freebsd-gnats-submit@FreeBSD.ORG > Subject: Re: kern/10029: many vm_fault: pager read errors > Date: Thu, 11 Feb 1999 08:45:35 -0800 > > >>Description: > >Quite often when a program I have written exits on a signal (usually INT), > >the kernel generates an endless stream of 'vm_fault: pager read error, pid ....' > >on the console. Doing a kill -9 on the process in question stops the error > >messages. This is definitely _not_ a hardware problem and occurs both with > >2.2.5-8 and 3.0 kernels. > > Are you running the binaries over NFS? > > -DG I'm running 2.2.8 NFS clients and see this quite a bit. It also seems to be a 'spiral of death' problem if you don't stop it somewhat quickly. The longer this is going on, the more processes start joining in. I will usually see one process segfault, then a different one start complaining in vm_fault. Feb 4 17:17:13 /kernel: pid 20141 (eggdrop), uid 1072: exited on signal 11 Feb 4 17:17:15 /kernel: vm_fault: pager input (probably hardware) error, PID 16937 failure Feb 4 17:19:55 last message repeated 20 times Feb 4 17:19:56 last message repeated 71475 times Feb 4 17:19:59 last message repeated 526470 times Feb 4 17:20:55 last message repeated 496355 times Feb 4 17:21:29 /kernel: pid 28826 (eggdrop), uid 1169: exited on signal 11 Feb 4 17:21:40 /kernel: vm_fault: pager input (probably hardware) error, PID 22993 failure Feb 4 17:21:40 /kernel: vm_fault: pager input (probably hardware) error, PID 17975 failure Feb 4 17:21:40 /kernel: vm_fault: pager input (probably hardware) error, PID 1988 failure Feb 4 17:21:41 /kernel: vm_fault: pager input (probably hardware) error, PID 546 failure Feb 4 17:21:41 /kernel: vm_fault: pager input (probably hardware) error, PID 1990 failure Feb 4 17:21:41 /kernel: vm_fault: pager input (probably hardware) error, PID 8000 failure Feb 4 17:21:41 /kernel: vm_fault: pager input (probably hardware) error, PID 1428 failure Feb 4 17:21:41 /kernel: vm_fault: pager input (probably hardware) error, PID 17975 failure Feb 4 17:21:41 /kernel: vm_fault: pager input (probably hardware) error, PID 1988 failure Feb 4 17:21:41 /kernel: vm_fault: pager input (probably hardware) error, PID 546 failure Feb 4 17:21:41 /kernel: vm_fault: pager input (probably hardware) error, PID 1990 failure Feb 4 17:21:41 /kernel: vm_fault: pager input (probably hardware) error, PID 8000 failure Feb 4 17:21:41 /kernel: vm_fault: pager input (probably hardware) error, PID 17975 failure Feb 4 17:21:41 /kernel: vm_fault: pager input (probably hardware) error, PID 1988 failure Feb 4 17:21:41 /kernel: vm_fault: pager input (probably hardware) error, PID 546 failure Feb 4 17:21:42 /kernel: vm_fault: pager in Feb 4 17:21:42 /kernel: ID 1429 failure Feb 4 17:21:42 /kernel: vm_fault: pager input (probably hardware) error, PID 17975 failure Feb 4 17:21:42 /kernel: vm_fault: pager input (probably hardware) error, PID 13416 failure Feb 4 17:21:42 /kernel: vm_fault: pager input (probably hardware) error, PID 13416 failure Feb 4 17:21:42 /kernel: vm_fault: pager input (probably hardware) error, PID 15198 failure Feb 4 17:21:42 /kernel: vm_fault: pager input (probably hardware) error, PID 1428 failure Feb 4 17:21:42 /kernel: vm_fault: pager input (probably hardware) error, PID 1579 failure Feb 4 17:21:42 /kernel: vm_fault: pager input (probably hardware) error, PID 7675 failure Feb 4 17:21:42 /kernel: vm_fault: pager input (probably hardware) error, PID 21174 failure Feb 4 17:21:42 /kernel: vm_fault: pager input (probably hardware) error, PID 15198 failure Feb 4 17:21:42 /kernel: vm_fault: pager input (probably hardware) error, PID 1579 failure Feb 4 17:21:42 /kernel: vm_fault: pager input (probably hardware) error, PID 7675 failure Feb 4 17:21:42 /kernel: vm_fault: pager input (probably hardware) error, PID 21174 failure Feb 4 17:21:42 /kernel: vm_fault: pager input (probably hardware) error, PID 1579 failure (many many pages snipped) Feb 4 17:31:05 shell1 inetd[13022]: telnet/tcp: root: No such user Feb 4 17:31:58 shell1 inetd[13034]: ftp/tcp: root: No such user Feb 4 17:31:10 shell1 inetd[13079]: ftp/tcp: root: No such user then: panic: kmem_malloc: kmem_map too small Is this any help? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message