From: Peter Williams <pwil3058@bigpond.net.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Badari Pulavarty <pbadari@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc2-mm4 ps hang ?
Date: Sat, 02 Oct 2004 10:13:08 +1000 [thread overview]
Message-ID: <415DF294.1050707@bigpond.net.au> (raw)
In-Reply-To: <20041001164938.3231482e.akpm@osdl.org>
Andrew Morton wrote:
> Badari Pulavarty <pbadari@us.ibm.com> wrote:
>
>>Here is the full sysrq-t output.
>
>
> What's this guy up to?
>
> db2fmcd D 0000000000000000 0 11032 1 1373 11031 (NOTLB)
> 00000101b9b9bef8 0000000000000002 0000003700000037 00000101c13608a0
> 000000010000009f 0000010199649250 0000010199649588 0000000000000000
> 0000000000000206 ffffffff801353db
> Call Trace:<ffffffff801353db>{try_to_wake_up+971} <ffffffff80445570>{__down_write+128}
> <ffffffff80125e7f>{sys32_mmap+143} <ffffffff80124b01>{ia32_sysret+0}
>
>
> Something is seriously screwed up if it's stuck in try_to_wake_up(). Tried
> generating a few extra traces?
>
> Then again, maybe we're missing an up_read() somewhere. hrm, I'll check.
It's highly^64 unlikely BUT a possible reason for a task getting stuck
in try_to_wakeup() is the function adjust_sched_timestamp() which is
part of the ZAPHOD patch. This could be tested by removing the if-while
statement from that function and seeing if that fixes things. Or you
could just remove the call from try_to_wake_up().
I'll use a more sensible (bounded) mechanism in the next version of ZAPHOD.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2004-10-02 0:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 16:08 2.6.9-rc2-mm4 ps hang ? Badari Pulavarty
2004-10-01 19:09 ` Andrew Morton
2004-10-01 20:06 ` Hugh Dickins
2004-10-01 20:59 ` Andrew Morton
2004-10-01 21:29 ` Badari Pulavarty
2004-10-01 21:55 ` Andrew Morton
2004-10-01 23:06 ` Badari Pulavarty
2004-10-01 23:49 ` Andrew Morton
2004-10-02 0:13 ` Peter Williams [this message]
2004-10-02 0:19 ` Badari Pulavarty
2004-10-02 0:44 ` Andrew Morton
2004-10-04 15:43 ` Badari Pulavarty
2004-10-02 0:29 ` Badari Pulavarty
2004-10-02 0:42 ` Andrew Morton
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=415DF294.1050707@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
/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.