From owner-freebsd-hackers Thu Dec 20 6:29:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scanner.secnap.net (scanner.secnap.net [216.241.67.74]) by hub.freebsd.org (Postfix) with ESMTP id 32FFB37B426; Thu, 20 Dec 2001 06:29:21 -0800 (PST) Received: from MIKELT ([10.1.1.40]) by scanner.secnap.net (8.11.3/8.11.5) with SMTP id fBKET6U57126; Thu, 20 Dec 2001 09:29:06 -0500 (EST) (envelope-from scheidell@secnap.net) Message-ID: <004e01c18962$a39f7020$2801010a@MIKELT> From: "Michael Scheidell" To: "Bri" , , , References: Subject: Re: the crash screen usually after 4 to 13 days not good... Date: Thu, 20 Dec 2001 09:28:47 -0500 Organization: Secnap Network Security, LLC. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Bri" To: ; ; Sent: Thursday, December 20, 2001 6:09 AM Subject: FW: the crash screen usually after 4 to 13 days not good... > yeah I'm running FreeBSD 4.4 running the lastest kernel 4.4 RELEASE-p1 > > with kernel options > > options IPFIREWALL > options IPDIVERT > options IPFIREWALL_VERBOSE > > yeah I'll take a look at the handbook on that issue thanks from an earler post: Id be currious if its crashing in the same vm section my system is crashing in. From: "Nick Hilliard" Newsgroups: comp.unix.bsd.freebsd.misc Sent: Tuesday, December 11, 2001 2:11 PM Subject: Re: hitting kern.maxfiles causes panic 12 reboot? > Michael Scheidell wrote: > > I know (overall) what the program is, nessusd ver 1.11 > > I increased kern.maxfiles to 8192 and it seems to get past the 4k files open > > point, but still dies. > > hard to directly tell what process is doing it since the panic shows up on > > the (nonexistant) console. > > You could get a crash dump and have a look at it: enable "dumpdev" in > /etc/rc.conf, > and then you should be able to get a kernel stack dump. > > There's more information about doing this sort of thing on: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneld ebug.html > > Nick > > Bri, > > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of > brian.hood@blueyonder.co.uk > Sent: 19 December 2001 20:18 > To: freebsd-stable@FreeBSD.ORG; freebsd-hackers@FreeBSD.ORG > Subject: the crash screen usually after 4 to 13 days not good... > > > What happens is the network card on xl0 going to down and its light goes > >off on the hub and I get this crash address straight after. > > > >It's a 3Com 900TPO 10Mbps > > > >Usually it reboots but its locked this time with it on the screen > > > >Fatal trap 12: page fault while in kernel mode > >Fault virtual address = 0xb0 > >Fault code = supervisor read, page not present > >Instruction pointer = 0x8:0xc02d7507 > >Stack pointer = 0x10:0xc4f8ae50 > >Frame pointer = 0x10:0xc4f8ae84 > >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 = 11999 (sh) > >interrupt mask = none > >trap number = 12 > >panic: page fault > > > >syncing disks... 10 > >done > >uptime: 2d18h27m28s > > > >when I reboot it I will be able to send this e-mail I hope:) > > > >any help is more than welcome > > >Bri, > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-stable" in the body of the message > ----------------------------------------------------------------------- > > Please see the FAQ and the handbook about obtaining debugging > crashdumps so this problem can be debugged. You also forgot to > mention which version of FreeBSD you're running. > > Kris > > > 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