From owner-freebsd-questions Fri Jan 25 13:54:45 2002 Delivered-To: freebsd-questions@freebsd.org Received: from smtp3.mx.pitdc1.stargate.net (smtp3.mx.pitdc1.stargate.net [206.210.69.143]) by hub.freebsd.org (Postfix) with SMTP id 54CC337B400 for ; Fri, 25 Jan 2002 13:54:23 -0800 (PST) Received: (qmail 22556 invoked from network); 25 Jan 2002 21:47:18 -0000 Received: from dap-209-166-135-174.nfas.greensburg-tnt-1.sns234.pa.stargate.net (HELO wastegate.net) (209.166.135.174) by smtp3.mx.pitdc1.stargate.net with SMTP; 25 Jan 2002 21:47:18 -0000 Received: from mother.wastegate.net (mother.wg.local [192.168.1.2]) by wastegate.net (Postfix) with SMTP id E05724844F; Fri, 25 Jan 2002 16:47:38 -0500 (EST) From: "Doug Reynolds" To: "freebsd-questions@freebsd.org" , "Joe Blow" Date: Fri, 25 Jan 2002 16:49:41 -0500 Reply-To: "Doug Reynolds" X-Mailer: PMMail 2000 Professional (2.20.2380) For Windows 98 (4.10.2222) In-Reply-To: <200201251054.g0PAsET01868@mail18.bigmailbox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD 4.x - lock ups + reboots Message-Id: <20020125214738.E05724844F@wastegate.net> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 25 Jan 2002 02:54:14 -0800, Joe Blow wrote: >This mailing list is my last resort for a hideous problem I've endured for >well over a year. I first started experiencing it with FreeBSD 4.2-R. I >bought the FreeBSD 4.3-R CDs when they first came out last year, hoping that >the problem would disappear. It didn't. > >I have searched through the freebsd.org problem reports and mailing list >arhives, through USENET, and through google.com. Although it seems many >other users are experiencing similar problems, solutions have been elusive. >The panic message is basically... > >Fatal trap 12: page fault while in kernel mode >[...] > >... with the register values and so forth that are meaningless to post here >without some kind of backtrace. Is there any reason why I am unable to get >crash dumps? sounds like bad ram to me. try installing and using /usr/ports/sysutils/memtest it helps identify if you ram is bad. --- doug reynolds | the maverick | mav@wastegate.net PGP Public Key Fingerprint: 6E7B 9993 B503 6D45 E33A 2019 26E5 C1DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message