From owner-freebsd-hackers Mon Aug 28 12:17:50 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id MAA21210 for hackers-outgoing; Mon, 28 Aug 1995 12:17:50 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id MAA21200 ; Mon, 28 Aug 1995 12:17:48 -0700 Message-Id: <199508281917.MAA21200@freefall.FreeBSD.org> X-Authentication-Warning: freefall.FreeBSD.org: Host localhost didn't use HELO protocol To: "Rashid Karimov." cc: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes), hackers@freebsd.org Subject: Re: S.O.S -2.1Stable and ASUSP54TP4 In-reply-to: Your message of "Mon, 28 Aug 95 15:10:19 EDT." <199508281910.PAA11521@haven.ios.com> Date: Mon, 28 Aug 1995 12:17:48 -0700 From: "Justin T. Gibbs" Sender: hackers-owner@freebsd.org Precedence: bulk >> 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 ,... This means that the system could not access the disk (ie couldn't page in login). It is the exact same problem. > Rashid > >> >> -- >> Rod Grimes rgrimes@gndrsh.aac.dev.com >> Accurate Automation Company Reliable computers for FreeBSD >> > -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations ===========================================