Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!news2.near.net!satisfied.elf.com!usenet From: *Hobbit* <hobbit@asylum.sf.ca.us> Newsgroups: comp.os.386bsd.bugs Subject: more on the "mysterious reboot" problem Date: 25 Jan 1995 03:20:09 EST Organization: large Lines: 19 Sender: root Approved: God Expires: 1 Apr 95 12:34 Message-ID: <3g520d$amg@satisfied.elf.com> NNTP-Posting-Host: asylum.sf.ca.us Having re-read someone's complaint about the sudden reboots in 2.0 or 950112-SNAP or whatever it was, maybe caused by garbage on a PPP line, adding this might help chase the problem: I'm seeing similar things too, but [I think] only when running ROUTED. After routed has been running for half an hour or so [doing utterly abominable things to the kernel tables, but that's a different problem] I can often cause the reboot by doing something possibly related to routing weirdness, such as traceroute, or ping -s some-src-addr. This is probably not a mismatched binaries problem, as I've sucked down and built afresh all the relevant programs [routed, traceroute, ping, ifconfig, netstat, etc etc etc]... Anyway, try turning off routed and see if the system stays up longer. [my first attempt with gated didn't fix it; it only left me a lovely 8Mb core file...] _H*