From: Bob Breuer <breuerr@mc.net>
To: sparclinux@vger.kernel.org
Subject: Re: nuke string.h micro-optimizations from orbit
Date: Fri, 15 Jul 2005 16:37:25 +0000 [thread overview]
Message-ID: <42D7E645.3020304@mc.net> (raw)
In-Reply-To: <20050607031302.GA2621@holomorphy.com>
Jurij Smakov wrote:
>
> Even though eliminating initrd made kernel to boot, under heavy I/O and
> memory use it randomly corrupts the filesystem, so we are back to square
> one.
That sounds less stable than mine. Currently my ss20 has been up for
about 60 hours with 2.6.12 and survived a couple kernel recompiles (I
did a 'make clean; make all' overnight to verify). The only problem
I've seen is when the scsi driver goes nuts and requires a power cycle
to recover, which seems to happen more frequently when the disk cache is
cold, but I haven't noticed any actual corruption recently.
Here's my current configuration:
hypersparc 150MHz, 512K cache
192MB ram (no highmem)
ext2/ext3 partitions
kernel 2.6.12 compiled with gcc 3.3.4
My suspicion is that highmem may cause problems. I'll try rearranging
the ram this weekend and see if I can make an initrd fail.
Bob
next prev parent reply other threads:[~2005-07-15 16:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 3:13 nuke string.h micro-optimizations from orbit William Lee Irwin III
2005-06-08 3:18 ` Jurij Smakov
2005-06-08 3:24 ` William Lee Irwin III
2005-06-08 4:36 ` Jurij Smakov
2005-06-08 5:29 ` Patrick Finnegan
2005-06-08 11:52 ` William Lee Irwin III
2005-06-08 19:06 ` David S. Miller
2005-06-08 19:19 ` William Lee Irwin III
2005-06-08 19:22 ` David S. Miller
2005-07-09 2:22 ` Jurij Smakov
2005-07-15 4:21 ` Jurij Smakov
2005-07-15 16:37 ` Bob Breuer [this message]
2005-07-16 16:29 ` Bob Breuer
2005-07-23 1:07 ` Jurij Smakov
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=42D7E645.3020304@mc.net \
--to=breuerr@mc.net \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.