From: Andrew Morton <akpm@zip.com.au>
To: Andres Salomon <dilinger@mp3revolution.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: D state processes in 2.4.18-pre7-ac3
Date: Thu, 07 Feb 2002 01:23:14 -0800 [thread overview]
Message-ID: <3C624782.14FC8C70@zip.com.au> (raw)
In-Reply-To: <20020207090237.GA2137@mp3revolution.net>
Andres Salomon wrote:
>
> Linux incandescent 2.4.18-pre7-ac3 #1 Tue Feb 5 01:00:50 EST 2002 i686 unknown
>
> I came home today to a bunch of processes apparently hung in jbd's
> do_get_write_access(); apparently, something deadlocked, where no
> processes could write to one of my partition's journal. That's my
> theory, anyways. Several processes had stacks similar to:
>
> ...
>
> And, kjournald had the following:
>
> Call Trace: [<c0131f0a>] [<d08ee6e6>] [<c0112380>] [<d08f08eb>]
> [<d08f07c0>]
> [<c010f4e8>]
> Warning (Oops_read): Code line not seen, dumping what data is available
>
> Trace; c0131f0a <__wait_on_buffer+6a/90>
> Trace; d08ee6e6 <[jbd]journal_commit_transaction+776/dd6>
> Trace; c0112380 <schedule+2c0/2f0>
> Trace; d08f08ea <[jbd]kjournald+10a/1a0>
> Trace; d08f07c0 <[jbd]commit_timeout+0/10>
This is the important part - we sent a write request down the
stack and it seems that I/O completion was never signalled.
You should check for any odd messages from the device driver
or LVM layers, if the logs made it to disk.
-
next prev parent reply other threads:[~2002-02-07 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 9:02 D state processes in 2.4.18-pre7-ac3 Andres Salomon
2002-02-07 9:23 ` Andrew Morton [this message]
2002-02-07 14:53 ` Andres Salomon
2002-02-07 18:29 ` Stephen C. Tweedie
2002-02-07 19:02 ` Andres Salomon
2002-02-07 13:10 ` Stephen C. Tweedie
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=3C624782.14FC8C70@zip.com.au \
--to=akpm@zip.com.au \
--cc=dilinger@mp3revolution.net \
--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.