From: Willy Tarreau <w@1wt.eu>
To: Viswanathan Murugesan <viswa.murugesan@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Question on 2.6.25 kernel crash.
Date: Wed, 21 Apr 2010 07:07:49 +0200 [thread overview]
Message-ID: <20100421050749.GC7798@1wt.eu> (raw)
In-Reply-To: <n2pfe58d3641004201821r3805616id4a8cd5cdb745b46@mail.gmail.com>
On Tue, Apr 20, 2010 at 06:21:08PM -0700, Viswanathan Murugesan wrote:
> 2.6.25 Kernel crashes when tried to upload a 2 MB file through FTP to
> a ftp server under a ipsec gateway.
Your logs are showing 2.6.25.7, which is two years old and not up to
date at all. 2.6.25 is not maintained anymore, but at least you should
have updated to 2.6.25.20 at that time. You basically missed 13 updates
on this version, so it is possible that your problem was identified and
fixed. Anyway, since it's not maintained anymore, you should probably
retry with 2.6.32.X which is going to be maintained for a long time.
Willy
prev parent reply other threads:[~2010-04-21 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <j2pfe58d3641004201748uadddaf12n1cfec0c0bb98117c@mail.gmail.com>
2010-04-21 1:21 ` Question on 2.6.25 kernel crash Viswanathan Murugesan
2010-04-21 5:07 ` Willy Tarreau [this message]
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=20100421050749.GC7798@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=viswa.murugesan@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