From owner-freebsd-hackers Thu May 18 08:49:36 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA11073 for hackers-outgoing; Thu, 18 May 1995 08:49:36 -0700 Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA11067 ; Thu, 18 May 1995 08:49:34 -0700 Received: (from tinguely@localhost) by plains.nodak.edu (8.6.11/8.6.10) id KAA06162; Thu, 18 May 1995 10:49:06 -0500 Date: Thu, 18 May 1995 10:49:06 -0500 From: Mark Tinguely Message-Id: <199505181549.KAA06162@plains.nodak.edu> To: adhir@iagi.net, current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Help! Content-Length: 1188 Sender: hackers-owner@FreeBSD.org Precedence: bulk > System: 486dx2/66, 32mb RAM, 512k cache, ASUS SP3G motherboard, using > onboard NCR PCI SCSI connected to 2 drives totalling 5 gigs. Video is > ATI Mach32 PCI w 2mb vram. > > Crash description: Freezes. No panic messages, just freezes up solid. we just bought a DEC XL590s with NCR SCSI, 16 MB, Seagate 4 GB drive, Diamond Stealth , SMC Ultra, GUS sound card (now taken out), and I have been getting freezes running 2.0-950412-SNAP. I thought it was this machine, since it is easy to lock the keyboard (require a complete power cycle) with or without the PS/2 style mouse enabled. I had it up for over a day with internal and external caches disabled, but it was soooo slow, I would have shipped it back if I have to run it this way. Since I have been leaving it in X when I leave at night, for giggles I left the monitor on and it lasted the night. I enabled the process accounting so I can tell when it locks and it is doing anything important - nothing but atrun is being done. I also ran a simple script that keeps track of output from /usr/sbin/swapinfo to make we are not exceeding swap, but that was of no help. I think the key is in the cache settings. --mark.