From owner-freebsd-stable Mon May 6 18:57:33 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA28397 for stable-outgoing; Mon, 6 May 1996 18:57:33 -0700 (PDT) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA28390 for ; Mon, 6 May 1996 18:57:30 -0700 (PDT) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id TAA19668; Mon, 6 May 1996 19:56:58 -0600 Date: Mon, 6 May 1996 19:56:58 -0600 From: Nate Williams Message-Id: <199605070156.TAA19668@rocky.sri.MT.net> To: Warner Losh Cc: stable@FreeBSD.org Subject: Re: SLIP and memory corruption? In-Reply-To: <199605070107.TAA02637@rover.village.org> References: <199605070107.TAA02637@rover.village.org> Sender: owner-stable@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Greetings, > I have a friend that has a small problem with kernel memory > corruption. He has 2 slip lines on his machine. One of them always > connected (or nearly so) to the village's central hub, and the other > connected to another machine from time to time. He's running -stable > from April 15ish. > > We've noticed over the past few weeks that whenever the second SLIP > line is in use, he starts to see negative numbers in his runtime > numbers that ps reports. He also sees routing go nuts as well. Hmm, I've seen no such problems on my router box, but I'm only running one SLIP connection. I would suspect one line would cause the same problems as two, but maybe not. In any case, my router has one dedicated SLIP line, one dedicated PPP line, and a dial-in PPP line from home. 7:54PM up 108 days, 40 mins, 3 users, load averages: 0.00, 0.00, 0.00 USER TTY FROM LOGIN@ IDLE WHAT Strout d2 - 16Mar96 51days -sliplogin (sliplogin) The SLIP connection is from my box at home: 7:54PM up 51 days, 7:54, 3 users, load averages: 0.09, 0.07, 0.02 Pretty darn good line. I wish the line from my house to work was as good as my line from home to work, as it's been up w/out even a blink for 51 days straight. I'm lucky to get 24 hours to our ISP w/out the line going nuts, and U.S. West hasn't been able to pin-point the problem with any luck as it's pretty sporadic. Both of the boxes are running 2.1R with minor patches from -stable. Nate