Well a nice follow up to all of these this is how it goes cvsupd compiled the kernel etc. etc. before I rebooted just over 2 weeks ago and someone has definately fixed something cos its been running ever since.
9:23AM up 20 days, 23:11, 2 users, load averages: 0.01, 0.08, 0.05 the funny thing is I tried all the debug stuff and to no avail none of it could find the problem for me so I thought to myself if I install a debug kernel and it crashes I loose all access to the machine for the rest of the day until and go and reboot it so i installed the normal kernel i used and its behaved ever since. I'm guessing there's been a vm fix or a bug in the xl net driver fixed. Bri, :) // Wonder if this is the end of my problem thread. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Scheidell Sent: 20 December 2001 14:29 To: Bri; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: the crash screen usually after 4 to 13 days not good... ----- Original Message ----- From: "Bri" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> 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" <nick@foobar#delete2email#.org> 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: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > [EMAIL PROTECTED] > Sent: 19 December 2001 20:18 > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > 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 [EMAIL PROTECTED] > >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 [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message