Date: Sun, 3 Feb 2002 20:21:09 +0000 From: hh <hh@dsgx.org> To: Robert Watson <rwatson@freebsd.org> Cc: questions@freebsd.org Subject: Re: crashs on 4.5RC Message-ID: <20020203202109.6679f1e4.hh@dsgx.org> In-Reply-To: <Pine.NEB.3.96L.1020203103320.20638C-100000@fledge.watson.org> References: <008c01c1ab66$b0692820$616156d1@DSGX1WZFFGDP93> <Pine.NEB.3.96L.1020203103320.20638C-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
and this one was the most recent one .. --- a little bit different > Sat Feb 2 01:34:57 GMT 2002 > rl0: promiscuous mode enabled > rl0: promiscuous mode disabled > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x28 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc02065fc > stack pointer = 0x10:0xc034c524 > frame pointer = 0x10:0xc034c544 > 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 = Idle > interrupt mask = > trap number = 12 > panic: page fault > > syncing disks... Copyright (c) 1992-2002 The FreeBSD Project. On Sun, 3 Feb 2002 10:36:03 -0500 (EST) Robert Watson <rwatson@freebsd.org> wrote: > On Fri, 1 Feb 2002, suporte wrote: > > > i updated my 4.4 to an 4.5RC the first time that i compiled .. it was > > crashing almost everysingle hour .. i booted up again on the old > > 4.5PRE-RELEASE .. and recompile the kernel with the new updates from > > cvsup .. k so was finally stable again .. now i can't get an uptime more > > than 4 days .. so i tryed again yesterday made another update using the > > cvsup there was a bunch of things new there .. i compile again .. how > > many time do u guys think this thing gonna keep reseting me and a bunch > > of friends we're having the same problems .. we really use the machine > > is not just a simple for mails .. is for eggdrops/apache/ircds/bncs .. > > stuffs like that .. can anybody give me a light ? > > You need to be more specific. What do you mean by "crash" -- do you get a > system panic, a system hang, a reboot without a message? Is any output > generated along the way? One common pitfall identified in the release > notes was a change in default sizing of socket buffers, which requires > some busy sites to increase nmbclusters (either by recompiling with > different kernel configuration settings, or simply updating loader.conf to > use a larger hard-coded value). Potentially, you could be running into > that. If you're getting a panic, this can be debugged using the kernel > debugging recommendations in the FreeBSD handbook. You'll either want to > enable dumping of system core, or include options DDB in the kernel so you > can debug live. You'll also want to build the kernel using debugging > symbols so that the results are useful. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020203202109.6679f1e4.hh>