Date: Fri, 2 Apr 1999 15:08:34 -0500 (EST) From: Ben Vaughn <bvaughn@prophetnetworks.net> To: "Addr.com Web Hosting" <admin@addr.net> Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Kernel panic question. Message-ID: <Pine.BSF.3.96.990402150737.26185A-100000@shell01.prophetnetworks.net> In-Reply-To: <4.1.19990402112539.02322710@mail.addr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Anthony- I am having the same problem on a dual pII-400 with 384mb of ram, FreeBSD-3.0-RELEASE. I would also be interested in any information on this. -biv On Fri, 2 Apr 1999, Addr.com Web Hosting wrote: > Hi, > > Recently I received the following kernel panic. I was wondering if anyone > has any thoughts or comments on this before I investigate further myself. > The system is a dual PII 400 with 1GB ram and an internal DPT raid > controller running several mirrored disks. Maxusers for the kernel is set > to 256, which I know is low, but anything above that makes the system > unstable (512 makes it panic every hour!). The system is running FreeBSD > 3.0-Release. The system is very stable in general, and is running high load > and with very diverse applications (http, https, sendmail, ftpd, ipop3d, > all the possible cgi scripts in this world and many more), however a panic > like this does occur once every few weeks. Sorry, no core dump for this > one, since I can't replicate the scenario. > Any help, comments or general information would be greatly appreciated. > > Fatal trap 12: page fault while in kernel mode > mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 > fault virtual address = 0x30 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xf020ba9d > stack pointer = 0x10:0xfe3e1ebc > frame pointer = 0x10:0xfe3e1ecc > 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 = 25908 (dir) > interrupt mask = <- SMP: XXX > trap number = 12 > panic: page fault > mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 > boot() called on cpu#0 > > as the FAQ requested, here is the results of "nm" that matched most closely > with the instruction pointer in the kernel. I'm guessing the > "_ufsspec_write" was the funtion which actually caused the panic. > > f020baf4 t _ufsfifo_read > > f020baac t _ufsspec_close > f020ba34 t _ufsspec_read > f020ba70 t _ufsspec_write > > > Thank you in advance, > Anthony Bourov > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990402150737.26185A-100000>