From owner-freebsd-questions Thu Jan 31 15:21:19 2002 Delivered-To: freebsd-questions@freebsd.org Received: from ns2.robhughes.com (12-237-138-77.client.attbi.com [12.237.138.77]) by hub.freebsd.org (Postfix) with SMTP id D890137B417 for ; Thu, 31 Jan 2002 15:20:45 -0800 (PST) Received: (qmail 2316 invoked from network); 30 Jan 2002 21:57:32 -0000 Received: from hexch01.robhughes.com (192.168.1.3) by ns2.robhughes.com with SMTP; 30 Jan 2002 21:57:32 -0000 Received: from kahuna-ws.robhughes.com ([192.168.1.13]) by HEXCH01.robhughes.com with Microsoft SMTPSVC(5.0.2195.2966); Wed, 30 Jan 2002 15:57:29 -0600 Subject: RE: HDLC error in ppp.log From: Rob Hughes To: Joe & Fhe Barbish Cc: Freebsd-Questions In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 30 Jan 2002 15:58:02 -0600 Message-Id: <1012427882.18587.57.camel@kahuna-ws.robhughes.com> Mime-Version: 1.0 X-OriginalArrivalTime: 30 Jan 2002 21:57:29.0509 (UTC) FILETIME=[1C8D1550:01C1A9D9] Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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