From owner-freebsd-hackers Mon Dec 2 05:05:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA20336 for hackers-outgoing; Mon, 2 Dec 1996 05:05:59 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA20328 for ; Mon, 2 Dec 1996 05:05:56 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.3/8.6.9) with ESMTP id FAA00341 for ; Mon, 2 Dec 1996 05:05:54 -0800 (PST) To: hackers@freebsd.org Subject: Bizarro bug in 2.1.6 that's had me stumped for ages... Date: Mon, 02 Dec 1996 05:05:53 -0800 Message-ID: <336.849531953@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I kept hoping that this was just me somehow, but after looking and looking for some sort of misconfiguration and still banging into this one, I thought I'd finally ask. I have a gateway machine with an SMC8216 ethernet card in it and an ISDN TA hanging off a standard 16550 serial port. It works just peachy, 99.9% of the time, except after I've really exercised it in some way (seems to happen most frequently after a make world though this could just be the sheerest coincidence). The symptom is that it's suddenly unable to talk to its SLIP interface directly, e.g.: root@whisker-> ifconfig -a .. sl0: flags=9011 mtu 552 inet 204.216.27.194 --> 204.216.27.193 netmask 0xfffffff0 root@whisker-> ping 204.216.27.193 PING 204.216.27.193 (204.216.27.193): 56 data bytes The weirder thing is that it still functions just great as a gateway. On another machine, which it talks to (just fine) through its ethernet interface, I can say: jkh@time-> ping 204.216.27.193 PING 204.216.27.193 (204.216.27.193): 56 data bytes 64 bytes from 204.216.27.193: icmp_seq=0 ttl=254 time=113.731 ms No problem. This is going, after one hop, out the very same SLIP interface that whisker refused to talk to in the previous example. Needless to say, I'm somewhat mystified. A reboot fixes it just fine and things work great for awhile until the next "hang." Any clues? Jordan