Skip site navigation (1)Skip section navigation (2)
Date:      30 Jan 2002 17:59:54 -0600
From:      Rob Hughes <rob@robhughes.com>
To:        FBSD <freebsd-questions@FreeBSD.ORG>
Subject:   RE: HDLC error in ppp.log
Message-ID:  <1012435194.19015.6.camel@kahuna-ws.robhughes.com>
In-Reply-To: <LPBBIGIAAKKEOEJOLEGOMEBHCGAA.barbish@a1poweruser.com>
References:  <LPBBIGIAAKKEOEJOLEGOMEBHCGAA.barbish@a1poweruser.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Or maybe there's a problem with the modem or the system is just too slow
to handle the data load? I don't know, but those errors are almost
always hardware related.And by port card, I meant serial card. I didn't
realize you're using an internal modem. I swore off those years ago due
to the number of problems I've had with them.I do know that the Zoom
2949 56k external modem that I have never causes any such problems with
my connection, nor have I had connection problems with any of the other
56k external modems I've worked with on other systems.

On Wed, 2002-01-30 at 17:37, Joe & Fhe Barbish wrote:
> What do you mean by "Try a new port card."?
> If you mean a different pci modem, then I must tell you
> the pci modem card I am using is brand new.
> It's a Zoom model 2920 pci modem.
> I am beginning to think that FBSD's sio program needs to
> be updated to handle the new modem speeds.
> I have no problems with my old 14.4 external modem.
> 
> 
> I think the following is the key to the problem,
> I get these sio1 interrupt-level buffer overflows message
> when I use 'tip or cu' command to issue the ATI11 to the
> modem to display the last connection values.
> Using tip command removes user ppp from consideration as
> the cause of the problem.
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Rob Hughes [mailto:rob@robhughes.com]
> Sent: Wednesday, January 30, 2002 4:58 PM
> To: Joe & Fhe Barbish
> Cc: Freebsd-Questions
> Subject: RE: HDLC error in ppp.log
> 
> If you're overflowing the receive buffer, then yes, this will cause the
> same error. Try a new port card. Its sounds like the one you have can't
> handle the amount of data coming in.
> 
> On Wed, 2002-01-30 at 15:08, Joe & Fhe Barbish wrote:
> > I have this in ppp.conf and my moden connects with V42bis.
> > disable pred1 deflate lqr     # compression features & line quality
> > reporting
> > deny    pred1 deflate lqr     # compression features & line quality
> reporting
> >
> > I think the HDLC log error messages are the result of the
> > sio1 interrupt-level buffer overflows error I am getting
> > on the console. What do you think?
> >
> >
> >
> > -----Original Message-----
> > From: Rob Hughes [mailto:rob@robhughes.com]
> > Sent: Wednesday, January 30, 2002 3:50 PM
> > To: Joe & Fhe Barbish
> > Cc: Freebsd-Questions
> > Subject: Re: HDLC error in ppp.log
> >
> > Those are Frame Check Error messages. The system should discard packets
> > with errors in the FCS CRC field, but appears to be hanging on them. Try
> > disabling compression, or enable hw error correction, etc. and see if it
> > gets better or worse.
> >
> > On Wed, 2002-01-30 at 14:28, Joe & Fhe Barbish wrote:
> > > I have a Zoom model 2920 pci modem on sio1 and
> > > connect to my ISP with user ppp.
> > > I keep getting this message on the FBSD console
> > > '30 more sio1 interrupt-level buffer overflows'.
> > >
> > > Most times when this happens a winbox on the LAN is getting
> > > a web page from some web server, and the user does not see
> > > any thing wrong in his display.
> > >
> > > But today I did a make install on apache13-fp and during the
> > > download the connection just stops. Top shows ppp as selected
> > > but not running and FBSD is 98% idle.
> > > The ppp.log has the HDLC messages shown below.
> > >
> > > I also get the more sio1 interrupt-level buffer overflows message
> > > when I use 'tip or cu' command to issue ATI11 to the modem to
> > > display the last connection values.
> > >
> > > Anybody know what the HDLC error message is trying to tell me?
> > >
> > >
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 1, ADDR: 0, COMD: 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 1, ADDR: 0, COMD: 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 9, ADDR: 0, COMD: 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 25, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 50, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 26, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 14, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 31, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 21, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 15, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 26, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 24, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 29, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 16, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 25, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 20, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 24, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 14, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 40, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 31, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 22, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> > > ppp[100]: tun0: Phase: deflink: HDLC errors -> FCS: 23, ADDR: 0, COMD:
> 0,
> > PROTO: 0
> >
> 



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




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