From owner-freebsd-bugs Thu Jul 6 4:10: 6 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 1E72337C254 for ; Thu, 6 Jul 2000 04:10:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id EAA10536; Thu, 6 Jul 2000 04:10:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 6 Jul 2000 04:10:04 -0700 (PDT) Message-Id: <200007061110.EAA10536@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: kern/19726: fatal trap 12 / page fault Reply-To: Sheldon Hearn 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: Sheldon Hearn To: jblaine@mitre.org Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/19726: fatal trap 12 / page fault Date: Thu, 06 Jul 2000 13:08:58 +0200 On Wed, 05 Jul 2000 20:47:27 MST, jblaine@mitre.org wrote: > Machine gateway/firewall/NAT box and is crashing and rebooting every 3 > or 4 days, which makes me very grumpy. I wish I had the knowledge to > fix it. Feel free to steer me through kgdb goop to help you, please. 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)? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message