From owner-freebsd-questions@FreeBSD.ORG Wed May 17 01:48:04 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8809B16A416 for ; Wed, 17 May 2006 01:48:04 +0000 (UTC) (envelope-from fbsd@aanet.com.au) Received: from mail.aanet.com.au (mail.aanet.com.au [202.63.43.131]) by mx1.FreeBSD.org (Postfix) with SMTP id 1682543D67 for ; Wed, 17 May 2006 01:47:55 +0000 (GMT) (envelope-from fbsd@aanet.com.au) Received: (qmail 30742 invoked by uid 89); 16 May 2006 20:56:39 -0000 Received: by simscan 1.2.0 ppid: 30714, pid: 30722, t: 0.6712s scanners: attach: 1.2.0 clamav: 0.88.1/m:37/d:1390 Received: from cust7346.vic01.dataco.com.au (HELO ?192.168.1.105?) (202.164.206.178) by mail.aanet.com.au with SMTP; 16 May 2006 20:56:38 -0000 Message-ID: <446A3CE2.4050307@aanet.com.au> Date: Wed, 17 May 2006 06:58:10 +1000 From: fbsd User-Agent: Thunderbird 1.5 (X11/20060326) MIME-Version: 1.0 To: Bill Moran References: <4469B2E0.90408@aanet.com.au> <20060516082747.fa6b46e9.wmoran@collaborativefusion.com> In-Reply-To: <20060516082747.fa6b46e9.wmoran@collaborativefusion.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Help to find cause of recurring crash X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 May 2006 01:48:04 -0000 Bill Moran wrote: > On Tue, 16 May 2006 21:09:20 +1000 > fbsd wrote: > > >> Hello All, >> >> I'm running a home email server and twice in the last week it has >> rebooted itself and been unable to restart due to corruption of the >> filesystem. I found the following in /var/log/messages >> >> May 16 17:46:07 hpvectra syslogd: kernel boot file is /boot/kernel/kernel >> May 16 17:46:07 hpvectra kernel: >> May 16 17:46:07 hpvectra kernel: >> May 16 17:46:07 hpvectra kernel: Fatal trap 12: page fault while in >> kernel mode >> May 16 17:46:07 hpvectra kernel: fault virtual address = 0x1c >> May 16 17:46:07 hpvectra kernel: fault code = supervisor write, >> page not present >> May 16 17:46:07 hpvectra kernel: instruction pointer = 0x20:0xc062c5e8 >> May 16 17:46:07 hpvectra kernel: stack pointer = 0x28:0xe5079c50 >> May 16 17:46:07 hpvectra kernel: frame pointer = 0x28:0xe5079c64 >> May 16 17:46:07 hpvectra kernel: code segment = base 0x0, limit >> 0xfffff, type 0x1b >> May 16 17:46:07 hpvectra kernel: = DPL 0, pres 1, def32 1, gran 1 >> May 16 17:46:07 hpvectra kernel: processor eflags = interrupt >> enabled, resume, IOPL = 0 >> May 16 17:46:07 hpvectra kernel: current process = 52 (vnlru) >> May 16 17:46:07 hpvectra kernel: trap number = 12 >> May 16 17:46:07 hpvectra kernel: panic: page fault >> May 16 17:46:07 hpvectra kernel: Uptime: 5d7h4m50s >> May 16 17:46:07 hpvectra kernel: Dumping 1023 MB (2 chunks) >> May 16 17:46:07 hpvectra kernel: chunk 0: 1MB (159 pages) ... ok >> May 16 17:46:07 hpvectra kernel: chunk 1: 1023MB (261872 pages) 1007 991 >> 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 >> 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 >> 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 >> 111 95 79 63 47 31 15 ... ok >> May 16 17:46:07 hpvectra kernel: >> May 16 17:46:07 hpvectra kernel: Dump complete >> May 16 17:46:07 hpvectra kernel: Automatic reboot in 15 seconds - press >> a key on the console to abort >> May 16 17:46:07 hpvectra kernel: Rebooting... >> >> When I turn on the monitor I see that the reboot has not been successful >> due to "/ was not properly dismounted" and it is asking for fsck to be >> run manually. When I do that everything is fine again. >> > > You can save yourself some hassle by enabling fsck_y_enable="yes" in > /etc/rc.conf. If the initial fsck fails, it will try again with fsck -y. > If that fails, you've got serious trouble. > > That will make the reboots a _little_ less of a problem for you, but it's > only paint over the rust. What you really need to do is set up your > system for kernel debugging: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html > This will allow you to collect enough information that a developer can > help. > > However, before doing that, I would upgrade to 6.1, in case the problem > has already been fixed. Additionally, FreeBSD is heavily tested enough > that kernel panics are _usually_ the result of failing hardware. I'd > get ahold of a memtest86 CD and test your RAM before doing much else. > > Good tip Bill re fsck. I'll do that. I'll also upgrade and run memtest. Ron