ISDN4BSD (HPS version) is going into ports

[Hans Petter Selasky]

On Monday 16 July 2012 12:48:24 Andreas Longwitz wrote:
> Hi Hans
> 
> > If you can collect the backtrace from these crashes, that would be nice.
> 
> Three examples of backtraces follow, the others are similar. I use
> minidumps and ddb with the line
>    script kdb.enter.default=watchdog; call doadump; reset
> in ddb.conf.
> 
> 1. example: Default options + SPPP + RBCH, crash on kldload i4b, test PC
> without isdn hardware:
> 
> kgdb /boot/kernel/kernel vmcore.3
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, ....
> ...

Hi Andreas,

I cannot reproduce this crash over here. I think it is not a bug in I4B, but rather
some hardware generating spurious interrupts when probing! Loading I4B will cause a
re-probe of existing devices with no driver attached.


              ┌────────────────────────────────────────────────────────────────────┐
              │ Options for isdn4bsd-kmod 2.0.3                                    │  
              │ ┌────────────────────────────────────────────────────────────────┐ │  
              │ │         [ ] DEBUG    Build with debugging support              │ │  
              │ │         [*] HFC      Build HFC-XXX driver                      │ │  
              │ │         [ ] ING      Build ING driver                          │ │  
              │ │         [ ] IPR      Build IPR driver                          │ │  
              │ │         [ ] IPR_VJ   Build IPR driver with VJ support          │ │  
              │ │         [ ] LOOP     Build loopback test driver                │ │  
              │ │         [*] MAN      Intall manual pages                       │ │  
              │ │         [*] RBCH     Build RBCH driver                         │ │  
              │ │         [*] SPPP     Build SPPP driver                         │ │  
              │ │         [ ] TEL      Build TEL driver                          │ │  
              │ │         [*] TRACE    Build TRACE driver                        │ │  
              │ │         [*] YEALINK  Build YEALINK driver                      │ │  
              │ │                                                                │ │  
              │ │                                                                │ │  
              │ └────────────────────────────────────────────────────────────────┘ │  
              ├────────────────────────────────────────────────────────────────────┤  
              │                   <  OK  >          <Cancel>                       │  
              └────────────────────────────────────────────────────────────────────┘  
                                                                                      

kldload i4b

i4b: ISDN call control device attached
capi: CAPI call control device attached, v2.11
i4bisppp: 8 ISDN SyncPPP device(s) attached
i4bctl: ISDN system control port attached
i4brbch: 8 raw B channel access device(s) attached
i4btrc: 64 ISDN trace device(s) attached

> 
> Is that what you expect ? I would expect a line
>   interface yealink.1
> but probably I am wrong.

The I4B module as a whole cannot be unloaded, it requires a reboot. Some parts of I4B supports unload, but others not.
A crash at this point is like expected. However it is possible in theory to split I4B into separate modules,
which can be loaded/unloaded, but not the core itself currently.

> 
> > I believe the SPPP functionality has not been tested for a while. I'm
> > currently using I4B mostly for voice.
> 

Thanks for testing!

--HPS