Summary: | ASTERISK-09621: Zaptel 1.4.2.1 Init scripts cause a kernel panic | ||
Reporter: | Peter Zieba (pzieba) | Labels: | |
Date Opened: | 2007-06-07 19:12:18 | Date Closed: | 2007-06-08 13:30:44 |
Priority: | Critical | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | make config was used to generate the init scripts. Upon running /etc/init.d/zaptel stop, console quickly fills with output. "Not prepped yet!" Scrolls wildly up the screen. Is then followed by a kernel panic and the following line: "irq 225: nobody cared (try booting with the "irqpoll" option)" This information is only available from the console itself, and so I cannot copy and paste. I do have actual screenshots taken with a digital camera, back to back, which I will adding to this ticket. ****** ADDITIONAL INFORMATION ****** Kernel: 2.6.18-8.1.4.el5 CentOS 5.0. Occured in CentOS 4.4 as well, if I remember correctly. Dell Poweredge 1850 and 2850 both have identical problem. This will either produce lots of output, or actually hard-lock the machine. | ||
Comments: | By: Peter Zieba (pzieba) 2007-06-07 19:14:07 Can provide console access to this machine, if desired, as it is only a test server. Screenshots of the crash will actually be from a similarly configured machine. By: Russell Bryant (russell) 2007-06-07 23:33:28 This should already be fixed in the latest 1.2 svn. We will be making a new release very shortly but you can grab the code from there. If it's not fixed, please let us know. By: Peter Zieba (pzieba) 2007-06-08 13:22:59 Alrighty -- I did have a few quick questions, however. Will this be fixed in 1.4 as well? As per the ticket I opened, I'm not actually using 1.2. Does 1.2.X Zaptel Work with Asterisk 1.4.X?? Is there a related / duplicate ticket that discusses this problem? I'm curious as to what went wrong -- I've never had a problem with Zaptel before. Appreciate the information. Thanks! By: Russell Bryant (russell) 2007-06-08 13:30:43 Yes, it should be fixed in 1.4 as well. i don't know why I only said 1.2. |