From owner-freebsd-current Mon Dec 14 12:03:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04184 for freebsd-current-outgoing; Mon, 14 Dec 1998 12:03:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lepton.nuc.net (lepton.nuc.net [204.49.61.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04176 for ; Mon, 14 Dec 1998 12:03:36 -0800 (PST) (envelope-from wheelman@nuc.net) Received: from electron (dhcp1.nuc.net [204.49.61.49]) by lepton.nuc.net (8.8.8/8.8.8) with SMTP id OAA01136; Mon, 14 Dec 1998 14:03:03 -0600 (CST) (envelope-from wheelman@nuc.net) From: "Jaime Bozza" To: "Brian Somers" , "Dmitry Valdov" Cc: Subject: RE: cvs commit: src/usr.sbin/ppp ip.c (fwd) Date: Mon, 14 Dec 1998 14:01:17 -0600 Message-ID: <000001be279c$82ba9540$313d31cc@electron.nuc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: <199812141909.TAA04535@keep.lan.Awfulhak.org> Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You say that with debug enabled, ppp thinks everything's ok. Does > this mean that ppp is reporting the modem carrier status as being > ``online'' ? > > If this is the case, then I suspect a hardware failure - it's > unlikely that the sio driver would report carrier if there isn't > any.... all it's doing is an inb() when it's given an > ioctl(,TIOCMGET,). While I haven't done much debugging in this area, (haven't had a lot of time recently), I have two systems that started having the same problem once I upgraded from 2.2.7-stable to 2.2.8-stable. (I know these aren't -current, but the merge of the ppp code was brought over for 2.2.8) The first system I upgraded is using an Adtran ISDN "modem" connected through a serial port. The system was working perfectly for about 15 months (since installation) until I upgraded the box to 2.2.8-stable. Now, when the line is dropped, ppp doesn't "see" the carrier lost and just sits there. For a quick fix, I just wrote a script that resets ppp if it can't ping a known server on our end. At first I thought it could be hardware failure until I updated another 2.2.7-stable box to 2.2.8-stable. (This one is using a USR Courier V.90 modem and has been working fine for about a year.) When the same thing happened (modem dropped carrier, ppp didn't pick it up) I started to think it wasn't a hardware failure. It's unlikely that both of these systems started failing at the same time, especially when the problem happened immediately after upgrading to 2.2.8-stable. Regardless, I'd be happy to run specific debug logs and send them to you if you want. Jaime Bozza Nucleus Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message