From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 7 18:12:26 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C05337B404 for ; Mon, 7 Apr 2003 18:12:26 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id E16B943FE1 for ; Mon, 7 Apr 2003 18:12:24 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0008.cvx40-bradley.dialup.earthlink.net ([216.244.42.8] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 192het-0006z7-00; Mon, 07 Apr 2003 18:12:20 -0700 Message-ID: <3E9221A6.1064427@mindspring.com> Date: Mon, 07 Apr 2003 18:11:02 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Christopher Smith References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a49235a70983009676606ba2236623c8d6548b785378294e88350badd9bab72f9c350badd9bab72f9c cc: freebsd-hackers@freebsd.org Subject: Re: Regular kernel panics on 4.7-RELEASE system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2003 01:12:26 -0000 Christopher Smith wrote: > Apologies if I've forgotten anything, this is the first time I've had a > problem like this... > > I have a 4.7-RELEASE box that is suffering regular kernel panics. > Unfortunately, they happen at about 3:15 AM every day, so I've yet to > actually witness one in person :). I have, however, followed the > directions at > http://www.onlamp.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html to > hopefully provide someone here with enough useful information to > address the problem. [ ... ] > #0 dumpsys () at ../../kern/kern_shutdown.c:487 > 487 if (dumping++) { > (kgdb) where > #0 dumpsys () at ../../kern/kern_shutdown.c:487 > #1 0xc0163cf0 in boot (howto=256) at ../../kern/kern_shutdown.c:316 > #2 0xc0164171 in panic (fmt=0xc0251c79 "%s") at > ../../kern/kern_shutdown.c:595 > #3 0xc0214e46 in trap_fatal (frame=0xf96f9c28, eva=0) at > ../../i386/i386/trap.c:974 > #4 0xc0214a99 in trap_pfault (frame=0xf96f9c28, usermode=0, eva=0) at > ../../i386/i386/trap.c:867 > #5 0xc02145df in trap (frame={tf_fs = -998113256, tf_es = -1070989296, > tf_ds = 16, tf_edi = 0, tf_esi = -993978880, > tf_ebp = -110125924, tf_isp = -110125996, tf_ebx = 0, tf_edx = > -1745469505, tf_ecx = 42, tf_eax = 0, tf_trapno = 12, > tf_err = 2, tf_eip = -1071565021, tf_cs = 8, tf_eflags = 66050, > tf_esp = -113611872, tf_ss = -1072095716}) > at ../../i386/i386/trap.c:466 > #6 0xc0213723 in generic_bzero () > #7 0xc01cfef7 in ffs_vget (mp=0xc4c11800, ino=22283597, > vpp=0xf96f9d48) at ../../ufs/ffs/ffs_vfsops.c:1109 Known problem. Fixed in -current. If you have a debugging kernel, go into gdb on the kernel.debug file, and print the code at: > #6 0xc0213723 in generic_bzero () > #7 0xc01cfef7 in ffs_vget (mp=0xc4c11800, ino=22283597, > vpp=0xf96f9d48) at ../../ufs/ffs/ffs_vfsops.c:1109 And then look at the same source code in -current to see the fix. Sorry, I don't have your exact version of the source code, so I can't do this for you. -- Terry