From owner-freebsd-questions@FreeBSD.ORG Sun Jan 13 07:06:57 2008 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 ABABD16A417 for ; Sun, 13 Jan 2008 07:06:57 +0000 (UTC) (envelope-from tedm@toybox.placo.com) Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [65.75.192.90]) by mx1.freebsd.org (Postfix) with ESMTP id 8F8F313C442 for ; Sun, 13 Jan 2008 07:06:57 +0000 (UTC) (envelope-from tedm@toybox.placo.com) Received: from TEDSDESK (nat-rtr.freebsd-corp-net-guide.com [65.75.197.130]) by mail.freebsd-corp-net-guide.com (8.13.8/8.13.8) with SMTP id m0D76c5g016111; Sat, 12 Jan 2008 23:06:39 -0800 (PST) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Tommy Scheunemann" , Date: Sat, 12 Jan 2008 23:07:44 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914 In-Reply-To: <20080111130111.q4ujmd20gs80c8oc@theseus.arrishq.net> Importance: Normal X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (mail.freebsd-corp-net-guide.com [65.75.192.90]); Sat, 12 Jan 2008 23:06:39 -0800 (PST) Cc: Subject: RE: FreeBSD 6.2 complete freeze 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, 13 Jan 2008 07:06:57 -0000 Your hardware is bad. I've seen this sort of thing dozens of times before. Likely it's bad ram, but it could be something else. Of course, I don't expect you to believe me. Load Windows on it and run some stuff on it and I'll bet it will freeze too. The very first step you need to do on troubleshooting this kind of thing is to build a second system - make sure it's not from the same vendor, not the same motherboard, not the same CPU, etc. - and build the software on it exactly like the first. Then swap it out and see if the freezing starts on the new system. I would bet that it will not. Ted > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Tommy > Scheunemann > Sent: Friday, January 11, 2008 5:01 AM > To: freebsd-questions@freebsd.org > Subject: FreeBSD 6.2 complete freeze > > > Hello everyone, > > I'm running a server with FreeBSD 6.2 installed. Since some time the > machine freezes completely, following the replies by the hoster even > the keyboard won't react so a hard reset is required. There're no > error messages like a Kernel Panic on the screen, just a freeze. > Once the machine is up again, there's also nothing in the logs which > points to a failure. > A dmesg dump: > > Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation. > FreeBSD 6.2-RELEASE-p9 #3: Fri Jan 11 13:35:14 CET 2008 > root@www.angelwings.ws:/usr/obj/usr/src/sys/ANGELWINGS > ACPI APIC Table: > 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 = 0xf29 Stepping = 9 > > Features=0xbfebfbff RR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HT > T,TM,PBE> > Features2=0x4400> > real memory = 1072627712 (1022 MB) > avail memory = 1040654336 (992 MB) > Security auditing service present > BSM auditing present > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > acpi0: on motherboard > acpi0: Power Button (fixed) > cpu0: on acpi0 > acpi_throttle0: on cpu0 > acpi_button0: on acpi0 > acpi_button1: on acpi0 > pcib0: port 0xcf8-0xcff,0x4000-0x40bf on acpi0 > pci0: on pcib0 > agp0: mem > 0xe0000000-0xe7ffffff,0xe8100000-0xe817ffff irq 16 at device 2.0 on pci0 > agp0: detected 892k stolen memory > agp0: aperture size is 128M > uhci0: port 0xd800-0xd81f > irq 16 at device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xd000-0xd01f > irq 19 at device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0xd400-0xd41f > irq 18 at device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem > 0xe8180000-0xe81803ff irq 23 at device 29.7 on pci0 > ehci0: [GIANT-LOCKED] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > uhub3: 6 ports with 6 removable, self powered > pcib1: at device 30.0 on pci0 > pci1: on pcib1 > rl0: port 0xc000-0xc0ff mem > 0xe8000000-0xe80000ff irq 21 at device 5.0 on pci1 > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl0: Ethernet address: 00:0d:61:18:38:3e > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0 > ata0: on atapci0 > ata1: on atapci0 > pci0: at device 31.3 (no driver attached) > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq > 2 on acpi0 > fdc0: [FAST] > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags > 0x10 on acpi0 > sio0: type 16550A > ppc0: port 0x378-0x37f irq 7 on acpi0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > ppbus0: on ppc0 > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > 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 > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > Timecounter "TSC" frequency 2813534500 Hz quality 800 > Timecounters tick every 1.000 msec > ad0: 152627MB at ata0-master UDMA100 > Trying to mount root from ufs:/dev/ad0s1a > rl0: link state changed to UP > arplookup xxx.xxx.xxx.xxx failed: host is not on local network > > The arplookup problem was fixed by setting a static route via: > > route add -host xxx.xxx.xxx.xxx -interface rl0 > > and adding an entry in the ARP table. > > vmstat -i > > interrupt total rate > irq6: fdc0 3 0 > irq14: ata0 4391 4 > irq21: rl0 21161 23 > cpu0: timer 1823817 1999 > Total 1849372 2027 > > The server is running Apache 2.2.x in a Chroot Environment, MySQL in a > Master <- -> Master replication Mode and PF as Firewall. > > Except the self-compiled Kernel the Base System is still the default > one from R9 updated via freebsd-update. > The difference to the GENERIC Kernel is the added PF Support and Auditing. > > Any help would be welcome > > _______________________________________________ > 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" > >