Summary: | ASTERISK-06451: Complete system freeze caused, I believe, by chan_misdn. | ||
Reporter: | richardp (richardp) | Labels: | |
Date Opened: | 2006-03-01 21:53:22.000-0600 | Date Closed: | 2006-03-02 13:10:37.000-0600 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_misdn |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) crash.txt | |
Description: | The system will suddenly stop responding to all user input. No mouse, keyboard response and no call processing. This occurs infrequently but about 2/3 times a day on average. Looking at the messages log before each reboot (shown in the included file) led me to believe that this was due to a problem unloading calls from the ISDN connection (mISDN). These are the problems reported; HFC-S USB: CRC or minlen ERROR channel_senddata: next_skb exist ERROR (skb->len=64 next_skb->len=64) though these aren't always present, on other occasions the last line recoreded before reboot is; release instance class dev inst-50010201 ****** ADDITIONAL INFORMATION ****** Originally the system was built on the 19th of Feb. This would mean that the SVN of mISDN was the 16th Feb version, however, I recomplied the channel drivers (including misdn) lastnight (12noon GMT on the 1st of March). This issue has persisted. | ||
Comments: | By: crich (crich) 2006-03-02 02:42:56.000-0600 I'd like you to post that issue on the mISDN bugtracker at: www.isdn4linux.de/mantis since the developers of the hfcsusb driver are reading this bugtracker only i think. Do you get a Kernel Oops? Can you make a digital photo of it and attach it to the bugreport please. chan_misdn cannot cause the system to freeze. It is only a userspace programm. It is mISDN which freezes the system. Thanks! |