ISDN4BSD (HPS version) is going into ports

[Andreas Longwitz]

Hi,

>> First step of analyze is done: I see in the isdntrace that several of
>> the incoming D-channel frames have an extra byte at the end of the frame:
>>        10101110 UNKNOWN single octet IE = 0xae
>> Further I see many single outgoing bytes on L3 level:
>>   L3 04 AE 10101110 Protocol = Other Layer 3 or X.25        (0xae)

I have to correct myself: Further I see many single incoming (not
outgoing) bytes. In the meantime I am convinced that every incoming L2
frame from the card has exactly one superfluos byte at the end.

>> On the other side of the ISDN-line all length are correct. Maybe there
>> is a "one byte length problem" in the D-channel communication between
>> the i4b driver and the card.
> 
> Maybe you can read out the chip numbers? Maybe some of the chips used are 
> documented. Should not be impossible to get this working!

Would be fine! The driver working in FreeBSD 6 gives ifpi2-0: ISACSX
PSB3186, but this is hardcoded in the source. On the chip I can read
"AVM PSB 3100 F".

> Should be easy to compare with the old driver from FreeBSD 6.x.

In the meantime I was able to do a verbose boot. Sounds strange, but
there was a another problem solved by Andriy Gapon:
   lists.freebsd.org/pipermail/freebsd-stable/2012-November/070634.html.

During verbose boot i4b gives for my AVM Fritz!Card version 2 PCI card:

i4b-L1 ihfc1: ihfc_pnp_probe_sub: this unit has 6 transmit and
              receive channels and 1 sub-controllers
i4b-L1 ihfc1: ihfc_alloc_all_resources: Internal IRQ-address: 0x17
ihfc1: Reserved 0x20 bytes for rid 0x10 type 3 at 0xfb145000
i4b-L1 ihfc1: ihfc_fifo_setup_soft: HFC_MAX_FRAMES >= f->fm.h.Fsize
i4b-L1 ihfc1: avm_pci_chip_status_read: status=0x48
i4b-L1 ihfc1: avm_pci_b_status_read: b_status=0x20
i4b-L1 ihfc1: avm_pci_b_status_read: b_status=0x00
i4b-L1 ihfc1: __ihfc_chip_interrupt: del=00000014 ista=0x0000,
     exir=0x0000, h_ista=0x0000, h_exir=0x0000, s_int_s1=0x00
i4b-L1 ihfc1: ihfc_fsm_update: Undefined state:  1!. (p0,a0,c0,u0,d0,i1)
ihfc1: <AVM Fritz!Card version 2 PCI> port 0x54c0-0x54df mem
     0xfb145000-0xfb14501f irq 23 at device 7.0 on pci0
i4b-L1 ihfc1: ihfc_post_setup: Setting up IRQ
ihfc1: [MPSAFE]
ihfc1: [ITHREAD]
ihfc1: Attaching I4B controller 0.
i4b-L1 ihfc1: ihfc_B_get_fifo_translator:
ihfc1: Creating /dev/ihfc0.X.
i4b-L1 ihfc1: avm_pci_chip_status_read: status=0x49
i4b-L1 ihfc1: avm_pci_chip_status_read: ista=0x11
i4b-L1 ihfc1: avm_pci_chip_status_read: ista_d=0x90
i4b-L1 ihfc1: ihfc_fsm_update: Activate indication (priority=8/9).
     (p0,a1,c1,u0,d0,i0)
i4b-L1 ihfc1: fsm_write: Start activation, cmd[0]=0x20
i4b-L1 ihfc1: avm_pci_b_status_read: b_status=0x00
i4b-L1 ihfc1: avm_pci_b_status_read: b_status=0x00
i4b-L1 ihfc1: __ihfc_chip_interrupt: del=00000010 ista=0x0000,
      exir=0x0000, h_ista=0x0000, h_exir=0x0000, s_int_s1=0x00

Maybe the "Undefined state" message in ihfc_fsm_update gives a hint ?

P.S.
With bootverbose in function ihfc_pnp_probe_sub() the debugbit
L1_HFC_DBG is set producing very very lot of messages and the system
comes to complete congestion, therefore after a few minutes my watchdog
triggers, If you think this not ok, then I can give more details. At the
moment I avoid this problem reliable with "isdndebug -d" as soon as
userland gets control after verbose boot.


-- 
Andreas Longwitz