From owner-freebsd-questions Sat Feb 9 19:50:39 2002 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (dsl-64-192-6-133.telocity.com [64.192.6.133]) by hub.freebsd.org (Postfix) with SMTP id 27C2237B419 for ; Sat, 9 Feb 2002 19:50:35 -0800 (PST) Received: (qmail 55250 invoked by uid 100); 10 Feb 2002 03:50:32 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15461.60935.767260.959295@guru.mired.org> Date: Sat, 9 Feb 2002 21:50:31 -0600 To: stan Cc: questions@freebsd.org Subject: Re: kernel panic! In-Reply-To: <85821253@toto.iv> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: "Mike Meyer" X-Delivery-Agent: TMDA/0.44 (Python 2.2; freebsd-4.5-STABLE-i386) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG stan types: > On Sat, Feb 09, 2002 at 03:36:24PM +1300, Jonathan Chen wrote: > > On Fri, Feb 08, 2002 at 07:30:06PM -0500, stan wrote: > > > > > > With nothing but the basic filesystems (/ /usr /var) mounted, if I run > > > "perodic daily" my machine crahse, reliably! It's a jernel trap 12, if > > > I caught the message that flashed by on the screen corectly. > > > > > > How can I trap exactly wat's crashing this machine? > > > > Why don't you run a kernel build, if that crashes your machine as > > well, I'd suspect h/w problems; probably memory. > > Make buildworld, and buildkernel run without triggering this panic. > > How can I further diagnose this problem? First, rebuild and reinstall your kernel with the config method, using "config -g MYKERNEL" in /usr/src/sys/i386/conf - assuming it's a 386 architecture machine - and install the resulting kernel. Now make sure you have a swap device that's has at least 64K more space than you have memory, then set set dumpdev to that device in /etc/rc.conf. If you don't have enough room to hold a core image and kernel code on /var/crash, you might want to set dumpdir as well. Now panic the system. As it comes back up, you should get a message about "saving core image" and it will count down to 0. If you then follow the instructions in the Handbook on debugging kernel problems, you should be able to pinpoint the exact line in the kernel that's causing the problem, along with a stack trace of how it got there. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message