From: "Jacky Liu" <jq419@my-deja.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.4 kernel freeze for unknown reason
Date: Wed, 9 May 2001 20:57:01 -0700 [thread overview]
Message-ID: <200105100357.UAA16327@mail25.bigmailbox.com> (raw)
Dear All,
I would like to post a question regarding to a problem of unknown freeze of my linux firewall/gateway.
Here is the hardware configuration of my machine:
AMD K-6 233 MHz
2theMax P-55 VP3 mobo
64Mb RAM in a single module (PC-100)
Maxtor 6G UDMA-33 harddisk
Matrox MG-II display card w/8Mb RAM
3Com 3C905B-TX NIC
RealTek 8129 10/100 NIC
It's running 2.4.4 kernel (RedHat 7.1) and acting as a firewall using Netfilter (gShield and Snort), DNS (Cache-Only DNS) and NAT gateway (ip-masq.) for my home network. I used 3C905B-TX NIC as my internal NIC and RealTek 8129 as my external NIC. Here is the problem:
The machine has been randomly lockup (totally freeze) for number of times without any traceable clue or error message. Usually the time frame between each lockup is between 24 to 72 hours. The screen just freeze when it's lockup (either in Console or X) and no "kernel panic" type or any error message prompt up. All services (SSH, DNS, etc..) are dead when it's lockup and I cannot find any useful information in /var/log/messages. I cannot reproduce the lockup since it's totally randomly. The lockup happened either when I was playing online game (A LOT, like getting thousands of server status in counter-strike in a very short time frame, of NAT traffic), surfing the web (normal traffic) or the machine was totally in idle (lockup when I was sleeping). It was lockup this morning when I was playing online game (when my game machine was trying to establish connection to a game server).
If there is any information you would like to obtain, please let me know. I would like to receive a copy of your reply, thank you very much for your kindly attention.
Best Regards,
Jacky Liu
"Genius or Wacko? Majority or Minority
"
------------------------------------------------------------
--== Sent via Deja.com ==--
http://www.deja.com/
next reply other threads:[~2001-05-10 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 3:57 Jacky Liu [this message]
2001-05-11 18:45 ` 2.4.4 kernel freeze for unknown reason Vincent Stemen
2001-05-11 18:46 ` Alan Cox
2001-05-12 6:05 ` Mike Galbraith
2001-05-12 11:18 ` Alan Cox
2001-05-12 13:45 ` Mike Galbraith
2001-05-12 14:25 ` Alan Cox
2001-05-12 15:33 ` Mike Galbraith
2001-05-13 18:16 ` Christoph Rohland
2001-05-14 4:36 ` Mike Galbraith
2001-05-13 6:17 ` Vincent Stemen
-- strict thread matches above, loose matches on Subject: below --
2001-05-11 2:26 Jacky Liu
2001-05-15 7:13 Jacky Liu
2001-05-16 5:25 ` Vincent Stemen
2001-05-29 3:59 Vasco Figueira
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=200105100357.UAA16327@mail25.bigmailbox.com \
--to=jq419@my-deja.com \
--cc=linux-kernel@vger.kernel.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