From owner-freebsd-questions Mon Feb 11 16:15:46 2002 Delivered-To: freebsd-questions@freebsd.org Received: from hotmail.com (f28.law11.hotmail.com [64.4.17.28]) by hub.freebsd.org (Postfix) with ESMTP id 206AF37B400 for ; Mon, 11 Feb 2002 16:15:36 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 11 Feb 2002 16:15:36 -0800 Received: from 65.161.208.2 by lw11fd.law11.hotmail.msn.com with HTTP; Tue, 12 Feb 2002 00:15:36 GMT X-Originating-IP: [65.161.208.2] From: "Charles Burns" To: dwinkler@ala.net, freebsd-questions@freebsd.org Subject: Re: random reboot problem Date: Mon, 11 Feb 2002 17:15:36 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 12 Feb 2002 00:15:36.0647 (UTC) FILETIME=[6506FD70:01C1B35A] Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >I am having a reoccurring problem with a FreeBSD 4.2 Release install where >my server will randomly reboot from time to time. Normally the machine will >run for a week or two at a time, sometimes 3, without an occurrence, but I >will >now and then get messages in my logs about problems with one of the drives. >When the machine comes back up, it requires a manual fsck to fix the drive >and bring the server back up again. When it occurs, there are no log >entries >about the problem that I can find. [...] >Any information on a fix for this problem, or where to check beyond >replacing >hardware ( have replaced drives in the 4.3 machine with no effect ) would >be greatly appreciated. > >Here is the information from the machine that might be helpful in tracking >down >the problem. [...] FYI, the only time that I have actually seen a random rebooting problem with FreeBSD involved RAM. You can test to see if that is the case using the program available here: http://www.teresaudio.com/memtest86/ Certain Athlon-compatible motherboards are very poorly made, which may be the cause. COuld you post the manufacturer, model, and preferably the chipset used (eg VIAKT133, AMD750, etc). There are certain problems with VIA chipsets and certain motherboards which may possibly be a cause. Some manufacturers somewhat consistantly produce poor boards, such as PCChips (and their 50 or so other names, noteable ESC and Elitegroup). It may possibly be an overheating CPU, but this is quite unlikely considering that Athlons generally just lock up rather than rebooting when they overheat, and that they can get *very* hot before malfunctioning. If the system has a flimsy heatsink or poor contact between the heatsink and chip, such as with cheap paste or a thermal pad, it might be worth spending a few seconds checking out. I use the same SCSI card that your system has, so I know that it works quite well. I have heard of some problems in newsgroups about using the 64-bit version in a 32-bit PCI slot. I doubt it is the drives, too. As you said, you replaced tham, and IBM's SCSI drives are very well made. Sorry I don't have anything specific, but I hope these help a bit if you haven't already considered them. There's always the classic "update the firmware on everything" response that you have probably taken care of as well. _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message