Date: Mon, 20 May 1996 01:18:29 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-hackers@freebsd.org (FreeBSD hackers) Cc: cmlambertus@ucdavis.edu (Chris Lambertus) Subject: Re: routes, i'm stumped Message-ID: <199605192318.BAA03191@uriah.heep.sax.de> In-Reply-To: <199605192048.NAA01659@cygnus.ucdavis.edu> from Chris Lambertus at "May 19, 96 01:48:15 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
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. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605192318.BAA03191>