From owner-freebsd-hackers Sun May 19 16:21:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA07253 for hackers-outgoing; Sun, 19 May 1996 16:21:25 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA07248 for ; Sun, 19 May 1996 16:21:19 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA02469; Mon, 20 May 1996 01:21:03 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA28912; Mon, 20 May 1996 01:21:03 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id BAA03191; Mon, 20 May 1996 01:18:29 +0200 (MET DST) From: J Wunsch Message-Id: <199605192318.BAA03191@uriah.heep.sax.de> Subject: Re: routes, i'm stumped To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Mon, 20 May 1996 01:18:29 +0200 (MET DST) Cc: cmlambertus@ucdavis.edu (Chris Lambertus) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199605192048.NAA01659@cygnus.ucdavis.edu> from Chris Lambertus at "May 19, 96 01:48:15 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Chris Lambertus wrote: > There are three problems, two of which appear to be related. (I can only say something to the first one.) > 1. The slip server has a tendency to reboot once every 5-10 days. > I cannot explain this (no hardware faults, no power failures that > I can determine.) Is there a way I can debug this? I tried enabling > kernel crash dumps, but it doesn't generate any when it crashes/reboots. > Is there any other recourse for debugging this kind of thing? I've seen such behaviour (either system hangs, or spontaneous reboots) with a server running FreeBSD 2.0.5 in our company. It's also using an ed0 interface. The problem reduced by the day some (network) load has been taken off this server, but only to got worse the day we moved the ``tcpdump'' router watcher to it. Since this tcpdump used to run well on another (smaller) machine before, i started to look for differences between both systems. I finally found that there have been many changes in the `ed' driver, simply moved the new driver (from some February SNAP) over, killed a few things related to PCCARD systems and thus irrelevant to this box, and gave it a try. This machine ran nicely ever since... -- 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. ;-)