From owner-freebsd-bugs Thu Jul 6 6:50: 9 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0B09837C2D3 for ; Thu, 6 Jul 2000 06:50:06 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id GAA76726; Thu, 6 Jul 2000 06:50:06 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 6 Jul 2000 06:50:06 -0700 (PDT) Message-Id: <200007061350.GAA76726@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Jeff Blaine Subject: Re: kern/19726: fatal trap 12 / page fault Reply-To: Jeff Blaine Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/19726; it has been noted by GNATS. From: Jeff Blaine To: Sheldon Hearn Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/19726: fatal trap 12 / page fault Date: Thu, 06 Jul 2000 09:49:44 -0400 > I don't remember having seen this kind of problem reported by anyone > else (a panic in arpintr(), that is), and 4.0-RELEASE has been around > for a while. Is there anything you can do to rule out hardware (e.g. > confirm that you're not overclocking, re-seat RAM, swap RAM, try an > entirely different box)? I'm not overclocked. I can start by reseating the RAM tonight. If it crashes again the same way, I'll take out 16 of the 32MB and try it that way for a bit. If it crashes again, I'll do a flip-flop of the 16MB RAM and try that other 16. Trying a different box is not an option for me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message