public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John F Flynn III <flynnj@cs.fiu.edu>
To: linux-kernel@vger.kernel.org
Subject: Very rare crash in prune_dcache
Date: Mon, 19 Dec 2005 16:38:55 -0500	[thread overview]
Message-ID: <43A7286F.3080104@cs.fiu.edu> (raw)

Good evening, folks...

We have been experiencing a very rare (on average once every two to 
three months) crash on some of our servers.

uname -a:
Linux cheetah 2.6.9-22.0.1.ELsmp #1 SMP Thu Oct 27 13:14:25 CDT 2005 
i686 i686 i386 GNU/Linux

(This is a CentOS provided kernel)

Here is a photo of the bottom of the panic. Unfortunately the kernel has 
no chance to log this anywhere else:

http://www.cs.fiu.edu/~flynnj/cheetah-crash.jpg


The crash appears to be in prune_dcache, and has happened on several 
distinct machines, so we do not believe it is a hardware problem.

If anyone has pointers on what bug could be causing this crash, or if 
it's been fixed in newer kernels we could try, it would be greatly 
appreciated. This only seems to happen on loaded production machines, 
and it happens so rarely that more detailed debugging is nearly impossible.

Thanks in advance,
-John Flynn

-- 
John Flynn                              flynnj@cs.fiu.edu
=========================================================
Systems and Network Administration             /\_/\
School of Computer Science                    ( O.O )
Florida International University               >   <

             reply	other threads:[~2005-12-19 21:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19 21:38 John F Flynn III [this message]
2005-12-19 22:34 ` Very rare crash in prune_dcache Cliff Wickman
2005-12-20  6:46   ` Bharata B Rao
2005-12-20 13:33     ` Cliff Wickman

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=43A7286F.3080104@cs.fiu.edu \
    --to=flynnj@cs.fiu.edu \
    --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