linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Daniel Martineschen" <martineschen@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC5200 + boa webserver + CGI + broken pipe
Date: Thu, 11 Jan 2007 02:15:30 +0100	[thread overview]
Message-ID: <20070111011530.8091635264F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 10 Jan 2007 09:07:29 -0200." <3acfce80701100307o18a24b37q616bb0c8ec4086dd@mail.gmail.com>

In message <3acfce80701100307o18a24b37q616bb0c8ec4086dd@mail.gmail.com> you wrote:
>
> > 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

  reply	other threads:[~2007-01-11  1:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09 18:01 MPC5200 + boa webserver + CGI + broken pipe Daniel Martineschen
2007-01-10  0:54 ` Wolfgang Denk
2007-01-10 11:07   ` Daniel Martineschen
2007-01-11  1:15     ` Wolfgang Denk [this message]
2007-01-11 17:58       ` Daniel Martineschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070111011530.8091635264F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=martineschen@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).