From: "Timothy A. DeWees" <whtdrgn@mail.cannet.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 2.2.18 reboots on high load.
Date: Wed, 10 Jan 2001 11:47:58 -0500 [thread overview]
Message-ID: <007801c07b25$1695db20$7930000a@hcd.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
Hello,
I have a 2.2.18 (with reiserfs patch), running on a Pentium 100
any time I get high disk writes or reads my system just reboots.
I have had it up and running with moderate disk activity (telnet
and small FTP's) for a week; however, when I write alot to the
disk (100 Mb plus), the system just reboots. I am also getting
kernel panics around every 3-4 times. I tried writing to the disk
with Samba, and fith FTP. I am running proFTP. Please tell me
what I need to send you. I will not that /proc/cpuinfo tells me that
my processor has a f00f bug?
The system is as follows.
Intel Pentium 100
32 Mb Ram
1Gb root partition - 32 Mb swap
14 Gb reiserfs partition
I am running Samba 2.0.7 and Apache 1.3.14 (with mod-ssl).
[-- Attachment #2: Type: text/html, Size: 1826 bytes --]
next reply other threads:[~2001-01-10 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 16:47 Timothy A. DeWees [this message]
2001-01-10 16:55 ` 2.2.18 reboots on high load Timothy A. DeWees
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='007801c07b25$1695db20$7930000a@hcd.net' \
--to=whtdrgn@mail.cannet.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