All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nick Warne" <nick@ukfsn.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Oopses with both recent 2.4.x kernels and 2.6.x kernels
Date: Tue, 15 Jun 2004 18:44:54 +0100	[thread overview]
Message-ID: <40CF43A6.5170.28D6B4D5@localhost> (raw)

FYI.

I have a box here that was originally running 2.4.x.  I updated to 
2.6.x a few months ago, and all was well.  Then I started to get 
curious oops, none of them the same.

I started to suspect NFS, as I use an old 486 to hold the web pages 
to serve to the box via NFS... the oops occurred every Saturday 
morning @ 4:02.  Lead to me think it was some sort of cron.weekly 
issue with the disc activity and file access or the like, or 
whatever... I didn't know - I was on a fishing exercise (and a lot of 
searching on the LKML)

But, after talking to a member of the HantsLUG, and showing logs and 
stuff, he brought up at the swap size.  This box was once 64Mb, but 
is now 128Mb - with 128Mb swap.  I created an additional swap file 
(256Mb), and (touch wood), no oops since, all heathly :)  I never 
looked at this before, as swap was never used _during_ normal running 
of the box, but as he said maybe the cron.weekly ran a lot of stuff 
that did use it up...

Nick

-- 
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."


             reply	other threads:[~2004-06-15 17:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-15 17:44 Nick Warne [this message]
2004-06-15 19:15 ` Oopses with both recent 2.4.x kernels and 2.6.x kernels Stian Jordet
  -- strict thread matches above, loose matches on Subject: below --
2004-02-03 18:26 Stian Jordet
2004-02-05 23:51 ` Marcelo Tosatti
2004-03-02 11:03   ` Stian Jordet
2004-03-02 12:31     ` Stian Jordet
2004-03-09 19:22       ` Marcelo Tosatti
2004-03-09 22:28         ` Stian Jordet
2004-06-14 17:07     ` Steven Dake
2004-06-14 18:26       ` Chris Shoemaker
2004-06-15 13:16       ` Marcelo Tosatti
2004-06-15 14:35         ` Stian Jordet
2004-06-15 17:56         ` Steven Dake

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=40CF43A6.5170.28D6B4D5@localhost \
    --to=nick@ukfsn.org \
    --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 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.