From owner-freebsd-questions@FreeBSD.ORG Thu Nov 4 16:27:16 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFA391065674 for ; Thu, 4 Nov 2010 16:27:16 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 425BA8FC13 for ; Thu, 4 Nov 2010 16:27:16 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PE2eg-0002sC-8r for freebsd-questions@freebsd.org; Thu, 04 Nov 2010 17:27:14 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 Nov 2010 17:27:14 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 04 Nov 2010 17:27:14 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Ivan Voras Date: Thu, 04 Nov 2010 17:27:05 +0100 Lines: 75 Message-ID: References: <918795E7-B590-4D1C-BB2B-36C68AFA01D8@partners.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101102 Thunderbird/3.1.6 In-Reply-To: <918795E7-B590-4D1C-BB2B-36C68AFA01D8@partners.org> X-Enigmail-Version: 1.1.2 Subject: Re: Kernel panics? 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: Thu, 04 Nov 2010 16:27:16 -0000 On 11/04/10 12:35, Richard Morse wrote: > Hi! I'm having a problem with an 8.1-RELEASE #0 amd64 machine. Looks like too many different problem all at once. Almost certainly there's a hardware problem somewhere. Try running memtest86 > Three weeks ago, it had a kernel panic, which I was too tired to properly capture. On reboot, I forgot to run fsck in single user mode; about 12-14 hours later it crashed complaining that the background file system checks were inconsistent. > > A day later it crashed with a "server double fault"; I was unfortunately on the way to a meeting, along with all of my technical co-workers, so I wasn't able to see the screen, and it was being reported by someone who was poorly equipped to give a good report. > > A few days later, it had hung (it didn't respond to input), and I needed to hard restart. > > A few days later, the same thing happened. > > Last weekend, on Friday evening it complained about the hard disk controller disappearing (at least, as far back as I was able to go in the screen buffer). > > Saturday night, I finally got a kernel panic that I captured; after this, I turned on core dumps. > > However, last night, it crashed again, and tried to write out a core, but didn't succeed. > > The kernel panic from Saturday night was: > > panic: unknown cluster size > cpuid = 0 > Uptime: 1h49m37s > Cannot dump. Device not defined or unavailable. > aac0: shutting down controller... > > Fatal trap 12: page fault while in kernel mode > cpuid = 9; apic id = 10 > fault virtual address = 0x1d > fault code = supervisor write data, page not present > ... > current process = 12 (irq256: em0) > trap number = 12 > done > > Last night's: > > Fatal trap 12: page fault while in kernel mode > cpuid = 9; apic id = 11 > fault virtual address = 0x8098f90e > fault code = supervisor read data, page not present > ... > current process = 97530 (taper) > trap number = 12 > panic: page fault > cpuid = 9 > Uptime: 3d21h24m57s > Physical memory: 12211MB > Dumping 2942MB: > > Note that there was nothing after the "Dumping 2942MB:"; the cursor was sitting just after the colon. On reboot, it did not find any cores to save to disk (I did have to boot single user and fsck -y; is it possible that this interfered with the core dump? if so, how do I fix this?). > > I tried, this morning, to run memtest86, however both 3.5 and 3.4 just give loud annoying beeps, not displaying anything on screen (not even a menu; once I get past the boot loader from the memtest86 cd, it just starts beeping). > > Any suggestions? > > Thanks, > Ricky > > > The information in this e-mail is intended only for the person to whom it is > addressed. If you believe this e-mail was sent to you in error and the e-mail > contains patient information, please contact the Partners Compliance HelpLine at > http://www.partners.org/complianceline . If the e-mail was sent to you in error > but does not contain patient information, please contact the sender and properly > dispose of the e-mail. > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >