From owner-freebsd-mobile Wed Mar 13 13:43:14 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 26C9D37B444 for ; Wed, 13 Mar 2002 13:42:38 -0800 (PST) Received: from caddis.yogotech.com (caddis.yogotech.com [206.127.123.130]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id OAA11599; Wed, 13 Mar 2002 14:42:36 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g2DLgXv33605; Wed, 13 Mar 2002 14:42:33 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15503.51145.499114.537234@caddis.yogotech.com> Date: Wed, 13 Mar 2002 14:42:33 -0700 To: dochawk@psu.edu Cc: nate@yogotech.com (Nate Williams), freebsd-mobile@FreeBSD.ORG Subject: Re: init 1 causes panic on A21p and A22m In-Reply-To: <200203132138.g2DLc5T00692@fac13.ds.psu.edu> References: <15503.46021.471159.480323@caddis.yogotech.com> <200203132138.g2DLc5T00692@fac13.ds.psu.edu> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > > I just tried it without X, and got the same thing. It's a page read > > > failure in supervisor mode. > > > You may need to get a back-trace. It sounds like you're get a NULL > > pointer exception. Can you try a minimal boot (no X, no other programs > > runningg, etc..) and see if it's related to some program that's running. > > I did this with /usr and /home set to ro in fstab (they take forever to > fsck, even with soft updates), and xdm disabled. It still happened. Can you just for kicks try booting into single-user mode and then shutdown down to see if something happens. Hit a key at boot up, and then type 'boot -s'. Once it comes up, hit return at the /bin/sh prompt, and then type 'reboot'. > How do I backtrace a kernel panic? I think I have a gig of swap with a > hlaf-gig of ram, but I don't know how to cause the dump (or what to do > with it). See the handbook section on kernel debugging. You'll need to setup your swap device in /etc/rc.conf to something: dumpdev="/dev/ad0s1b" (It should be the same as your swap partition. > > This is happening on two different hardware boxes, right? If it wasn't > > happening on two different boxes, I would suspect a hardware issue. > > Two boxes--but the same hard drive. It may be completely unrelated to the hard drive. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message