From owner-freebsd-stable Thu Sep 9 10:28:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mongoose.slip.net (mongoose.slip.net [207.171.193.14]) by hub.freebsd.org (Postfix) with ESMTP id A8BE1151BA for ; Thu, 9 Sep 1999 10:28:10 -0700 (PDT) (envelope-from admin@addr.com) Received: from [209.152.191.146] (helo=comp3.addr.com) by mongoose.slip.net with esmtp (Exim 2.12 #4) id 11P7ys-0002Z0-00 for freebsd-stable@FreeBSD.ORG; Thu, 9 Sep 1999 10:27:34 -0700 Message-Id: <4.2.0.58.19990909101426.009d3d40@mail3.addr.com> X-Sender: addr@mail3.addr.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 09 Sep 1999 10:27:28 -0700 To: freebsd-stable@FreeBSD.ORG From: "Addr.com Web Hosting" Subject: Fequent panics in FreeBSD 3.3-RC ... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have recently upgraded a system to the latest stable, and have already received three of these panics: uname -a reads FreeBSD addr3.addr.com 3.3-RC FreeBSD 3.3-RC #0: Tue Sep 7 21:57:07 GMT 1999 root@addr3.addr.com:/usr/src/sys/compile/ADDRKERN i386 the panic reads: Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 01000000 fault virtual address = 0xc4e7f08c fault code = supervisor write, page not present instruction pointer = 0x8:0xc025f47a stack pointer = 0x10:0xd2ed2f0c frame pointer = 0x10:0xd2ed2f1c 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 = 12498 (httpd) interrupt mask = net tty bio cam <- SMP: XXX trap number = 12 panic: page fault mp_lock = 01000002; cpuid = 1; lapic.id = 01000000 boot() called on cpu#1 nm /kernel for that area shows: c025f314 T pmap_page_exists c025f30c T pmap_pageable c025f3a4 T pmap_remove_pages c025f4e0 t pmap_testbit I have also received one panic at c025e2cc: nm /kernel | grep c025e2 c025e290 t pmap_insert_entry And also one complete freeze up. This is all in only 3 days, but I have found no way to replicate the error. It doesn't seem entirely random since it always occurs in "pmap" related functions. These panics have been following me since 3.0-STABLE and into 3.2-RELEASE and now in 3.3-RC. They seem like the result of some sort of attack because they increase in frequency if we have a spam issue with a user or similar on that machine. The server is a dual PentiumIII-450 with 512 MB of ram and DPT raid controller. Max users is set at 256 (I don't know about this version, but on previous versions setting it higher caused constant panics). It usually runs at load average of about 2, serving apache/sendmail/telnet/ftpd/ipop3d as well as a little bit of NFS data for local updates and a completely idle NFS client. Same panics occurred on server with dual P||-400 with 1GB of ram and DPT controller, so it is not an issue caused by faulty hardware. Oh, I am not using "device apm" since this seems to be a cause for a lot of discussion lately. If you need any more info I would be glad to provide it. Any help regarding this problem would be greatly appreciated. Best Regards, Anthony Bourov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message