From owner-freebsd-questions@FreeBSD.ORG Fri Jan 21 11:37:25 2005 Return-Path: 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 D6A2416A4CE for ; Fri, 21 Jan 2005 11:37:25 +0000 (GMT) Received: from mail22.messagelabs.com (mail22.messagelabs.com [62.231.131.211]) by mx1.FreeBSD.org (Postfix) with SMTP id CA59443D31 for ; Fri, 21 Jan 2005 11:37:24 +0000 (GMT) (envelope-from rdls@satamatics.com) X-VirusChecked: Checked X-Env-Sender: rdls@satamatics.com X-Msg-Ref: server-17.tower-22.messagelabs.com!1106307398!20229730!1 X-StarScan-Version: 5.4.7; banners=satamatics.com,-,- X-Originating-IP: [212.125.75.75] Received: (qmail 14168 invoked from network); 21 Jan 2005 11:36:38 -0000 Received: from smtp-6.star.net.uk (212.125.75.75) by server-17.tower-22.messagelabs.com with SMTP; 21 Jan 2005 11:36:38 -0000 Received: (qmail 15494 invoked from network); 21 Jan 2005 11:36:38 -0000 Received: from unknown (HELO hub.bw.satamatics.net) (62.231.144.4) by smtp-6.star.net.uk with SMTP; 21 Jan 2005 11:36:38 -0000 Received: from [10.24.5.250] (doctor-evil.satamatics.net [10.24.5.250]) j0LBabmq051899; Fri, 21 Jan 2005 11:36:37 GMT (envelope-from rdls@satamatics.com) Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: R D L Smith Date: Fri, 21 Jan 2005 11:36:32 +0000 To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.619) cc: Richard Smith Subject: Spontaneous reboot problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 11:37:25 -0000 I have a teramac R310-1U from DNUK running 5.3-RELEASE-p1. It is the only server I have running 5.x. ISTR that the SiS chip set prevented me loading 4.x. The uptime of this server is good unless its under heavy load. When MySQL (with InnoDB) is being worked hard, the server will reboot after a few hours. However, build world will not crash it. I have added the following to rc.conf: dumpdev="/dev/ad0s1b" and the following to the kernel configuration file: makeoptions DEBUG=-g options KDB options PANIC_REBOOT_WAIT_TIME=-1 I have also connected a serial console to the serial port and logged in as "root". I never get a dump file and I never get a message at the console. I don't know what else I can do other than strike this hardware vendor off my list and dump the server. This machine has already had its motherboard replaced. Any clue would be appreciated. Many thanks, Richard Output from dmesg follows... rdls@anya:~ % dmesg Copyright (c) 1992-2004 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 5.3-RELEASE-p1 #1: Wed Dec 8 17:39:58 UTC 2004 rdls@anya.satamatics.net:/usr/obj/usr/src/sys/KERNEL Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2813.53-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf25 Stepping = 5 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1006567424 (959 MB) avail memory = 975388672 (930 MB) ACPI APIC Table: ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0x1400-0x147f,0x1080-0x10ff,0x1000-0x107f,0x480-0x48f,0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe8000000-0xebffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 2.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.5 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ohci0: mem 0xed103000-0xed103fff irq 20 at device 3.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xed100000-0xed100fff irq 21 at device 3.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci0: at device 3.3 (no driver attached) rl0: port 0xec00-0xecff mem 0xed104000-0xed1040ff irq 16 at device 15.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:0d:61:36:14:cf fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: at iomem 0xc0000-0xc7fff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 2813530300 Hz quality 800 Timecounters tick every 10.000 msec ad0: 117243MB [238209/16/63] at ata0-master UDMA133 acd0: CDROM at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted WARNING: /data was not properly dismounted /data: mount pending error: blocks 150848 files 1 WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted /var: mount pending error: blocks 32 files 1 rdls@anya:~ % Final note: the spontaneous reboots do have a tendency to introduce data errors on the disk - however, it still fails even after the disk has been fully repaired. -- R D L Smith Network Systems Director Satamatics Limited Gloucester Road, Tewkesbury, GL20 5TT, United Kingdom T: +44 1684 278610 F: +44 1684 278611 E: rdls@satamatics.com ________________________________________________________________________ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________