atom feed4 messages in org.freebsd.freebsd-isdnRe: CRC error / Receive Aborted error
FromSent OnAttachments
Hellmuth MichaelisNov 10, 2000 7:45 am 
Poul-Henning KampNov 10, 2000 7:46 am 
Hellmuth MichaelisNov 10, 2000 7:54 am 
Clem DyeNov 12, 2000 7:14 am 
Subject:Re: CRC error / Receive Aborted error
From:Clem Dye (cl@bastet.com)
Date:Nov 12, 2000 7:14:34 am
List:org.freebsd.freebsd-isdn

From a personal viewpoint I belive that it's always better to have too much rather than too little info. I'm in the process of gathering kit right now to permit me to use FreeBSD as an ISDN router. Given that I'm totally new to this, anything and everything may be of help.

Having not seen the problem first hand (yet) I can't comment properly on the issue per se, but couldn't the messages go to stderr or an [exception] log file of some sort, or perhaps be user-controllable with a switch?

Clem

Hellmuth Michaelis wrote:

From the keyboard of Poul-Henning Kamp:

The errors occur at the time where the exchange shuts down layer 1. I have tried to find out if there is a bug in the ISAC handling code, but i could not find one. All seems to work ok.

Based on what i see, the only conclusion i can draw from this is that the above mentioned errors occuring while shutting down the layer 1 can not be avoided.

Right, but shouldn't we stop printf'ing them all the time then ?

I don't like to disable them in general, because its a very good hardware setup "debugging" aid.

I thought about if it is possible to check that the bus is in an "about to be deactivated" condition and if yes, prevent printing the messages out.

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 majo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message

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