Summary:	ASTERISK-00133: wct1xxp + wcfxs + ZAPATA_NET creates crashes/instability
Reporter:	ulexus (ulexus)	Labels:
Date Opened:	2003-08-20 11:44:36	Date Closed:	2004-09-25 02:52:04
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	If you compile the wct1xxp module with both -DCONFIG_ZAPATA_NET and -DCONFIG_ZAPATA_PPP, the kernel throws  "random" memory allocation error Oops's under moderate load. Sometimes, the system will spontaneously reboot as a result. Choosing _either_ ZAPATA_NET  or  ZAPATA_PPP singly works fine. Notably, this does not affect tor2.
Comments:	By: Mark Spencer (markster) 2003-08-20 14:46:32 Does it depend upon you using one or the other of the features? By: ulexus (ulexus) 2003-08-20 15:26:49 No.  As long as I have run loaded the modules and run ztcfg, it will cause the spurious errors. It will run just the same if you have hdlc0 up and running or completely unconfigured. The errors, also, are not related to the card functions.  For instance, I can always get the kernel to burp simply by compiling a reasonably large program, if I have those modules loaded. The system basically behaves like it has bad RAM.  I have tried this on two different systems with exactly the same results.  Both systems run stably when I turn off one of the two defines. By: Mark Spencer (markster) 2003-08-20 17:59:36 Can you show me what your config looks like in zaptel.conf? By: ulexus (ulexus) 2003-08-21 13:25:15 # cat /etc/zaptel.conf |grep -v ^# span=1,0,0,esf,b8zs e&m=1-4 nethdlc=5-24 fxoks=25 fxoks=27-28 loadzone = us defaultzone=us By: ulexus (ulexus) 2003-09-29 19:41:14 Corrected bug parameters: This bug ONLY occurs when wct1xxp AND wcfxs AND -DCONFIG_ZAPATA_NET Unlike original definition, this bug DOES STILL occur with only the -DCONFIG_ZAPATA_NET defined. Further notes: This bug does not occur if I do not load the wcfxs module.  I don't understand this at all, since there is no networking code in the wcfxs module that I see.  It is definitely linked to the network code, however.  If I compile both modules without -DCONFIG_ZAPATA_NET, everything is stable. Worse, if I swap out the T100P for a T400P, with no other changes, the system is stable.  If I swap out for a different T100P or a different TDM400P, the system still crashes. Hence, I figure it must be some sort of memory space that both T100P and TDM400P use when ZAPATA_NET is defined and may spill over into the main memory...? This is just bizarre.  No card is sharing an interrupt with anything else. This bug is still present in the latest CVS (as of 09/29/2003 16:00) By: ulexus (ulexus) 2003-09-29 20:01:47 I just noticed that, in light of the updated notes, the title of this bug is now wrong.  Should I open a new bug and copy the information, or can you change the title to more accurately reflect the problem? "wct1xxp + wcfxs + ZAPATA_NET = system instability and oopses", perhaps? By: ulexus (ulexus) 2003-10-31 18:29:40.000-0600 Okay.  The new TDM400P's (and CVS update) fixed this bug.  I was confused for a while with another, similar but ultimately unrelated issue.\ This bug can be closed as resolved.