Date: Wed, 19 Jul 2000 13:53:22 +0200 From: "Sokon" <sokon@dds.nl> To: "'Gary Jennejohn'" <garyj@muc.de> Cc: <freebsd-isdn@freebsd.org> Subject: RE: i4b CRC / Recieve Aborted error, user PPP Message-ID: <000001bff177$f1350810$0201a8c0@danielle> In-Reply-To: <200006270551.HAA60328@peedub.muc.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, sorry for the late response, I was away for some time. As you might recall I received the following errors every few minutues with my AVM fritz!card PCI: Jul 19 02:50:48 /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error Jul 19 02:50:48 /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error Jul 19 02:50:48 /kernel: i4b-L1-isic_isac_irq: unit 0: Receive Aborted error Jul 19 02:50:48 /kernel: i4b-L1-isic_isac_irq: unit 0: Receive Aborted error Gary Jennejohn wrote about this: "Might be interesting to run isdntrace while the line is idle and see just what the NT is sending to cause this message." And this is what I got with an idle line: =========== isdntrace controller #0 =========== started Wed Jul 19 02:48:51 2000 -- NT->TE - unit:0 - frame:000004 - time:19.07 02:50:18. 73844 - length:8 ------ Dump:000 fe ff 03 0f 00 00 04 ff ........ Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0x0000, IdCheckReq, Ai=127 Jul 19 02:50:48 /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error Jul 19 02:50:48 /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error Jul 19 02:50:48 /kernel: i4b-L1-isic_isac_irq: unit 0: Receive Aborted error Jul 19 02:50:48 /kernel: i4b-L1-isic_isac_irq: unit 0: Receive Aborted error -- NT->TE - unit:0 - frame:000005 - time:19.07 02:53:18.846570 - length:8 ------ Dump:000 fe ff 03 0f 00 00 04 ff ........ Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0x0000, IdCheckReq, Ai=127 Jul 19 02:53:48 /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error Jul 19 02:53:48 /kernel: i4b-L1-isic_isac_irq: unit 0: CRC error Jul 19 02:53:48 /kernel: i4b-L1-isic_isac_irq: unit 0: Receive Aborted error Jul 19 02:53:48 /kernel: i4b-L1-isic_isac_irq: unit 0: Receive Aborted error === So, the following message seems to reflect the cause of the problem. It's also a very non-random error, since the CRC error messages appear -excactly- 30 sec. after the NT->TE message (see trace log above)! -- NT->TE - unit:0 - frame:000006 - time:19.07 02:56:19.619297 - length:8 ------ Dump:000 fe ff 03 0f 00 00 04 ff ........ Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0x0000, IdCheckReq, Ai=127 What could this idCheckReq be? Can it be a harware fault? when I replace all my configuration files with the default ones, I still get the messages, so the problem lies not in there. I also placed the PCI card in a different slot (I dunno why), completely reinstalled FreeBSD (not because of this, though), but still I get these messages after I recompile my kernel with i4b. What can I do? Remember: I do not get these messages when I'm online. It's only with an idle line. If it can't be solved, how can I suppress these kernel messages(if it can be done)? Thanks, Sokon. 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?000001bff177$f1350810$0201a8c0>