All of lore.kernel.org
 help / color / mirror / Atom feed
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 20:59:48 -0800	[thread overview]
Message-ID: <200303162059.48245.gregory@castandcrew.com> (raw)
In-Reply-To: <20030317022646.GN20188@holomorphy.com>

On Sunday 16 March 2003 18:26, William Lee Irwin III wrote:
> If it didn't behave badly then it won't help to look at the stats.

I'm seriously at my wits end.  (Not because of you!  I hate vague 
problems...)  I have no idea why it behaved itself this time, just like i 
have no idea why it misbehaves.

Right now, I'm back to running 2.4.19 with the inode.c patch from one of the 
2.4.19-preXX-aaY kernels (see 
http://castandcrew.com/~gregory/lkmlstuff/burpr/2.4.19/patches) as the most 
stable thing we've gotten so far.

I'm going to write some scripts to run out of cron ever 5 minutes (or maybe 
even every minute) to collect meminfo, slabinfo, ps output, and whatever 
else i can think of.  What else would be useful to help you track down 
these problems?

Hopefully, the next time the system goes to hell, I'll have _something_ to 
give you.

As a side question, is bigmem >2GB?  I.e., if I pass "mem=2048m" to the 
kernel from lilo, will the bigmem stuff for the VM be disabled, or should I 
instead build a new kernel with high memory support turned off?  Also, with 
highmem support turned off, the max memory is 2GB, right?  I may well just 
ignore the high 6GB out of desperation to get a stable system until 2.6 is 
released.

Thanks again for taking the time.

Working on a migrain,
Gregory

-- 
Gregory K. Ruiz-Ade <gregory@castandcrew.com>
Sr. Systems Administrator
Cast & Crew Entertainment Services, Inc.


  reply	other threads:[~2003-03-17  4:49 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
2003-03-17  2:26                 ` William Lee Irwin III
2003-03-17  4:59                   ` Gregory K. Ruiz-Ade [this message]
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=200303162059.48245.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 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.