From owner-freebsd-questions Wed Jan 30 15:37:59 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mail.mango-bay.com (mail.mango-bay.com [208.206.15.12]) by hub.freebsd.org (Postfix) with ESMTP id 38F3A37B405 for ; Wed, 30 Jan 2002 15:37:25 -0800 (PST) Received: from barbish ([63.70.155.73]) by mail.mango-bay.com (Post.Office MTA v3.5.3 release 223 ID# 0-52377U2500L250S0V35) with SMTP id com; Wed, 30 Jan 2002 18:40:54 -0500 From: "Joe & Fhe Barbish" To: "Rob Hughes" Cc: "FBSD" Subject: RE: HDLC error in ppp.log Date: Wed, 30 Jan 2002 18:37:18 -0500 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <1012427882.18587.57.camel@kahuna-ws.robhughes.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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 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