Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 Jan 2002 16:08:12 -0500
From:      "Joe & Fhe Barbish" <barbish@a1poweruser.com>
To:        "Rob Hughes" <rob@robhughes.com>
Cc:        "Freebsd-Questions" <freebsd-questions@FreeBSD.ORG>
Subject:   RE: HDLC error in ppp.log
Message-ID:  <LPBBIGIAAKKEOEJOLEGOIEBECGAA.barbish@a1poweruser.com>
In-Reply-To: <1012423804.18587.2.camel@kahuna-ws.robhughes.com>

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