From owner-freebsd-questions Thu Feb 6 17:15:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA20355 for questions-outgoing; Thu, 6 Feb 1997 17:15:19 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA20329; Thu, 6 Feb 1997 17:15:14 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id RAA19508 ; Thu, 6 Feb 1997 17:07:24 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id JAA06394; Fri, 7 Feb 1997 09:28:03 +1100 Date: Fri, 7 Feb 1997 09:28:03 +1100 From: Bruce Evans Message-Id: <199702062228.JAA06394@godzilla.zeta.org.au> To: freebsd-questions@freebsd.org, spatula@gulf.net Subject: Re: What's going on here? Cc: freebsd-bugs@freebsd.org Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I have some more information that may be useful to diagnosing the >problems I have been having. In a nutshell, my system encounters a lot >of page faults while in kernel mode. They can be made to stop by not >using swap at all, but that isn't really such a great solution. > >My most recent trace from the debugger reveals this: (I've reversed the >order so it's chronological) > >Xsyscall at _Xsyscall+0x35 >_syscall(27,27,5,efbf75d,efbfdb54) at _syscall+0x183 >_execve(f137c800,efbfff94,efbfff84,8097060,efbfd75d) at _execve+0x1c7 >_exec_aout_imgoct(efbffe98,f01bf6c18,f137c800,0,0) at _exec_aout_imgoct+0x15f >_exec_new_vmspace(efbffe98,0,0,efbffe98,3e000) at _exec_new_vmspace+0x3d >_pmap_remove_pages(f1425164,0,efbfe000,0,efbde000) at _pmap_remove_pages+0x7b >... > Other information that may be of use: I know that there are bad >sectors on my swap partition, but I had the install program check and >mark bad blocks. Also, this is happening with 3.0-SNAP, but also was >happening with 2.1.5. This is running on a P100, intel chipset, with 32 >megs of RAM and 74 megs swap. Did the install program use bad144 to mark the bad blocks? This only works for IDE disks. exceve() requires virtual memory to work perfectly for some things. Swap probably needs to work perfectly to avoid panics in execve(). Bruce