From owner-freebsd-hackers Mon Aug 28 12:11:03 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id MAA20976 for hackers-outgoing; Mon, 28 Aug 1995 12:11:03 -0700 Received: from haven.ios.com (haven.ios.com [198.4.75.45]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id MAA20967 for ; Mon, 28 Aug 1995 12:10:53 -0700 Received: (from rashid@localhost) by haven.ios.com (8.6.11/8.6.9) id PAA11521; Mon, 28 Aug 1995 15:10:19 -0400 From: "Rashid Karimov." Message-Id: <199508281910.PAA11521@haven.ios.com> Subject: Re: S.O.S -2.1Stable and ASUSP54TP4 To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Mon, 28 Aug 1995 15:10:19 -0400 (EDT) Cc: gibbs@freefall.FreeBSD.org, hackers@freebsd.org In-Reply-To: <199508281717.KAA01839@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Aug 28, 95 10:17:44 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 3691 Sender: hackers-owner@freebsd.org Precedence: bulk > > > After having a lot of problems with different > > > motherboards under FreeBSD I've switched to the > > > "editor's choice" - ASUS P54TP4 mb.,which was > > > recommended here by Jordan :) > > > Few problems went away ( like random reboots and > > > stuff), but oneremains consistent: > > > > > > the freaking system loks each and every day and > > > I think this is because of .... something related > > > to HD activity/driver/adapter/whatever. > > > > > > The system is P90,Adaptec 2940 PCI _SCSI adapter, > > > SMC EtherPower. > > > > > > > > > The symptoms: > > > > > > system locks at random times w/o any messages at the console/ > > > log files. Locks means the system becomes unreachable neither > > > from the local net nor from the console > > > After I hit "reboot" switch, system reboots up to the fsck > > > level and it starts complaining that it can't read partition > > > information off the second HDD ( Seagate Barracuda 4 Gb) (!). > > > > > > If one hits "reboot" again and goes to the Adaptec BIOS and runs > > > disk utilities --> media check from there - the BIOS (!) complains > > > that it can not talk to the second HD. > > > > It sounds like your Barracuda is overheating. > > I agree with that assement of the facts given here. But would like a > few ``details'' filled in. > > a) When the lock up occurs are any drive select lights on solid? > > b) Do you have an LED hooked to the controller and what state is it when > the lock occurs? The LED on the adapter ( ADAPTEC ) is OFF. No activity at all - at least for the time I'd been watching it. > > c) Have you any process that core on occasion, or system panics of any > form? [Looking for memory related problems which usually manifest > themselves as random signall 11's if they occur in user land, and > kernel panics if they occur in the kernel] Not with this particualr system. I do see like 5-10 messages every 8-10 hours about processes dying with SIG 3 ( weird ). They are randon though and this doesn't happen right before the system locks up > > d) And my most famous question I always ask, have your _triple_ checked > that your scsi bus is properly terminated and built using high quality > double shielded scsi-ii rated cables? [Applies to external cables, > internal cables should be 110 Ohm 26AWG flat ribon cable.] Also make > sure you are using ACTIVE termination, at fast scsi-II speeds anything > less is dangerous. Well , the last HD is terminated, the first one is not. The terminated one gets the power from the HD. Should I change it to "from the SCSI cable" ? The HDs are internal ones , so I use flat ribbon cable. Don't have a brand on them though ... think they came with adapters. > > e) Back to the Barracuda and heat problems, what is the case temperature > of the drives while operating (give them 4 hours to stabalize under > your worse load before taking a measurement). Also make sure not > to perturb the normal conditions for those 4 hours. Its quite possible that this is a temperature problem, since I've changed the motherboards on Friday and left the PC in not-well-conditioned room. Other thing happened since the time of my last message: The system locked up in the weird way - the console driver was working , I could switch the virt. consoles, when I telnetted from the net - I saw the message "connected', but otherwise the system was dead. Don't know if it is related to the same heat problem ,... Rashid > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Reliable computers for FreeBSD >