From owner-freebsd-stable Mon Mar 3 11:38:13 2003 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F84037B401 for ; Mon, 3 Mar 2003 11:38:11 -0800 (PST) Received: from linda.pathlink.com (linda.pathlink.com [129.250.170.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9AA443FD7 for ; Mon, 3 Mar 2003 11:38:10 -0800 (PST) (envelope-from kachun@pathlink.com) Received: from dvl-1 (dvl-1.pathlink.com [129.250.170.211]) by linda.pathlink.com (8.11.6/8.11.6) with SMTP id h23Jc8569147; Mon, 3 Mar 2003 11:38:08 -0800 (PST) (envelope-from kachun@pathlink.com) Message-Id: <200303031938.h23Jc8569147@linda.pathlink.com> To: sewall@ix.netcom.com Subject: Re: VM issues in -stable? Cc: freebsd-stable@freebsd.org From: kachun@pathlink.com (Kachun Lee) Date: Mon, 03 Mar 2003 11:38:07 -0800 X-Mailer: WinVN 0.99.8 (x86 32bit) In-Reply-To: References: MIME-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article , you say... > > > >David Schultz wrote: > >> Thus spake Scott Sewall : >> > >> > The FreeBSD July - August 2002 Status Report mentions some VM issues in >> > -stable related to vm_map corruption >> > on large-memory systems under heavy loads. The report indicates there is >> > ongoing work to MFC the bug fixes. >> > >> > Has the work to MFC the bug fixes to -stable been completed? >> > >> > I have a 4.6.2 system with 2GB of memory that's getting a page fault >> > while in kernel mode. The failure occurs >> > when "periodic daily" is run. The active process is always find. I >> > suspect this system may be experiencing the >> > problem described by the report. >> >> If you post the panic message and a backtrace, people might be >> able to tell you more about the particular bug you're running >> into. > >Here's the panic message, the gdb backtrace and dmesg boot ouput. > >-- Scott > > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x0 >fault code = supervisor write, page not present >instruction pointer = 0x8:0xc02d4f53 >stack pointer = 0x10:0xff605c70 >frame pointer = 0x10:0xff605ca4 >code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 >processor eflags = interrupt enabled, resume, IOPL = 0 >current process = 275 (find) >interrupt mask = bio >panic: from debugger >panic: from debugger If you don't think you had hardware problem, one possibility could be your kernel reached the default 1G size limit (esp with 2G or RAM). Check with: sysctl -a | fgrep kvm if you kvm_free is get very close to the kvm_size, you may want to increase KVM_PAGES and see if that fixes your problem. > [snip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message