Date: Tue, 15 Jan 2002 17:33:27 +0100 (MET) From: hm@hcs.de (Hellmuth Michaelis) To: Martin Kraemer <Martin.Kraemer@Fujitsu-Siemens.com> Cc: freebsd-isdn@freebsd.org Subject: Re: FW: ISDN4BSD not ready for prime time in 4.5-RC ? Message-ID: <20020115163327.27899552@hcswork.hcs.de> In-Reply-To: <20020115170039.A1324@deejai2.mch.fsc.net> "from Martin Kraemer at Jan 15, 2002 05:00:39 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
From the keyboard of Martin Kraemer: > Still I am unsure what actually goes wrong here. > Will isdntrace help me to pinpoint the trouble? I cannot make much sense > from its output (attached). These come together with repeated syslog > messages like... > Jan 15 15:55:20 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: CRC error An HDLC frame had a CRC error and was thrown away. > Jan 15 15:55:20 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: Receive Aborted error The receive of a frame was aborted due to some error. > Jan 15 15:55:24 deejai2 /kernel: i4b-L2 i4b_mph_status_ind: unit 0, persistent deactivation! Link is dead. > Jan 15 15:55:24 deejai2 /kernel: i4b-L3 i4b_mdl_status_ind: STI_PDEACT: unit 0 TEI = 0 = 0x00 > Jan 15 15:56:41 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: CRC error > Jan 15 15:56:41 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: Receive Aborted error Same again, see above. > Jan 15 16:23:53 deejai2 /kernel: i4b: unit 0, assigned TEI = 81 = 0x51 A TEI could be assigned. This means that it is possible to use Layer 1 and 2 (at least for negotiating on a TEI. > Jan 15 16:24:37 deejai2 /kernel: i4b-L1 isic_isac_irq: unit 0: CRC error See above. > What else can I check (short of putting a second card into my PC -- problematic > because of lack of irq's...)? Check your hardware - and _ESPECIALLY_ the BIOS settings of your hardware. Nothing serious with respect to ISDN line handling was changed recently, the same setup as yours (same card, same rbch/isp use) runs fine here in several places. The only thing i can imagine is broken hardware (NTBA, cable, jacks, plugs, card, etc) and/or timing problems on your hardware due to changes in the (PCI/ISA) bus handling in FreeBSD - perhaps you have some sort of settings in your BIOS which were close to some maxes or mins and a slightly changed way of FreeBSD handling bus transfers and/or setups might trigger your problems: check BIOS timing settings. > Can it still be that the NTBA is broken? Maybe. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de 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?20020115163327.27899552>