From: Patrick Mau <mau@oscar.ping.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Process stuck with 2.5 bk current
Date: Thu, 20 Mar 2003 18:54:57 +0100 [thread overview]
Message-ID: <20030320175457.GA3171@oscar.ping.de> (raw)
Hallo list,
"kded", the KDE desktop daemon, always gets stuck in
D state with kernel 2.5 (BK from today). I used Sysreq-T
to get a call trace. Maybe someone has a clue what's
going on.
The NFS mounts on this machine are from a remote
2.4.20 nfs server with reiserfs partitions, if
that matters. NFS still works, BTW.
cheers,
Patrick
Here's the call trace:
Mar 20 18:47:13 tony kernel: kdeinit D 00000046 4292898224 636
635
(NOTLB)
Mar 20 18:47:13 tony kernel: Call Trace:
Mar 20 18:47:13 tony kernel: [<c011ef29>] schedule_timeout+0x5f/0xb3
Mar 20 18:47:13 tony kernel: [<c011eec1>] process_timeout+0x0/0x9
Mar 20 18:47:13 tony kernel: [<c011589b>] sleep_on_timeout+0x4a/0x66
Mar 20 18:47:13 tony kernel: [<c011556c>] default_wake_function+0x0/0x12
Mar 20 18:47:13 tony kernel: [<c018fb5c>] nlmclnt_block+0x4c/0xc6
Mar 20 18:47:13 tony kernel: [<c01904e0>] nlmclnt_call+0xcf/0x204
Mar 20 18:47:13 tony kernel: [<c01908c3>] nlmclnt_lock+0x59/0xc9
Mar 20 18:47:13 tony kernel: [<c01902b5>] nlmclnt_proc+0x2d9/0x3a7
Mar 20 18:47:13 tony kernel: [<c0183bdd>] nfs_lock+0x1e2/0x263
Mar 20 18:47:13 tony kernel: [<c01839fb>] nfs_lock+0x0/0x263
Mar 20 18:47:13 tony kernel: [<c0154638>] fcntl_setlk64+0x215/0x296
Mar 20 18:47:13 tony kernel: [<c01411d7>] dentry_open+0x1a7/0x1c4
Mar 20 18:47:13 tony kernel: [<c0150462>] sys_fcntl64+0x4e/0x95
Mar 20 18:47:13 tony kernel: [<c0108d5b>] syscall_call+0x7/0xb
reply other threads:[~2003-03-20 17:43 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=20030320175457.GA3171@oscar.ping.de \
--to=mau@oscar.ping.de \
--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.