[Asterisk-Users] Updated Zaptel this morning and *BOOM* *CRASH*

[Troy Settle]

> -----Original Message-----
> From: Troy Settle
> Sent: Monday, May 31, 2004 6:49 AM
> 
> First time around, I just unloaded/reloaded the modules.  The 
> box locked up tight.  On reboot, I get this:
> 
> general protection fault: 0000
> CPU:    0
> EIP:    0010:[<c01defb3>]    Not tainted
> EFLAGS: 00010097
> eax: f61d4260   ebx: f61d4260   ecx: ffffffff   edx: f61d425f
> esi: f61d4264   edi: f61d4260   ebp: f4de7f14   esp: f4de7ef4
> ds: 0018   es: 0018   ss: 0018
> Process sh (pid: 387, stackpage=f4de7000)
> Stack: 00000297 00000001 00000001 00000086 00000001 f61d411c 00000202
> f61d4008 
>        00000004 f897ebaf 00000001 00000000 00000001 f897eccf f61d411c
> 00000004 
>        00000008 f61d4008 f6551680 00000000 00000000 f61d4008 f61d4000
> 00000000 
> Call Trace:    [<f897ebaf>] [<f897eccf>] [<f89c7852>] [<c01d0349>]
> [<c01d0568>]
>   [<c01d2fa8>]
> 
> Code: 8b 01 85 45 f0 75 1c 8b 02 89 d3 89 c2 0f 18 00 39 f3 75 e9 
>  <0>Kernel panic: Aiee, killing interrupt handler!
> 
> 
> BTW, this is kernel 2.4.25-gentoo-r2
> 

Oops... Missed one step.  It's not locking up until a few moments (less than
a second?) after running ztcfg.


> --
>   Troy Settle
>   Pulaski Networks
>   http://www.psknet.com
>   866.477.5638
>