From: Willy Tarreau <w@1wt.eu>
To: morrowc+kernel@ops-netman.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: crashes of 2.4.31 kernel (oops included)
Date: Mon, 26 Jun 2006 22:01:20 +0200 [thread overview]
Message-ID: <20060626200120.GK13255@w.ods.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0606260544000.10457@arb-h2.bcf-argzna.arg>
Hello,
On Mon, Jun 26, 2006 at 05:52:37AM +0000, morrowc+kernel@ops-netman.net wrote:
> >From URL - http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html
>
> [1.] One line summary of the problem: kernel panic/oops system hangs
> [2.] Full description of the problem/report:
> After some random period of time (from 1 hour to several days) kernel
> receives an 'oops' and dies. Requires power cycle to recover. I've a few
> of the 'oops' output saved and converted with ksymoops if required
> (included one below) Error appear to be in the iptables
> connection_tracking actually.
>
> [3.] Keywords (i.e., modules, networking, kernel):
> networking kernel oops
> [4.] Kernel version (from /proc/version):
> Linux version 2.4.31 (root@neo-u2.ops-netman.net) (gcc version 3.3.5
> (Debian 1:3.3.5-13)) #1 SMP Sun Mar 12 15:09:22 GMT 2006
Many bugs have been fixed in netfilter code since 2.4.31, you should
really upgrade, either to 2.4.33-rc2, or to 2.4.31-hf32.6 which contains
adds to 2.4.31 all relevant fixes till two weeks ago. You can find it
here : http://linux.exosec.net/kernel/2.4-hf/
If the problem is new, it can indicate a hardware problem, or someone
succeeding in exploiting one of those old bugs.
Regards,
Willy
next prev parent reply other threads:[~2006-06-26 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 5:52 morrowc+kernel
2006-06-26 20:01 ` Willy Tarreau [this message]
2006-06-27 0:15 ` Chris Morrow
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=20060626200120.GK13255@w.ods.org \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=morrowc+kernel@ops-netman.net \
/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
all inboxes | Powered by JetHome®