|Summary:||ASTERISK-00828: [tracking] e1000 network card causes kernel panic when used with TE410P and possibly other Zaptel devices.|
|Date Opened:||2004-01-13 21:47:07.000-0600||Date Closed:||2004-09-25 02:55:30|
|Description:||jerjer and anthm have noted kernel panics using the e1000|
with zaptel hardware, including the TE410P. This seems to be an issue with the e1000 and not with the Zaptel device.
|Comments:||By: jerjer (jerjer) 2004-01-14 00:15:34.000-0600|
The only time I have ever encountered this is when using IAX/IAX2 and MeetMe.
By: zoa (zoa) 2004-01-14 03:31:40.000-0600
i also have e1000 networkcards in my server and also see kernel panic every now and then.
But all my servers have e1000 networkcards so i can't really tell if its better without.
Any known workarounds, its a bit a pitty to replace the integrated networkcards with pci networkcards ?
By: zoa (zoa) 2004-01-14 03:32:50.000-0600
oh i never did meetme on some of those servers, so that doesnt seem to be related.
By: sbisker (sbisker) 2004-01-31 15:38:22.000-0600
I have e1000 on a dual Xeon server. Two T400P cards and a megaraid controller. Zaptel is compiled for SMP. And I get a kernel panic every 24-36 hours. I am running RedHat 2.4.20-28.8smp kernel on RedHat 8. IAX2 is enabled, but it doesn't seem to be happening with IAX. The last console message I see is attempting to bridge Zap/xxx and Zap/xxx.
By: Paul Cadach (pcadach) 2004-02-07 23:51:58.000-0600
Looks like troubles in meetme-related code in zaptel module. Check notes on ASTERISK-957... I have dual-Xeon server with asterisk and e1000 with installed TE410P (but not configured and not connected to PSTN) WITHOUT meetme - works fine.
By: zoa (zoa) 2004-02-08 07:15:14.000-0600
i have several dual xeons with e1000's and zaptel hardware, it doesnt kernel panic all that often, (didnt happen in the last 2 months)
I rarely use meetme
By: Brian West (bkw918) 2004-02-11 23:27:22.000-0600
its meetme related when mixing zap with voip(ie sip/iax) that the problem comes up. If you dont use meetme you won't see the problem.
By: Mark Spencer (markster) 2004-02-27 11:51:58.000-0600
This should be fixed in CVS as of at least a few weeks ago. Can we confirm it's fixed and close out this bug?
By: zoa (zoa) 2004-02-27 13:00:32.000-0600
i havent seen this for a while...
If it happens again, ask a bugmarshall to reopen the bug.