From owner-freebsd-hackers Mon Dec 26 23:57:39 1994 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id XAA10486 for hackers-outgoing; Mon, 26 Dec 1994 23:57:39 -0800 Received: from transarc.com (transarc.com [192.54.226.1]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id HAA10480 for ; Tue, 27 Dec 1994 07:57:36 GMT Received: by transarc.com (5.54/3.15) id for hackers@freebsd.org; Tue, 27 Dec 94 02:57:03 EST Received: via switchmail; Tue, 27 Dec 1994 02:57:03 -0500 (EST) Received: from unix3 via qmail ID ; Tue, 27 Dec 1994 02:56:30 -0500 (EST) Received: from unix3 via qmail ID ; Tue, 27 Dec 1994 02:56:27 -0500 (EST) Received: from cui.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix3.sun4.40 via MS.5.6.unix3.sun4_40; Tue, 27 Dec 1994 02:56:27 -0500 (EST) Message-Id: Date: Tue, 27 Dec 1994 02:56:27 -0500 (EST) From: Pat_Barron@transarc.com To: hackers@freebsd.org Subject: Why am I getting these SLIP crashes? Sender: hackers-owner@freebsd.org Precedence: bulk OK, I have some more data about these SLIP related crashes that I've been happening. Here is what I've been doing to start SLIP sessions: 1) "cu -l /dev/cua01 -s 19200" 2) Dial up to Cisco terminal server, start SLIP; the terminal server gives me an IP address (chosen based on what line I've gotten in my hunt group). 3) Use "~^Z" to suspend cu. 4) "slattach -h -s 19200 /dev/cua01" 5) "ifconfig sl0 " 6) "route add default " 7) "telnet " At this point, the machine spontaneously reboots. No panic or anything, just a reboot - as if the CPU has taken a double-fault or something else that would shut it down. This even happens if I do "telnet localhost" in step #7 (but this may be because a DNS lookup is being attempted across the SLIP interface). Now, I *can* get this to work; between step #5 and step #6, I have to do "route add 0"; I get a warning message that says "old usage of trailing 0; assuming route to if", but that was what I wanted anyway. *Then* I can use the network, and th machine does not crash. What changed to make this happen? I am using the -current version of 2.0, which I am sup'ing from freefall. I first noticed this behavior in a kernel I sup'ped some time around the first or second week of December. Thanks, --Pat.