From owner-freebsd-stable Tue May 8 3:38:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 9710E37B422 for ; Tue, 8 May 2001 03:38:54 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id hccbaaaa for ; Tue, 8 May 2001 20:37:52 +1000 Message-ID: <3AF7CDEC.CF2CD24D@quake.com.au> Date: Tue, 08 May 2001 20:43:56 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-stable Subject: Help - Fatal Trap12's Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hiyas, I have an old P166 with 32mb running as my gateway for my network... It has been running natd and ipfw (with only a few rules) for a while without any problems... But recently it has started to get panics and die... I usualy dont have a monitor pluged into it, but the two crashes I have seen were both fatal trap 12's in natd... This has only started happening with Tribes2 being played over the gateway, but that could just be coincidence or the load this puts on natd?... Anyone know what could be causing this? Nothing has changed on the machine in ages (its 4.0-Stable and hasnt moved since then), and this has just recently started happening... Anyway here is the latest crash: Fatal Trap 12: Page fault while in kernel mode Fault virtual address = 0x4b6d6e4a Faultcode = Supervisor read, page not present Instruction pointer = 0x8:0x4b6d6e4a Stack pointer = 0x10:0xc4acfd34 Frame pointer = 0x10:0xc4acfd54 Code Segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, sran 1 Processor eflags = interrupt enabled, resume, IOPL=0 Curret Process = 136 (natd) Interrupt mask = Trap number = 12 Panic: page fault Thanks for any help! Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message