From owner-freebsd-questions@FreeBSD.ORG Fri Jul 7 14:56:40 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 8B47F16A4DA for ; Fri, 7 Jul 2006 14:56:40 +0000 (UTC) (envelope-from jerrymc@clunix.cl.msu.edu) Received: from clunix.cl.msu.edu (clunix.cl.msu.edu [35.9.2.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id F01D943D49 for ; Fri, 7 Jul 2006 14:56:39 +0000 (GMT) (envelope-from jerrymc@clunix.cl.msu.edu) Received: from clunix.cl.msu.edu (localhost [127.0.0.1]) by clunix.cl.msu.edu (8.13.6+Sun/8.13.6) with ESMTP id k67Eud4D018796; Fri, 7 Jul 2006 10:56:39 -0400 (EDT) Received: (from jerrymc@localhost) by clunix.cl.msu.edu (8.13.6+Sun/8.13.6/Submit) id k67EudeC018795; Fri, 7 Jul 2006 10:56:39 -0400 (EDT) From: Jerry McAllister Message-Id: <200607071456.k67EudeC018795@clunix.cl.msu.edu> To: wash@wananchi.com (Odhiambo Washington) Date: Fri, 7 Jul 2006 10:56:39 -0400 (EDT) In-Reply-To: <20060707105212.GH92687@wananchi.com> X-Mailer: ELM [version 2.5 PL7] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Spontaneous reboots with Dell PowerEdge 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: Fri, 07 Jul 2006 14:56:40 -0000 > > Hi, > > I am hoping that someone has come across this weird happening with > Dell PowerEdge 1800. > > We have one such server, with dual power supply, running FreeBSD 4.11-STABLE. > > Spontaneously, the server does a hard boot and comes back up. > /var/log/messages only states the previous system shutdown was unexpected. > This happens at random > times and is completely unpredictable. We have replaced all the RAM modules > with a completely different set, just to eliminate anything to do with faulty > modules, but this has not cured the problem. > > The server has 7 disks on a RAID 5 set. A hard reboot definately calls for a > fsck, which makes the reboot process take forever. I have fsck_y_enable in > rc.conf, because otherwise someone will have to manually run fsck after these > spontaneous reboots! > > I am considering a serial console option to see if I can capture > something, but apart from that I am at my wit's end reagrding this issue. Well, it sounds like something in the area of a power or heat problem. But, it is hard to tell. dmesg.boot will not tell you much about what caused the system to go down. It only contains information about it coming back up. You might try and look in to /var/log/messages et al. But, I would check on power consistency and if any component is heating up. ////jerry > > > > Here is the output of dmesg.boot: > > 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 4.11-STABLE #12: Thu Apr 20 16:44:32 EAT 2006 > root@ns2.wananchi.com:/usr/obj/usr/src/sys/SRV4.x > Timecounter "i8254" frequency 1193182 Hz > CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3192.22-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 > Features=0xbfebfbff > Hyperthreading: 2 logical CPUs > real memory = 3757834240 (3669760K bytes) > avail memory = 3658661888 (3572912K bytes) > Preloaded elf kernel "kernel" at 0xc0414000. > Warning: Pentium 4 CPU: PSE disabled > VESA: v2.0, 16384k memory, flags:0x1, mode table:0xc0398502 (1000022) > VESA: ATI RADEON VE > netsmb_dev: loaded > Pentium Pro MTRR support enabled > md0: Malloc disk > Using $PIR table, 25 entries at 0xc00fb750 > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: irq 0 at device 2.0 on pci0 > pci1: on pcib1 > pcib2: at device 0.0 on pci1 > pci2: on pcib2 > amr0: mem 0xfe9c0000-0xfe9fffff,0xfa0f0000-0xfa0fffff irq 7 at device 14.0 on pci2 > amr0: Firmware 521X, BIOS H430, 256MB RAM > pcib3: at device 0.2 on pci1 > pci3: on pcib3 > pcib4: irq 0 at device 3.0 on pci0 > pci4: on pcib4 > pcib5: at device 0.0 on pci4 > pci5: on pcib5 > pcib6: at device 0.2 on pci4 > pci6: on pcib6 > pcib7: irq 0 at device 4.0 on pci0 > pci7: on pcib7 > pcib8: irq 0 at device 5.0 on pci0 > pci10: on pcib8 > pcib9: at device 0.0 on pci10 > pci11: on pcib9 > em0: port 0xdcc0-0xdcff mem 0xfe4e0000-0xfe4fffff irq 11 at device 7.0 on pci11 > em0: Speed:N/A Duplex:N/A > pcib10: at device 0.2 on pci10 > pci12: on pcib10 > em1: port 0xccc0-0xccff mem 0xfe2e0000-0xfe2fffff irq 11 at device 8.0 on pci12 > em1: Speed:N/A Duplex:N/A > pcib11: irq 0 at device 6.0 on pci0 > pci13: on pcib11 > uhci0: port 0x9ce0-0x9cff irq 11 at device 29.0 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0x9cc0-0x9cdf irq 10 at device 29.1 on pci0 > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0x9ca0-0x9cbf irq 7 at device 29.2 on pci0 > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: 2 ports with 2 removable, self powered > pci0: at 29.7 irq 3 > pcib12: at device 30.0 on pci0 > pci16: on pcib12 > pci16: at 13.0 irq 7 > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port 0xfc00-0xfc0f,0-0x3,0-0x7,0-0x3,0-0x7 irq 0 at device 31.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > orm0: