Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Dec 1998 23:47:24 +0000
From:      Brian Somers <brian@Awfulhak.org>
To:        "Jaime Bozza" <wheelman@nuc.net>
Cc:        "Brian Somers" <brian@Awfulhak.org>, "Dmitry Valdov" <dv@dv.ru>, current@FreeBSD.ORG
Subject:   Re: cvs commit: src/usr.sbin/ppp ip.c (fwd) 
Message-ID:  <199812142347.XAA12050@keep.lan.Awfulhak.org>
In-Reply-To: Your message of "Mon, 14 Dec 1998 14:01:17 CST." <000001be279c$82ba9540$313d31cc@electron.nuc.net> 

next in thread | previous in thread | raw e-mail | index | archive | help
> > 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.

That's what I'm asking :-)  Can you enable debug logging (``set log 
+debug'') and tell me what happens WRT the online/offline messages 
and what ``show modem'' says ?

Cheers.

> Jaime Bozza
> Nucleus Communications, Inc.
> 
> 

-- 
Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
      <http://www.Awfulhak.org>;
Don't _EVER_ lose your sense of humour !



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812142347.XAA12050>