Date: Fri, 11 Feb 2000 22:13:19 +0100 From: Gary Jennejohn <garyj@peedub.muc.de> To: Andrea Venturoli <ml.ventu@flashnet.it> Cc: freebsd-isdn@FreeBSD.ORG Subject: Re: Elsa QuickStep 1000 pro problems: found more info. Message-ID: <200002112113.WAA17895@peedub.muc.de> In-Reply-To: Your message of "Fri, 11 Feb 2000 18:59:07 EST." <200002111801.TAA31863@mbox01-rm.flashnet.it>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrea Venturoli writes: >Feb 11 15:16:24 ugo /kernel: i4b-L4-i4brbchopen: unit 0, open [snip] >Feb 11 15:16:26 ugo /kernel: i4b-L2-i4b_T202_start: unit 0 Up to here it all looks normal. After this point it starts looking _really_ weird. >Feb 11 15:16:26 ugo /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = >F4 Awaiting Signal <-- what's this ? shouldn't happen, normally [snip] >Feb 11 15:16:26 ugo /kernel: i4b-L4-i4brbchioctl: unit 0, ioctl, unknown cmd 4 >0047477 <-- and this is REALLY strange. [snip] >Feb 11 15:16:26 ugo /kernel: i4b-L1-isic_recover: HSCX B: ISTA = 0x0 >Wait EST, event = EV_T303EXP - T303 timeout! > isic_recover is an emergency error handler, generally as the result of a timeout, which you have. [snip] I assume that you're using PPPoI here (PPPonISDN) ? Because of the rbch, that is. I'd say that your card is set up for the wrong interrupt. The symptoms all point at that. That's why the T303 timeout happens. Or your ISDN cable is shot, or the NTBA is shot, or your card is shot. Most likely is a problem with the interrupt, though. Why those other strange messages appear - I have not the least idea. Is this a fragment from a log with numerous abortive connect attampts ? --- Gary Jennejohn / garyj@muc.de garyj@fkr.cpqcorp.net gj@freebsd.org 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?200002112113.WAA17895>