Re: MPC5200 + boa webserver + CGI + broken pipe

In message [off-list ref] you wrote:

quoted

This is most probably a hardware issue (bad SDRAM initialization?)

yes, but why does it happen only when we use the boa webserver? when

Probably because this causes a specific load pattern  which  triggers
the problem.

My point is: is it really a bad choice to use boa? can boa really be
causing so much trouble?

No, probably any other application might have caused the same effect.

Is this a Rev. B CPU? Are you using current code? For example, do you
perform the required SDelay initialization (AN3221) ?

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
So we follow our wandering paths, and the very darkness acts  as  our
guide and our doubts serve to reassure us. - Jean-Pierre de Caussade,
eighteenth-century Jesuit priest

On 1/10/07, Wolfgang Denk [off-list ref] wrote:

In message [off-list ref] you wrote:

quoted

quoted

This is most probably a hardware issue (bad SDRAM initialization?)

yes, but why does it happen only when we use the boa webserver? when

Probably because this causes a specific load pattern  which  triggers
the problem.

hmm.. this problem with "broken pipes" only occur when there are too
many concurrent accesses to a CGI script, which communicates to
another application.
but, the system only freezes when we stop and re-start the webserver.
so, could be this CGI script causing all the trouble (by starting and
dying and leaving traces/ perfoming this "load pattern") ?

Is this a Rev. B CPU? Are you using current code? For example, do you
perform the required SDelay initialization (AN3221) ?

no, it's not Rev. B. we wanted to use it but we had some compatibility
problems.


regards

-- 
---
Daniel Martineschen
http://www.inf.ufpr.br/danielm