From: "Gregory K. Ruiz-Ade" <gregory@castandcrew.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 instability on bigmem systems?
Date: Sun, 16 Mar 2003 18:15:11 -0800 [thread overview]
Message-ID: <200303161815.11973.gregory@castandcrew.com> (raw)
In-Reply-To: <20030314200857.GL20188@holomorphy.com>
On Friday 14 March 2003 12:08, William Lee Irwin III wrote:
> On Fri, Mar 14, 2003 at 09:31:15AM -0800, Gregory K. Ruiz-Ade wrote:
> > Ahh. I was a bit out of it yesterday, and didn't think to actually
> > stress the machine. :\
> > I'll be able to give it a good beating this weekend sometime.
>
> cc: me when you post those results.
Okay, I tried to load the system a bit and stress out the disk I/O, running
a couple finds across the whole system (find | xargs stat, find | xargs cat
> /dev/null, a couple other things) after sucking up free memory by catting
our database disk files to /dev/null. I also had a 'make -j5 clean
oldconfig dep bzImage modules' running to try to drive the load up a bit,
too.
I've got snapshots of meminfo, slabinfo, and output from 'ps auxfww' at:
http://castandcrew.com/~gregory/lkmlstuff/burpr/2.4.20/loadtest/
It only really starts getting interesting after 20030316.1725, when I
started the kernel build. I have a very simple shell script that basically
does nothing other than "make clean oldconfig dep && make -j5 bzImage &&
make -j5 modules". I ran that a couple times in the sources for Red Hat's
2.4.9-e.12 kernel sources.
Surprisingly I wasn't able to grind down the system like I expected. Not
sure why it's behaving so wonderfully today.
It crashed again on Friday night, running 2.4.19. The only information I
was able to get was a kernel BUG message on the serial console (I
ksymoops'ed it after rebooting). From what I could tell after the fact,
nothing was really running. Several scripts got fired off by cron, which
check various things (mainly to make sure certain services are still
running), and around then is when the system locked up. The info I have
for that crash is at:
http://castandcrew.com/~gregory/lkmlstuff/burpr/2.4.19
As it is, I'm going to try running on Red Hat's 2.4.9-e.12 sources this
week. I'm compiling the kernel right now, and will be rebooting into it
shortly.
This has been quite the week of headaches for me.
--
Gregory K. Ruiz-Ade <gregory@castandcrew.com>
Sr. Systems Administrator
Cast & Crew Entertainment Services, Inc.
next prev parent reply other threads:[~2003-03-17 2:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 0:27 2.4.20 instability on bigmem systems? Gregory K. Ruiz-Ade
2003-03-14 0:42 ` William Lee Irwin III
2003-03-14 1:45 ` Gregory K. Ruiz-Ade
2003-03-14 1:53 ` William Lee Irwin III
2003-03-14 3:55 ` Gregory K. Ruiz-Ade
2003-03-14 4:13 ` William Lee Irwin III
2003-03-14 17:31 ` Gregory K. Ruiz-Ade
2003-03-14 20:08 ` William Lee Irwin III
2003-03-17 2:15 ` Gregory K. Ruiz-Ade [this message]
2003-03-17 2:26 ` William Lee Irwin III
2003-03-17 4:59 ` Gregory K. Ruiz-Ade
2003-03-17 5:38 ` Gregory K. Ruiz-Ade
2003-03-14 18:31 ` Martin J. Bligh
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=200303161815.11973.gregory@castandcrew.com \
--to=gregory@castandcrew.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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