From: "security" <security@lea-linux.com>
To: Alistair Tonner <Alistair@nerdnet.ca>, netfilter@lists.netfilter.org
Subject: Re: list delete bug: kernel crash
Date: Wed, 1 Sep 2004 00:19:11 +0200 [thread overview]
Message-ID: <007801c48fa8$8a8116d0$0a00a8c0@aziz> (raw)
In-Reply-To: 200408311201.29993.Alistair@nerdnet.ca
>
> I recall having memory problems in the past (about three years ago) ...
> never very fun, and the issue was so fine grained that I ended up having to
> rebuild the box from a zeroed disk. Reading backward I see you are using
> 2.6.8.1 kernel code. Can you check
>
[snip]
I have backup all my data, take my 2 install slackware CDROM, format all my
disk and re-install slackware 10.0.
Now i'm sure:
- My memory is not faulty (10 PASS of memtest86 without error)
- kernel / program are installed / compiled without memory fault
- i have a fresh and good install
No crash since my re install ,in fact i'm still installing, so many things to
do... and as usuall i have forget to backup some files, but it's ok lol :)
So if i got another kernel crash i will post here :)
thanks all to help me :)
next prev parent reply other threads:[~2004-08-31 22:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 14:18 list delete bug: kernel crash 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 [this message]
2004-08-31 19:52 ` Jose Maria Lopez
-- strict thread matches above, loose matches on Subject: below --
2004-08-30 23:34 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
2004-08-31 13:34 ` security
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='007801c48fa8$8a8116d0$0a00a8c0@aziz' \
--to=security@lea-linux.com \
--cc=Alistair@nerdnet.ca \
--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