Summary:	ASTERISK-00974: kernel panic crash freeze caused either by manager or meetme
Reporter:	Matt Florell (mflorell)	Labels:
Date Opened:	2004-02-02 09:00:46.000-0600	Date Closed:	2004-09-25 02:56:59
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I have been testing a new meetme-intensive system for the the last two weeks. The problem that occurs is that I will have about a dozen SIP calls and a dozen zap calls going into a dozen separate meetme conferences and after about an hour the system kernel panics. the calltrace on the console is usually different but it is always zaptel that is listed in brackets: - io_transmit [zaptel] - send [zaptel] Those are ones that frequently appear. I have been able to reproduce this kernel panic on 3 separate machines all running different CVS versions. When I stop using the meetme-based application, the kernel panics stop as well. The 3 machines are: machine 1: - P4 2.6GHz HT / 2BG RAM / SCSI RAID - 3com net card - Digium T400P with 4 T1s (E&M wink) - Redhat 9.0 - Asterisk CVS 2004-01-12 machine 2: - P4 2.6GHz HT / 2BG RAM / SCSI RAID - 3com net card - Digium T400P with 3 T1s (E&M wink) - Redhat 9.0 - Asterisk CVS 2004-01-13 machine 3: - dual Athlon MP 2800+ /2GB RAM / SCSI RAID - 3com ethernet on MoBo - digium T410p - Redhat 9.0 - Asterisk CVS 2004-01-25
Comments:	By: Brian West (bkw918) 2004-02-02 11:09:58.000-0600 Happen to have an e1000 gige card in these boxes? By: Brian West (bkw918) 2004-02-02 11:20:49.000-0600 Related to 963 please continue discussion there.