Date: Sun, 27 Oct 1996 01:12:27 -0400 From: "Gary Palmer" <gpalmer@freebsd.org> To: "Tom W. Cutter" <twcutter@gushi.ns.net> Cc: multimedia@freebsd.org Subject: Re: Mrouted in 2.2-961006-SNAP ? Message-ID: <11597.846393147@orion.webspan.net> In-Reply-To: Your message of "Sat, 26 Oct 1996 11:17:39 PDT." <199610261817.LAA00311@gushi.ns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"Tom W. Cutter" wrote in message ID <199610261817.LAA00311@gushi.ns.net>: > I'm having problems with the getting mrouted 3.8 and the mbone tools > like vat, vic and wb working without locking the system and rebooting. > > Running the the vat, vic, sdr ... without mrouted running works fine. The > machine works as it should. When starting mrouted and running any of the abo > ve > except sdr, the system locks almost immediately without anything written > to /var/log/messages or anything pertinent with mrouted -d 3. I've setup > the kernel to go into diagnostics mode on a kernel error. This doesn't seem > to happen. What does is the system will lock and in about 30 seconds reboot. Take out ``options DIAGNOSTIC'', or stop running X. The problem is your machine panic's, but you don't see it 'cos you're running X. It seems that `options DIAGNOSTIC' claims that a packet is passed through the networking code without valid headers, or somesuch (I barely remember the details, sorry). I found this out before 2.1.5 was released, but didn't have the time to go digging and produce more information, sorry. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11597.846393147>