Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Jul 1999 08:25:19 +0200 (METDST)
From:      hm@hcs.de (Hellmuth Michaelis)
To:        rich@dynamite.org
Cc:        freebsd-isdn@FreeBSD.ORG, brian@Awfulhak.org
Subject:   Re: PPPoISDN
Message-ID:  <m114ITn-0001b7C@hcswork.hcs.de>
In-Reply-To: <B0000040532@clyde.chugaboom.net> from Rich Wood at "Jul 13, 99 09:27:38 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m114ITn-0001b7C>