From owner-freebsd-bugs Wed Nov 19 22:50:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA14811 for bugs-outgoing; Wed, 19 Nov 1997 22:50:07 -0800 (PST) (envelope-from owner-freebsd-bugs) Received: (from gnats@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA14785; Wed, 19 Nov 1997 22:50:02 -0800 (PST) (envelope-from gnats) Date: Wed, 19 Nov 1997 22:50:02 -0800 (PST) Message-Id: <199711200650.WAA14785@hub.freebsd.org> To: freebsd-bugs Cc: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: kern/5063: Kernel Panic - seems to be always associated with a Cron job running Reply-To: j@uriah.heep.sax.de (J Wunsch) Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/5063; it has been noted by GNATS. 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. ;-)