From owner-freebsd-stable@FreeBSD.ORG Fri Mar 11 16:54:21 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 5398116A4D0; Fri, 11 Mar 2005 16:54:21 +0000 (GMT) Date: Fri, 11 Mar 2005 16:54:21 +0000 From: Kris Kennaway To: Emmanuel OTTON Message-ID: <20050311165421.GE72527@hub.freebsd.org> References: <6290d171fce4e3b4ee88f403a4aac711@enstimac.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6290d171fce4e3b4ee88f403a4aac711@enstimac.fr> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: PAE+SMP panic with "page fault while in kernel mode" in many files opened situations X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Mar 2005 16:54:21 -0000 On Fri, Mar 11, 2005 at 10:31:40AM +0100, Emmanuel OTTON wrote: > The panic message is: > ---------------------------------------------------- > fatal trap 12: page fault while in kernel mode > cpuid: 00; apic id = 00 > fault virtual address = 0x24 > fault code = supervisor read, page not present > .../... several lines of hexa addresses, are they needed ? .../... Yes, they're vital. You should also try to obtain a crashdump and traceback as described in the chapter on kernel debugging in the developers' handbook. Kris P.S. Make sure you are not using any old modules (run kldstat). Using modules that are compiled with different options, or are out of date with respect to your kernel, will cause this kind of crash.