From owner-freebsd-questions Thu Apr 10 11:43:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA22491 for questions-outgoing; Thu, 10 Apr 1997 11:43:08 -0700 (PDT) Received: from eeyore.lv-hrc.nevada.edu (eeyore.lv-hrc.nevada.edu [131.216.27.16]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA22485 for ; Thu, 10 Apr 1997 11:43:05 -0700 (PDT) Received: from scooby.lv-hrc.nevada.edu (scooby.lv-hrc.nevada.edu [131.216.27.8]) by eeyore.lv-hrc.nevada.edu (8.7.6/8.7.3) with ESMTP id LAA13336 for ; Thu, 10 Apr 1997 11:49:50 -0700 (PDT) Message-Id: <199704101849.LAA13336@eeyore.lv-hrc.nevada.edu> From: "Harry Reed" To: Subject: Help with 2.2.1-Release crashes Date: Thu, 10 Apr 1997 11:46:09 -0700 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Here's the scenario ... Hardware: Top Data 5x86-120 w/32 MB RAM Adaptec 2842 VLB SCSI controller 1 Fujitsu M2364(?) 1GB SCSI disk 1 Micropolis 2110? 1GB SCSI disk Archive Viper 250-MB SCSI tape drive Diamond Stealth 64 VLB S3 video card US Robotics intenal modem Logitec Busmouse Under FreeBSD 2.1.0, 2.1.5 (w/XF86 3.1.2) absolutely no problems. Entire machine worked perfectly. Would stay up for weeks on end. Installed (upgraded to) 2.2.1-Release (w/XF86 3..2) without any problems. Recompiled kernel with my old configuration file without any problems. Re-booted machine, again, no problems. Started doing things. No problem for 2 or so hours. Then while doing multiple compiles the system hung. No warning, no console error messages, just hung. Mouse wouldn't respond, ctrl-backspace did nothing, ctrl-alt-del did nothing. System completely dead. Did a reset. Rebooted w/o problem. Same thing, after a few minutes of light/medium SCSI activity the machine would crash. Upgraded to 2.2-970401-RELENG same problem. If I let the machine run with minimal SCSI activity (i.e. running Xlock) the machine will stay up for days w/o incident. When I go anduse the disks then the crashes occur. The 2842 VLB SCSI controller uses the same microcode as the 2940 PCI. Could this be a related problem? I'm going to reconfigure the kernel to use an old Adaptec 1542C to see if the probem goes away or if is SCSI related. Anyhelp would be appreciated. Harry Reed doon@hrc.nevada.edu .