public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rob Mueller" <robm@fastmail.fm>
To: <linux-kernel@vger.kernel.org>
Cc: "Bron Gondwana" <brong@fastmail.fm>,
	"Jeremy Howard" <jhoward@fastmail.fm>
Subject: 2.6.12.2 dies after 24 hours
Date: Tue, 12 Jul 2005 19:26:29 +1000	[thread overview]
Message-ID: <01dd01c586c3$cdd525d0$7c00a8c0@ROBMHP> (raw)

As background, we've been using a relatively old kernel (2.6.4-mm2) on some 
IBM x235 machines with 6G of RAM, umem cards, and serveraid storage. These 
machines are under continuous heavy-ish load, load avg between about 1 and 
5, with between 2500-3500 procs at all times, with several largish ReiserFS 
partitions and have been running *really* well with >250 days uptime on one 
machine.

We recently tried upgrading one of the machines to the latest kernel 
(2.6.12.2) and it's died after about 24 hours. It seemed to end up in some 
weird state where we could ssh into it, and some commands worked (eg uptime) 
but process list related commands (ps) would just freeze up into an 
unkillable state and we'd have to close the seesion and ssh in again.

I did manage to get a full sysrq-t dump. I've placed it, a kernel config 
dump, and a dmesg boot dump here:

http://robm.fastmail.fm/kernel/t7/

Hope this provides some useful data to track down the problem.

Rob

PS. Yes, I know this is a non-PAE kernel on a 6G machine so 2G was unused. 
This was a mistake in this case, but it still doesn't explain the crash...


             reply	other threads:[~2005-07-12  9:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12  9:26 Rob Mueller [this message]
2005-07-12  9:43 ` 2.6.12.2 dies after 24 hours Lars Roland
2005-07-12 11:46   ` Rob Mueller
2005-07-12 12:13     ` Lars Roland
2005-07-12 13:51       ` Bron Gondwana
2005-07-12 16:37         ` Lars Roland
2005-07-13  0:27           ` Rob Mueller
2005-07-13  0:42             ` Chris Mason
2005-07-13  0:50               ` Rob Mueller
2005-07-13  1:03                 ` Chris Mason
2005-07-13  1:27                   ` Rob Mueller
2005-07-13  1:00               ` Chris Mason

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='01dd01c586c3$cdd525d0$7c00a8c0@ROBMHP' \
    --to=robm@fastmail.fm \
    --cc=brong@fastmail.fm \
    --cc=jhoward@fastmail.fm \
    --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