From owner-freebsd-hackers Tue Jul 14 07:41:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11374 for freebsd-hackers-outgoing; Tue, 14 Jul 1998 07:41:05 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11366 for ; Tue, 14 Jul 1998 07:41:03 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id KAA07348; Tue, 14 Jul 1998 10:35:14 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Tue, 14 Jul 1998 10:35:14 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: CyberPsychotic cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Kernel dies. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG it's REALLY time you upgraded. 2.2.1 has accumilated a long list of holes, you are vulnerable to several TCP/IP DoS attacks as well as vulnerabilities in the userland tools get a copy of 2.2.6 (maybe 2.2.7, it' out i heard) you should be fine -Alfred On Tue, 14 Jul 1998, CyberPsychotic wrote: > Hello people, > I have recompiled kernel (2.2.1) and added Firewalls options to it, and > since that, it started rebooting nearly every 15 minutes. Here's the > message it displayed before going down: > > --------------- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0x0 > 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 = 62 (routed) > interrupt mask = > kernel: type 12 trap, code = 0 > ----------------- > > Any ideas what could be wrong? I suppose there might be some problem with > routed daemon and firewalling options. But anyone knows what exactly goes > wrong here? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message