[asterisk-bugs] [JIRA] (ZAP-366) Wildcard TE820 and Wildcard TE420 issue

[Serghei (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ZAP-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Serghei updated ZAP-366:
------------------------

    Description: 
I have one server (HP ProLiant for 380p G8, OS Ubuntu 12.04.3 LTS, 3.13.1-031301 kernel-generic) with 2 Digium cards- Wildcard TE820 (DM21140600051) and Wildcard TE420.
The problem appears after 1 or 2 days: Wildcard TE820 "dahdi shows status"  shows red alarm. Manually restarting the DAHDI drivers doesn't fix the problem (the red light is still there). The problem is fixed only after rebooting the server.
You can see system logs  and /proc/interrupts in attached files. 
Please help me to resolve this issue


  was:
I have one server (HP ProLiant for 380p G8, OS Ubuntu 12.04.3 LTS, 3.13.1-031301 kernel-generic) with 2 Digium cards- Wildcard TE820 (DM21140600051) and Wildcard TE420.
The problem appears after 1 or 2 days: Wildcard TE820 "dahdi shows status"  shows red alarm. Manually restarting the DAHDI drivers doesn't fix the problem (the red light is still there). The problem is fixed only after rebooting the server.



> Wildcard TE820 and Wildcard TE420 issue
> ---------------------------------------
>
>                 Key: ZAP-366
>                 URL: https://issues.asterisk.org/jira/browse/ZAP-366
>             Project: Zaptel
>          Issue Type: Task
>      Security Level: None
>          Components: wct4xxp
>            Reporter: Serghei
>            Assignee: Russ Meyerriecks
>         Attachments: interrupts.txt, syslog.log
>
>
> I have one server (HP ProLiant for 380p G8, OS Ubuntu 12.04.3 LTS, 3.13.1-031301 kernel-generic) with 2 Digium cards- Wildcard TE820 (DM21140600051) and Wildcard TE420.
> The problem appears after 1 or 2 days: Wildcard TE820 "dahdi shows status"  shows red alarm. Manually restarting the DAHDI drivers doesn't fix the problem (the red light is still there). The problem is fixed only after rebooting the server.
> You can see system logs  and /proc/interrupts in attached files. 
> Please help me to resolve this issue



--
This message was sent by Atlassian JIRA
(v6.2#6252)