From owner-freebsd-questions@FreeBSD.ORG Sun Apr 9 14:01:56 2006 Return-Path: X-Original-To: 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 07DF516A402 for ; Sun, 9 Apr 2006 14:01:56 +0000 (UTC) (envelope-from lauasanf@wilderness.homeip.net) Received: from mxsf32.cluster1.charter.net (mxsf32.cluster1.charter.net [209.225.28.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80B5E43D45 for ; Sun, 9 Apr 2006 14:01:53 +0000 (GMT) (envelope-from lauasanf@wilderness.homeip.net) Received: from mxip07a.cluster1.charter.net (mxip07a.cluster1.charter.net [209.225.28.137]) by mxsf32.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id k39E1pLA008731 for ; Sun, 9 Apr 2006 10:01:52 -0400 Received: from 24-159-55-136.dhcp.jcsn.tn.charter.com ([24.159.55.136]) by mxip07a.cluster1.charter.net with ESMTP; 09 Apr 2006 10:01:51 -0400 X-IronPort-AV: i="4.04,104,1144036800"; d="scan'208"; a="1732127:sNHT27893790" Date: Sun, 9 Apr 2006 08:55:36 -0500 (CDT) From: Laurence Sanford X-X-Sender: lauasanf@devel.cotharyus.net To: fbsd_user In-Reply-To: Message-ID: <20060409085333.C26227@devel.cotharyus.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: questions@freebsd.org Subject: RE: Panic/reboot - a little help. 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: Sun, 09 Apr 2006 14:01:56 -0000 On Sun, 9 Apr 2006, fbsd_user wrote: > Here is the standard causes. > I all most all cases this is a hardware problem. Yes, this I suspected. > > Motherboard is overheating because of years of accumulated dust. > Open box and use small paint brush to blow away dust on motherboard > chips. > Remove heat sink on CPU and clean out chocking dust and reinstall. > Done this regularly. To all of my systems. > Power supply's just go bad over time resulting in lower operating > voltages > to motherboard and hard drive. Hard drive will not spin as fast > which causes > the r/w heads not to fly above platter with out touching the > surface. > Hard disk starts going bad because of this and will need replacement > along with the power supply. > > Power supply has cooling fan which can become plugged with dust. > Cleaning out dust in power supply may result in output voltage to > return to normal. > > Hard drive central bearing wears out over time and causes the > platters > to wobble allowing the r/w heads to rub on surface of platters > causing > surface damage and loss of data. > > What you may be experiencing is end-of-life of your PC. > > Back up your user data now or it may be gone for every. > > It's possible. I certainly haven't ruled out end of life. Fortunately, I back up all of my data once a week, and if I change something important, I make a backup then as well. You only have to lose everything once :) > > > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Laurence > Sanford > Sent: Sunday, April 09, 2006 8:57 AM > To: questions@freebsd.org > Subject: Panic/reboot - a little help. > > > My desktop box, which has run very stable for a couple years now > using > which ever version of FreeBSD I've been running at the time, has > developed a sudden and alarming need to panic. I have two vmcore > files > at this point, but I'm unsure how much actual help they'll be in > figuring out what's happening because I don't have debugging > compiled > into the kernel (never needed it before!) nor do I actually know > exactly > how to gather any information from them if they *can* still be of > use. I > can tell you this has happened twice now in the past 5 hours. Once I > was > asleep, and once I was reading my email. I'm going to include what I > can > here, any suggestions or ideas what's happening will be a great > help. > > lauasanf@colossus(~)$ dmesg > Copyright (c) 1992-2005 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD 6.0-STABLE #2: Sat Jan 14 12:03:12 CST 2006 > lauasanf@colossus.cotharyus.net:/usr/obj/usr/src/sys/Colossus > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) MP 2000+ (1666.74-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 > > Features=0x383fbff PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE> > AMD Features=0xc0480800 > real memory = 536346624 (511 MB) > avail memory = 515342336 (491 MB) > MPTable: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 1 > cpu1 (AP): APIC ID: 0 > ioapic0: Assuming intbase of 0 > ioapic0 irqs 0-23 on motherboard > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > cpu0 on motherboard > cpu1 on motherboard > pcib0: pcibus 0 on motherboard > pci0: on pcib0 > agp0: port 0x1010-0x1013 mem > 0xf8000000-0xfbffffff,0xf4c00000-0xf4c00fff at device 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at device 5.0 (no driver attached) > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 7.1 on > pci0 > ata0: on atapci0 > ata1: on atapci0 > pci0: at device 7.3 (no driver attached) > pcib2: at device 16.0 on pci0 > pci2: on pcib2 > ohci0: mem 0xf4900000-0xf4900fff irq > 19 > at device 0.0 on pci2 > ohci0: [GIANT-LOCKED] > usb0: OHCI version 1.0, legacy support > usb0: SMM does not respond, resetting > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 4 ports with 4 removable, self powered > xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0x2000-0x207f mem > 0xf4901000-0xf490107f irq 19 at device 8.0 on pci2 > miibus0: on xl0 > ukphy0: on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > xl0: Ethernet address: 00:e0:81:24:e7:bb > pmtimer0 on isa0 > orm0: at iomem > 0xc0000-0xc7fff,0xc8000-0xc87ff,0xe0000-0xe3fff on isa0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse Explorer, device ID 4 > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > ppbus0: on ppc0 > ppbus0: IEEE1284 device found /NIBBLE/ECP > Probing for PnP devices on ppbus0: > ppbus0: MLC,PCL,PML > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > isa0 > unknown: can't assign resources (port) > unknown: can't assign resources (memory) > unknown: can't assign resources (port) > unknown: can't assign resources (port) > unknown: can't assign resources (irq) > unknown: can't assign resources (port) > Timecounters tick every 1.000 msec > ad0: 43979MB at ata0-master UDMA100 > ad2: 38166MB at ata1-master UDMA100 > acd0: DVDR at ata1-slave UDMA33 > SMP: AP CPU #1 Launched! > Trying to mount root from ufs:/dev/ad0s1a > WARNING: / was not properly dismounted > WARNING: /tmp was not properly dismounted > WARNING: /usr was not properly dismounted > /usr: mount pending error: blocks 216 files 5 > WARNING: /usr/ports was not properly dismounted > WARNING: /usr/src was not properly dismounted > WARNING: /var was not properly dismounted > cd0 at ata1 bus 0 target 1 lun 0 > cd0: Removable CD-ROM SCSI-0 device > cd0: 33.000MB/s transfers > cd0: Attempt to query device size failed: NOT READY, Medium not > present > drm0: mem > 0xf6000000-0xf7ffffff,0xf4800000-0xf4803fff,0xf4000000-0xf47fffff > irq 18 > at device 5.0 on pci1 > info: [drm] AGP at 0xf8000000 64MB > info: [drm] Initialized mga 3.2.1 20051102 > > Also, this message comes up when the system saves the vmcore: > Reboot after panic: Page Fault > > Thanks in advance for the assistance with this. > _______________________________________________ > 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" > >