From owner-freebsd-isdn Tue Jul 13 23:27: 0 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with SMTP id 4A50614D2C for ; Tue, 13 Jul 1999 23:26:42 -0700 (PDT) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (4866 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Wed, 14 Jul 1999 08:25:26 +0200 (CEST) (Smail-3.2.0.104 1998-Nov-20 #1 built 1998-Dec-11) Received: by hcswork.hcs.de (Smail3.1.29.0 #13) id m114ITn-0001b7C; Wed, 14 Jul 99 08:25 METDST Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: PPPoISDN In-Reply-To: from Rich Wood at "Jul 13, 99 09:27:38 pm" To: rich@dynamite.org Date: Wed, 14 Jul 1999 08:25:19 +0200 (METDST) Cc: freebsd-isdn@FreeBSD.ORG, brian@Awfulhak.org Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 4036 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Rich Wood: > Jul 13 21:20:12 zippy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, > state = F4 Awaiting Signal > Jul 13 21:20:14 zippy /kernel: i4b-L1-timer3_expired: state = F4 Awaiting > Signal > Jul 13 21:20:14 zippy /kernel: i4b-L1-isic_recover: HSCX B: ISTA = 0x0 > Jul 13 21:20:14 zippy /kernel: i4b-L1-isic_recover: ISAC: ISTA = 0x1 > Jul 13 21:20:14 zippy /kernel: i4b-L1-isic_recover: ISAC: EXIR = 0x10 > Jul 13 21:20:14 zippy /kernel: i4b-L1-isic_recover: HSCX B: IMASK = 0xff > Jul 13 21:20:14 zippy /kernel: i4b-L1-isic_recover: HSCX A: IMASK = 0xf8 > Jul 13 21:20:14 zippy /kernel: i4b-L1-isic_recover: ISAC: IMASK = 0x2a > Jul 13 21:20:14 zippy /kernel: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 > Jul 13 21:20:14 zippy /kernel: i4b-L1-ph_data_req: still in state F3! > Jul 13 21:20:14 zippy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, > state = F4 Awaiting Signal > Jul 13 21:20:16 zippy /kernel: i4b-L3-T303_timeout: SETUP not answered, cr > = 35 > Jul 13 21:20:16 zippy /kernel: i4b-L3-next_l3state: FSM illegal state, > state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! What you are seeing is the result of an interrupt from the card not being delivered to the interrupt handler. This can have many reasons, the most likely are problems with the IRQ routing settings in the BIOS for that particular IRQ you are using or hardware. There is a long entry in the i4b FAQ about how other people solved the BIOS setting problem. For the hardware (and it was a Teles S0/8 in a particular piece of PC brand hardware) problems i once posted a short article here, which went like this: A short story on PC Hardware or HELP, my ISDN card does not work! ----------------------------------------------------------------- FYI and before i forget about that: recently i bought one of those cheap soundcards to plug it in one of my machines. This machine is a usual machine of a well known manufacturer and is equipped with a PCI and an ISA bus, on the ISA bus was a working Teles ISDN card and everything else was fine. After installing the sound card and configuring its driver it worked almost immediately. But ISDN stopped working, some of you know the symptoms ... /kernel: i4b-L1-timer3_expired: state = F4 Awaiting Signal /kernel: i4b-L1-isic_recover: HSCX B: ISTA = 0x0 /kernel: i4b-L1-isic_recover: ISAC: ISTA = 0x94 /kernel: i4b-L1-isic_recover: ISAC: CISQ = 0x52 /kernel: i4b-L1-isic_recover: HSCX B: IMASK = 0xff /kernel: i4b-L1-isic_recover: HSCX A: IMASK = 0xf8 /kernel: i4b-L1-isic_recover: ISAC: IMASK = 0x2a /kernel: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 /kernel: i4b-L1-ph_data_req: still in state F3! /kernel: i4b-L3-T303_timeout: SETUP not answered, cr = 43 /kernel: i4b-L3-next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! ... and you all know by now that this is the IRQ not being delivered to or recognized by the interrupt handler. Removed the soundcard, ISDN worked. Plugged in the soundcard, ISDN does not work anymore. Checked memory ranges, i/o ranges, IRQ etc. etc.: nothing all was fine. I became desparate ("this s**t PC crap hardware design !$'%&//!"). What i then did was disabling the IRQ ISA connector PCB trace on the soundcards ISA connector, the ISDN card is or wanted to use (i didn't want to cut the PCB trace with a knife, so i used a bit of adhesive tape to insulate it). And, voila, since then i again have a working ISDN card (and a soundcard) in that machine. Bottom line: a driver can only run if the hardware allows it to run. hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 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