From: Dan Malek <dan@mvista.com>
To: Bryan Rittmeyer <bryan@ixiacom.com>
Cc: linuxppc-embedded@lists.linuxppc.org, akuster@mvista.com
Subject: Re: http_load causes 405GP kernel panic w/ linux_2_4_devel
Date: Thu, 25 Oct 2001 00:10:11 -0400 [thread overview]
Message-ID: <3BD790A3.D4AF4852@mvista.com> (raw)
In-Reply-To: 3BD77667.2060406@ixiacom.com
Bryan Rittmeyer wrote:
> Looks like linux_2_4_devel is very unstable under high TCP/IP loads
> and low amounts of memory on the Walnut.
Yeah, that's why it's called a _development_ tree. If you want to
play around here, the purpose is for you to help us fix the bugs.
When you find a solution, post a patch and we'll all take a look
at it. If you are willing to help out, that's great, but we all have
plenty to do so just expecting someone else to look at it and fix
it for you isn't going to be very satisfying :-).
Thanks.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-25 4:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 2:18 http_load causes 405GP kernel panic w/ linux_2_4_devel Bryan Rittmeyer
2001-10-25 4:10 ` Dan Malek [this message]
2001-10-29 22:19 ` Bryan Rittmeyer
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=3BD790A3.D4AF4852@mvista.com \
--to=dan@mvista.com \
--cc=akuster@mvista.com \
--cc=bryan@ixiacom.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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).