From owner-freebsd-questions Thu Apr 10 18:14:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA16778 for questions-outgoing; Thu, 10 Apr 1997 18:14:50 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA16773 for ; Thu, 10 Apr 1997 18:14:48 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id SAA07038; Thu, 10 Apr 1997 18:14:43 -0700 (PDT) Date: Thu, 10 Apr 1997 18:14:42 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Harry Reed cc: freebsd-questions@freebsd.org Subject: Re: Help with 2.2.1-Release crashes In-Reply-To: <199704101849.LAA13336@eeyore.lv-hrc.nevada.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 10 Apr 1997, Harry Reed wrote: > 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 Check.. > 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. Try setting the flag 0x1 on npx0. This disables an operation that causes some machines to lock up. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major