From owner-freebsd-current Fri Mar 31 20:19:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id 7B1B737B6D9 for ; Fri, 31 Mar 2000 20:19:36 -0800 (PST) (envelope-from patrick@137.org) Received: from friley-160-236.res.iastate.edu (localhost [127.0.0.1]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id 2978E1D4; Fri, 31 Mar 2000 22:19:34 -0600 (CST) Reply-To: Patrick Hartling To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic in pmap_enter In-reply-to: Message from Matthew Dillon of "Fri, 31 Mar 2000 19:58:51 PST." <200004010358.TAA36352@apollo.backplane.com> Date: Fri, 31 Mar 2000 22:19:34 -0600 From: Patrick Hartling Message-Id: <20000401041935.2978E1D4@friley-160-236.res.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > :I rebuilt my -current system this morning and am now getting paincs with > :both the SMP and non-SMP kernels. The current panic with a uniprocessor > :kernel is: > : > :panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da0000 > : > :It occurs right after the output for pci0. I'm currently sitting at the db> > :prompt with this kernel. > : > :With an SMP kernel, I get the following at the same point in the boot > :process: > : > :panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da3000 > > This usually happens when you set kernel resource options that are > too high. If you are setting kernel resource options, try commenting > them out. Well, I did recently add options for shared memory settings to get XFree86 4.0 working better. It hadn't caused any problems until now though. I just tried commenting out those options and recompiling, but I still get the panic. > To get your old kernel to boot you may have to remove your ethernet card. That's not an option. ;) I am, however, using the if_fxp module instead of compiling the driver into the kernel, so I can avoid loading the module. > :I can still boot my old kernel (from 3/26), but I get a panic in ifconfig > :when my Ethernet card (an onboard Intel EtherExpress Pro 10/100) is ^^^^^^^ > :configured, so it's not easy for me to get working sources or newer changes. > :Has anyone else seen this? I haven't seen much email today because my > :-current machine is where I normally get my mail. :( > : > : -Patrick > > You can boot the kernel into single user mode. Interrupt the FreeBSD > boot sequence by hitting space, then (typically) type 'boot /kernel -s' > (specify a path to your working kernel if not /kernel). Yes, I know how to get into single-user mode and how to choose kernels at boot time. I was a bit vague in what I was trying to do with my old kernel. Sorry for any confusion. -Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message