public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Orion Poplawski <orion@cora.nwra.com>
To: linux-kernel@vger.kernel.org
Subject: RH8.0 - 2.4.18-27 System gets wedged in jbd:do_get_write_access
Date: Thu, 01 May 2003 09:06:14 -0600	[thread overview]
Message-ID: <b8rd2u$2i9$1@main.gmane.org> (raw)

I've got a system that has been locking up on me pretty frequently for a 
while.  It is currently running RH 8.0 kernel 2.4.18-27, but the problem 
has been present at previous versions.  I suspect a hardware issue of 
some kind, since most of our systems are running this software, but am 
not getting any error messages.

I've installed the debug kernel, and using kdb alt-sysreq-p have 
determined that all of the tasks get hung up in 
"jbd:do_get_write_access".  Basic scheduling is still working, but 
anything that attempts to access the disk hangs.

Are there any other steps I can take to debug?  I've run basic hard disk 
read diagnostics and not found any problems, as well as memtst86.

Thank you,

  Orion Poplawski



                 reply	other threads:[~2003-05-01 15:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='b8rd2u$2i9$1@main.gmane.org' \
    --to=orion@cora.nwra.com \
    --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