Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Feb 2000 14:25:09 +0100
From:      Gunnar Kedenburg <9kedenbu@informatik.uni-hamburg.de>
To:        Gary Jennejohn <garyj@muc.de>, freebsd-isdn@freebsd.org
Subject:   Re: teles 16.3 pnp errors
Message-ID:  <20000210142509.A24270@informatik.uni-hamburg.de>
In-Reply-To: <200002091832.TAA11400@peedub.muc.de>; from garyj@peedub.muc.de on Wed, Feb 09, 2000 at 07:32:19PM %2B0100
References:  <30121.950120384@www16.gmx.net> <200002091832.TAA11400@peedub.muc.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 09, 2000 at 07:32:19PM +0100, Gary Jennejohn wrote:
> I wasn't trying to dump on you. I was trying to get you to provide
> some information regarding the failure modes you're seeing. That's
> what I meant with my "helps no-one", since no useful information
> regarding the error was provided.

Okay, I included some info below. If you need something I left out, please tell me.

Without any apparent cause, i get the following messages on syslog:
These were the first messages that appeared after a reboot.

Feb  7 13:16:07 ozone /kernel: i4b-L1-isic_isac_irq: RPF, input buffer overflow!
Feb  7 13:16:07 ozone /kernel: i4b-L1-isic_isac_irq: RPF, input buffer overflow!
Feb  7 13:16:07 ozone /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error
Feb  7 13:16:07 ozone /kernel: i4b-L1-isic_isac_irq: unit 0: Receive Aborted error
Feb  7 13:16:07 ozone /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error
Feb  7 13:16:07 ozone /kernel: i4b-L1-isic_isac_irq: RPF, input buffer overflow!
Feb  7 13:16:07 ozone /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error
Feb  7 13:16:07 ozone /kernel: i4b-L1-isic_isac_irq: unit 0: Receive Aborted error
Feb  7 13:16:07 ozone /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error
Feb  7 13:16:07 ozone /kernel: i4b-L1-isic_isac_irq: RPF, input buffer overflow!
Feb  7 13:16:07 ozone /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error
Feb  7 13:16:07 ozone /kernel: i4b-L1-isic_isac_irq: unit 0: Receive Aborted error
Feb  7 13:16:09 ozone /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error
Feb  7 13:16:10 ozone /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error
Feb  7 13:16:10 ozone /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error
Feb  7 13:16:19 ozone /kernel: i4b-L1-isic_isac_irq: RPF, input buffer overflow!
Feb  7 13:16:19 ozone /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error
Feb  7 13:16:21 ozone /kernel: i4b-L1-isic_isac_irq: RPF, input buffer overflow!
Feb  7 13:16:21 ozone /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error
...

The messages appear sometimes directly after reboot, or a little while later.
After the next reboot (and after leaving the machine off for four minutes), the same messages are shown, but the order is different, eg. the first error is a 
	i4b-L1-isic_isac_irq: unit 0: CRC error
and not the
	i4b-L1-isic_isac_irq: RPF, input buffer overflow!
as above.

I use userland-ppp to connect to my isp. It worked a few times, but generally not after the error messages appeared. When the connection to the isp is established, everything works very well.
But even after a connection had been established, the errors occur again after i shut down the connection.

My ISDN Kernel config is:

options         TEL_S0_16_3_P  
device          isic
pseudo-device   "i4bq921"       # Q.921 / layer 3
pseudo-device   "i4bq931"       # Q.931 / layer 3
pseudo-device   "i4b"           # layer 4
pseudo-device   "i4bctl"        # userland driver to control the whole thing
pseudo-device   "i4brbch"  2    # userland driver for access to raw B channel
pseudo-device   "i4btrc"   2    # userland driver to do ISDN tracing 


According to it's PnP identification string, the card is a "Teles S0/16.3 PnP".
On the card, i found the following: TELES.S0/PnP, revision 1.5 N, 1996

I don't know if that helps you, but the two SIEMENS chips on the card are:
- 641L
  PSB 21525 N
  HSCX TE V2.1
- 630L
  PSB 2186N V1.1
  ISAC-S TE

Plus there is an ALTERA
- EPM7032LC44-15T
  BA9616

As i said before, the card works perfectly under linux for over a year now, so I don't think the hardware is the problem.
-- 
Gunnar.
pgp encrypted/signed mail preferred.


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




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