[asterisk-users] Trying to understand mISDN kernel buffer messages...

[Ex Vitorino]

  Hello List,

  I have got some questions about mISDN kernel buffer messages
  which I posted to the mISDN users list a while ago.

  Unfortunatelly I received no feedback at all, so I though I'd share them
  in this (wider) context to see if anyone can give any input...

  Thanks in advance for any feedback and kind regards,
--
  Ex Vito

---------- Forwarded message ----------
From: Ex Vitorino <ex.vitorino at gmail.com>
Date: Jan 2, 2007 1:22 PM
Subject: Trying to understand kernel buffer messages...
To: misdn-asterisk at lists.beronet.com


  Hello list,

  I've been successfully running an Asterisk 1.2.14 + bundled chan_misdn +
  mISDN 1.0.4 + mISDNuser 1.0.3 + beroNet 4 port BRI card solution for
  about two weeks.

  It's running on top of Ubuntu Server 6.06 LTS, kernel 2.6.15-26-server and
  everything installed, to my knowledge, without a hitch.

  After this period, the kernel buffer is holding several different
mISDN related
  messages which I'd like to fully understand. Can anyone shed some light,
  please ?


  1. These show up on boot

        Modular ISDN Stack core $Revision: 1.37 $
        mISDNd: kernel daemon started (current:f7e53a90)
        mISDNd: test event done
        mISDN_isac: disagrees about version of symbol mISDN_debugprint
        mISDN_isac: Unknown symbol mISDN_debugprint
        netjetpci: Unknown symbol mISDN_isac_free
        netjetpci: Unknown symbol mISDN_isac_interrupt
        netjetpci: Unknown symbol mISDN_clear_isac
        netjetpci: Unknown symbol mISDN_isac_init
        netjetpci: Unknown symbol mISDN_ISAC_l1hw

  ...something about mISDN_isac and netjetpci does not seem right; neither
  of the modules is currently loaded.


  2. MISDN free_device: entitylist not empty

        Does this indicate some cleaning up did no go as it should ? They seem
        to appear everytime Asterisk is restarted (not shure if on
shutdown or on
        startup!)


  3.  ie not handled ie [76] l [b]

        I've got 7 of these: all of them have the [76], two have [b],
two have [2]
        and three have [5]...

        I can't associate any of them to a particular Asterisk log event but,
        honestly, this seems to indicate something did not go as planned ! :-(


  4.  Found ie in set which we do not support ie [27]

        Once. Right after one of the previous messages "ie not handled
ie [76] l [2]".
        Again, what went wrong here ?


  5. These ones seem related and show up in pairs, like:

        mISDN_FsmAddTimer: timer already active!
        lapd 1 mISDN_FsmAddTimer already active!

        ...or...

        mISDN_FsmAddTimer: timer already active!
        lapd 2 mISDN_FsmAddTimer already active!

        I've got 4 of these pairs... None of them show up on times which can
        be related to any specific Asterisk activity.


  6. Last, but not least, this one...

        DSS1 1 mISDN dss1 sending RELEASE_COMPLETE without proc
pr=35a80 dinof(90001)

        ...which I already know shows up after every call. The question: does it
        make any sense to fill the kernel message buffer with them ?
Shouldn't they
        rather be sent to a log file only, and only if activated ?


  I'd like to thank everyone in advance for any help or pointers they can
  provide. The objective is simple: have a good understanding of what
  is going on, so as to keep the system running as smoothly as possible.

  Kind regards and Happy New Year,
--
  Ex Vito