[asterisk-bugs] [JIRA] (DAHLIN-43) Loading and Configuring wctdm breaks various system commands

[Tzafrir Cohen (JIRA)]

    [ https://issues.asterisk.org/jira/browse/DAHLIN-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202283#comment-202283 ] 

Tzafrir Cohen edited comment on DAHLIN-43 at 1/28/13 8:23 AM:
--------------------------------------------------------------

Just noticed that this is an old issue. I suspect the faulty OSLEC code. If the issue was not reproduced since, maybe close it?
                
      was (Author: tzafrir):
    Just to note that it reminds me of the symptoms of using OSLEC with the faulty floating-point code - part of the code is incorrectly messing with the FPU in interrupt mode.
                  
> Loading and Configuring wctdm breaks various system commands
> ------------------------------------------------------------
>
>                 Key: DAHLIN-43
>                 URL: https://issues.asterisk.org/jira/browse/DAHLIN-43
>             Project: DAHDI-Linux
>          Issue Type: Bug
>          Components: wctdm
>    Affects Versions: 2.0.0-rc5
>            Reporter: andre valentin
>            Severity: Blocker
>         Attachments: dahdi.dmesg.debug100, system.conf
>
>
> Im using asterisk-rc6 with dahdi rc5 (or rc4, does not matter). After loading the wctdm module and configuring the channels with dahdi_cfg varios system commands do stop working. For example, the ssh server responds unpredictable (existing connections close). Also ssh-keygen seems to hang in a loop.
> If remove the channels from system_conf, execute dahdi_cfg and unload the module ssh works fine again.
> I cannot break it down to any special revision, but the last zaptel revision worked.
> ****** ADDITIONAL INFORMATION ******
> Distribution CentOS 5
> Kernel: 2.6.18-92.1.10.el5 #1 SMP
> Dahdi MMX Support: disabled

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira