From: Gavin Hamill <gdh@acentral.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: list delete bug: kernel crash
Date: Tue, 31 Aug 2004 14:24:54 +0100 [thread overview]
Message-ID: <200408311424.54003.gdh@acentral.co.uk> (raw)
In-Reply-To: <000a01c48f5c$e8560050$0a00a8c0@aziz>
On Tuesday 31 August 2004 14:17, security wrote:
> Hum still have crash. I have test again my memory, made 10 pass with
> memtest86 without error found.
This may be a long shot, but there may exist the possibility of the files on
disk being corrupted when they were installed, due to your faulty memory?
Try to reinstall the kernel / modules and iptables userspace?
Cheers,
Gavin.
next prev parent reply other threads:[~2004-08-31 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 23:34 list delete bug: kernel crash security
2004-08-31 10:50 ` KOVACS Krisztian
2004-08-31 11:39 ` security
2004-08-31 13:17 ` security
2004-08-31 13:24 ` Gavin Hamill [this message]
2004-08-31 13:34 ` security
-- strict thread matches above, loose matches on Subject: below --
2004-08-31 14:18 security
2004-08-31 15:05 ` Gavin Hamill
2004-08-31 15:32 ` security
2004-08-31 16:01 ` Alistair Tonner
2004-08-31 22:19 ` security
2004-08-31 19:52 ` Jose Maria Lopez
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=200408311424.54003.gdh@acentral.co.uk \
--to=gdh@acentral.co.uk \
--cc=netfilter@lists.netfilter.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