From nobody  Sat Nov 15 17:14:47 1997
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id RAA08565;
          Sat, 15 Nov 1997 17:14:47 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199711160114.RAA08565@hub.freebsd.org>
Date: Sat, 15 Nov 1997 17:14:47 -0800 (PST)
From: srinivas@hybrid.com
To: freebsd-gnats-submit@freebsd.org
Subject: Kernel Panic - seems to be always associated with a Cron job running
X-Send-Pr-Version: www-1.0

>Number:         5063
>Category:       kern
>Synopsis:       Kernel Panic - seems to be always associated with a Cron job running
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Nov 15 17:20:01 PST 1997
>Closed-Date:    Sun Nov 23 14:48:13 MET 1997
>Last-Modified:  Sun Nov 23 14:49:01 MET 1997
>Originator:     Srinivas Dabir
>Release:        2.0
>Organization:
Hybrid Networks
>Environment:
>Description:
We have a freeBSD 2.0 crashing in the interval of once a week at a customer site.  The last crash indicated that it happenned in our driver interrupt routines.  But the interesting thing is that on two occasions it happneed while the weekly cron job was running at the same time aand the last incident happenned when the atrun job was the current process.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:

From: j@uriah.heep.sax.de (J Wunsch)
To: srinivas@hybrid.com
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: kern/5063: Kernel Panic - seems to be always associated with a Cron job running
Date: Wed, 19 Nov 1997 18:41:36 +0100

 As srinivas@hybrid.com wrote:
 
 > >Description:
 
 > We have a freeBSD 2.0 crashing in the interval of once a week at a
 > customer site.  The last crash indicated that it happenned in our
 > driver interrupt routines.  But the interesting thing is that on two
 > occasions it happneed while the weekly cron job was running at the
 > same time aand the last incident happenned when the atrun job was
 > the current process.
 
 Sorry, but without any further information about what panic, a kernel
 stack trace etc., there's no chance to even remotely guess what your
 problem might be.
 
 Btw., if this is really FreeBSD 2.*0*, then please update it within a
 second.  This release was considered to be rather beta-quality only,
 so it's very likely that your problem has been fixed for ages now.
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)
State-Changed-From-To: open->closed 
State-Changed-By: joerg 
State-Changed-When: Sun Nov 23 14:48:13 MET 1997 
State-Changed-Why:  

Most likely caused by the use of an ancient and rather buggy version 
of FreeBSD.  The originator agreed to try upgrading first. 
>Unformatted:
