From owner-freebsd-questions  Sat Aug  5 15:22:51 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id PAA04563
          for questions-outgoing; Sat, 5 Aug 1995 15:22:51 -0700
Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id PAA04557
          for <questions@freebsd.org>; Sat, 5 Aug 1995 15:22:48 -0700
Received: from localhost (localhost [127.0.0.1])
	  by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id XAA01361
	  ; Sat, 5 Aug 1995 23:22:07 +0100
To: Nik Clayton <Nik.Clayton@brunel.ac.uk>
cc: questions@freebsd.org
Subject: Re: System freezes after inactivity 
In-reply-to: Your message of "Sat, 05 Aug 1995 23:03:36 BST."
             <2323.9508052203@mishmash.brunel.ac.uk> 
Date: Sat, 05 Aug 1995 23:22:03 +0100
Message-ID: <1358.807661323@palmer.demon.co.uk>
From: Gary Palmer <gary@palmer.demon.co.uk>
Sender: questions-owner@freebsd.org
Precedence: bulk

In message <2323.9508052203@mishmash.brunel.ac.uk>, Nik Clayton writes:
>I have a 486/66 (EISA, 16Mb RAM) running 2.0R. Does the job very nicely.
>However, ever since I've been running 2.0R on it the system has
>exhibited a tendency to lock-up when it's not doing anything.

OK - this doesn't tell me much about your hardware - from what you say
below, I'm guessing that you are getting stray interrupts or something
which is causing the kernel to hang...

You may want to try compiling the kernel with the debugger in place
and when the kernel locks up, drop to the debugger and see where it's
stuck.

Gary