Date: Fri, 11 Jan 2002 16:48:10 +0100 From: Martin Kraemer <Martin.Kraemer@Fujitsu-Siemens.com> To: freebsd-stable@freebsd.org Subject: ISDN4BSD not ready for prime time in 4.5-RC ? Message-ID: <20020111164810.A568@deejai2.mch.fsc.net>
next in thread | raw e-mail | index | archive | help
Hello, In 4.5-RC (more exact, since ~October), I cannot succeed in using ISDN any more. Yes I changed the cable, and I asked a friend to use ISDN on the same NTBA (from Win2k), to the same provider I use; he had no problems. Only my machine, which used to be ISDN'ing rock-solidly, is unusable, and each connection is broken and torn down after a few packets' exchange between my machine and my provider. In 4.2, 4.3 and 4.4-RELEASE, I used a Teles Teles S0/16.3 ISA (non-PnP) card. Because I noticed the ISDN problems, I brought a Fritz!Card PCI 1.0 and tested that, but to no avail: both experience the same symptoms. OTOH I don't want to go back to FreeBSD-4.3 only for ISDN..... I have the following ISDN configuration in my kernel: --snip-- options TEL_S0_16_3 device isic0 at isa? port 0xd80 irq 5 flags 3 device ifpi pseudo-device "i4bq921" pseudo-device "i4bq931" pseudo-device "i4b" pseudo-device "i4btrc" 8 pseudo-device "i4bctl" pseudo-device "i4brbch" 8 pseudo-device "i4btel" 2 pseudo-device "i4bipr" 8 options IPR_VJ pseudo-device "i4bisppp" 8 --snip-- (Is there a problem with using 8 instead of 4?) I cvsup'ed to 4.5-RC today -- using a modem :-( I noticed there was a patch in the i4bisppp code, but the problems haven't changed. For TELES 16.3: Jan 11 15:44:41 deejai2 /kernel: isic0 at port 0xd80-0xd9f,0x980-0x99f,0x180-0x19f,0x580-0x59f irq 5 flags 0x3 on isa0 Jan 11 15:44:41 deejai2 /kernel: isic0: passive stack unit 0 Jan 11 15:44:41 deejai2 /kernel: isic0: Teles S0/16.3 Jan 11 15:44:41 deejai2 /kernel: i4bctl: ISDN system control port attached Jan 11 15:44:41 deejai2 /kernel: i4btrc: 8 ISDN trace device(s) attached Jan 11 15:44:41 deejai2 /kernel: i4bisppp: 8 ISDN SyncPPP device(s) attached (VJ header compression) Jan 11 15:44:42 deejai2 /kernel: i4b: ISDN call control device attached Jan 11 15:44:42 deejai2 /kernel: i4btel: 2 ISDN telephony interface device(s) attached Jan 11 15:44:42 deejai2 /kernel: i4brbch: 8 raw B channel access device(s) attached Jan 11 15:44:42 deejai2 /kernel: i4bipr: 8 IP over raw HDLC ISDN device(s) attached (VJ header compression) ... Jan 11 15:44:42 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: CRC error Jan 11 15:44:42 deejai2 /kernel: i4b-L2 i4b_T202_timeout: unit 0, N202 = 3 Jan 11 15:44:42 deejai2 /kernel: i4b-L3 T303_timeout: SETUP not answered, cr = 68 Jan 11 15:44:42 deejai2 /kernel: i4b-L3 next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! Jan 11 15:44:42 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: CRC error Jan 11 15:44:42 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: Receive Aborted error Jan 11 15:45:47 deejai2 /kernel: i4b-L2 F_ILL: FSM function F_ILL executing Jan 11 15:45:47 deejai2 /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, state = ST_EST_AW_TEI, event = EV_DLESTRQ! Jan 11 15:45:52 deejai2 /kernel: i4b-L3 T303_timeout: SETUP not answered, cr = 24 Jan 11 15:45:52 deejai2 /kernel: i4b-L3 next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! ... Jan 11 16:25:31 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: CRC error Jan 11 16:25:31 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: Receive Aborted error Jan 11 16:25:43 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: CRC error Jan 11 16:25:43 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: Receive Aborted error Jan 11 16:26:04 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: CRC error Jan 11 16:26:04 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: Receive Aborted error Jan 11 16:26:14 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: CRC error Jan 11 16:26:14 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: Receive Aborted error Jan 11 16:26:14 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: CRC error Jan 11 16:26:14 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: Receive Aborted error Jan 11 16:26:17 deejai2 /kernel: i4b-L2 i4b_mph_status_ind: unit 0, persistent deactivation! Jan 11 16:26:17 deejai2 /kernel: i4b-L3 i4b_mdl_status_ind: STI_PDEACT: unit 0 TEI = 0 = 0x00 and with the Fritz!Card: Jan 11 16:12:43 deejai2 /kernel: ifpi0: <AVM Fritz!Card PCI> port 0xe800-0xe81f mem 0xfedfac00-0xfedfac1f irq 9 at device 16.0 on pci0 Jan 11 16:12:43 deejai2 /kernel: ifpi0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) Jan 11 16:12:43 deejai2 /kernel: ifpi0: passive stack unit 0 ... Jan 11 16:15:55 deejai2 isdnd[476]: DMN init_controller_state: controller 0 is AVM Fritz!Card PCI Jan 11 16:15:55 deejai2 isdnd[476]: DMN i4b isdn daemon started (pid = 476) Jan 11 16:16:01 deejai2 /kernel: i4b-L1 ifpi_ph_data_req: No Space in TX FIFO, state = F4 Awaiting Signal Jan 11 16:16:01 deejai2 /kernel: i4b-L1 ifpi_isac_irq: unit 0: CRC error Jan 11 16:16:03 deejai2 /kernel: i4b-L2 i4b_T202_timeout: unit 0, N202 = 3 Jan 11 16:16:03 deejai2 /kernel: i4b: unit 0, assigned TEI = 73 = 0x49 Jan 11 16:16:03 deejai2 /kernel: i4b-L1 ifpi_isac_irq: unit 0: CRC error Jan 11 16:18:54 deejai2 /kernel: i4b-L1 ifpi_isac_irq: unit 0: CRC error Jan 11 16:19:59 deejai2 /kernel: i4b-L1 ifpi_isac_irq: unit 0: CRC error Jan 11 16:19:59 deejai2 /kernel: i4b-L1 ifpi_isac_irq: unit 0: Receive Aborted error Jan 11 16:20:02 deejai2 /kernel: i4b-L1 ifpi_isac_irq: unit 0: CRC error Jan 11 16:20:02 deejai2 /kernel: i4b-L1 ifpi_isac_irq: unit 0: Receive Aborted error Jan 11 16:20:02 deejai2 /kernel: i4b-L1 ifpi_isac_irq: unit 0: CRC error Jan 11 16:20:02 deejai2 /kernel: i4b-L1 ifpi_isac_irq: unit 0: Receive Aborted error Jan 11 16:20:02 deejai2 /kernel: i4b-L1 ifpi_isac_irq: unit 0: CRC error ...etc... Jan 11 16:20:40 deejai2 /kernel: i4b-L1 ifpi_isac_irq: unit 0: CRC error Jan 11 16:20:40 deejai2 /kernel: i4b-L1 ifpi_isac_irq: unit 0: Receive Aborted error Jan 11 16:20:40 deejai2 /kernel: i4b-L1 ifpi_isac_irq: RPF, input buffer overflow! Jan 11 16:20:41 deejai2 /kernel: i4b-L2 i4b_mph_status_ind: unit 0, persistent deactivation! Jan 11 16:20:41 deejai2 /kernel: i4b-L3 i4b_mdl_status_ind: STI_PDEACT: unit 0 TEI = 0 = 0x00 Anybody seeing a light? Helpless, Martin -- <Martin.Kraemer@Fujitsu-Siemens.com> | Fujitsu Siemens Fon: +49-89-636-46021, FAX: +49-89-636-47655 | 81730 Munich, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020111164810.A568>