From: andrew may <acmay@acmay.homeip.net>
To: Dan Kegel <dank@kegel.com>
Cc: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: khttpd crash verified with vanilla linuxppc_2_4_devel
Date: Tue, 21 May 2002 14:16:43 -0700 [thread overview]
Message-ID: <20020521141643.D20012@ecam.san.rr.com> (raw)
In-Reply-To: <3CEAAEFF.3D274083@kegel.com>
On Tue, May 21, 2002 at 01:33:03PM -0700, Dan Kegel wrote:
>
> I can crash khttpd at will on a totally vanilla
> linuxppc_2_4_devel kernel as of changeset 1.749
> using an open source load generator, with or without
> the patch that fixes a khttpd crash on x86
> ( http://www.kegel.com/linux/khttpd/khttpd-unbork.patch ).
>
> This crash is not present on the imac with current kernels, nor
> in Hard Hat 2.0 on this same board, nor on the PC with current kernels.
> I believe it's a bug in the linuxppc_2_4_devel trunk.
What filesystem are you using? RAMfs? Can you try the imac using
the same FS?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-21 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 20:33 khttpd crash verified with vanilla linuxppc_2_4_devel Dan Kegel
2002-05-21 21:16 ` andrew may [this message]
2002-05-21 21:37 ` Dan Kegel
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=20020521141643.D20012@ecam.san.rr.com \
--to=acmay@acmay.homeip.net \
--cc=dank@kegel.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).