From: "Bulent Abali" <abali@us.ibm.com>
To: Jeff Dike <jdike@karaya.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
James Stevenson <mistral@stev.org>
Subject: Re: all processes waiting in TASK_UNINTERRUPTIBLE state
Date: Mon, 25 Jun 2001 12:48:46 -0400 [thread overview]
Message-ID: <OF831FC2D7.C211A862-ON85256A76.005AEC98@pok.ibm.com> (raw)
>abali@us.ibm.com said:
>> I am running in to a problem, seemingly a deadlock situation, where
>> almost all the processes end up in the TASK_UNINTERRUPTIBLE state.
>> All the process eventually stop responding, including login shell, no
>> screen updates, keyboard etc. Can ping and sysrq key works. I
>> traced the tasks through sysrq-t key. The processors are in the idle
>> state. Tasks all seem to get stuck in the __wait_on_page or
>> __lock_page.
>
>I've seen this under UML, Rik van Riel has seen it on a physical box, and
we
>suspect that they're the same problem (i.e. mine isn't a UML-specific
bug).
Can you give more details? Was there an aic7xxx scsi driver on the box?
run_task_queue(&tq_disk) should eventually unlock those pages
but they remain locked. I am trying to narrow it down to fs/buffer
code or the SCSI driver aic7xxx in my case. Thanks. /bulent
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next reply other threads:[~2001-06-25 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 16:48 Bulent Abali [this message]
2001-06-25 18:25 ` Jeff Dike
2001-06-25 17:39 ` Rik van Riel
2001-06-25 19:33 ` Jeff Dike
[not found] <Pine.LNX.4.30.0106252031240.25982-100000@cyrix.stev.org>
2001-06-29 20:40 ` Jeff Dike
2001-06-30 0:12 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2001-06-26 14:47 Bulent Abali
2001-06-26 15:02 ` Andrea Arcangeli
2001-06-25 14:10 Bulent Abali
2001-06-25 17:05 ` Jeff Dike
2001-06-25 20:10 ` James Stevenson
2001-06-26 12:55 ` Andrea Arcangeli
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=OF831FC2D7.C211A862-ON85256A76.005AEC98@pok.ibm.com \
--to=abali@us.ibm.com \
--cc=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mistral@stev.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