From owner-freebsd-hackers Tue Jun 27 11:00:18 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA26235 for hackers-outgoing; Tue, 27 Jun 1995 11:00:18 -0700 Received: from husky.cslab.vt.edu (jaitken@cslab.cs.vt.edu [128.173.41.87]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA26229 for ; Tue, 27 Jun 1995 11:00:16 -0700 Received: (jaitken@localhost) by husky.cslab.vt.edu (8.6.10/8.6.4) id OAA16095; Tue, 27 Jun 1995 14:00:03 -0400 From: Jeff Aitken Message-Id: <199506271800.OAA16095@husky.cslab.vt.edu> Subject: Re: Random Lockups To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Tue, 27 Jun 1995 14:00:03 -0400 (EDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199506271607.MAA00396@crh.cl.msu.edu> from "Charles Henrich" at Jun 27, 95 12:07:36 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 827 Sender: hackers-owner@freebsd.org Precedence: bulk > On one of our 486's and now my Micron, the system will lock up solid causing > a hard reboot in the 486 case. In the P100 case the system has to be reset > by the button. Has anyone else experienced this? This has happened quite > frequently with the 2.0.5R, never with the 0210-SNAP or 04-SNAP With 2.0.5R, I've had this happen twice now. Once was during heavy disk activity, the second was right after I ran the command 'ispcvt'. In both cases, the machine hung, with the disk activity light on, and I had to shut the thing off and back on to reset it. There are no log messages, no messages on the console, no nothing indicating why this happened. This is a 486DX/2 with 16MB, NCR 53c810, micropolis 4110 drive, and the usual goodies (serial card, parallel port, soundblaster card) -- Jeff Aitken jaitken@vt.edu