Here you go: ps l, as requested.
kitchen:~$ ps l 7823
F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND
0 1000 7823 1787 20 0 113056 21760 sync_p D+ pts/0 0:00
/usr/bin/python /usr/bin/bzr diff
kitchen:~$
** Changed in: bzr (Ubuntu)
Status:
If you're hitting this problem on nfs4, it's very likely an Ubuntu
kernel bug; please file it there. In fact, pretty much regardless of
the environment, if the process is unkillable it's a kernel bug.
--
bzr becomes unkillable with -9
https://bugs.launchpad.net/bugs/651806
You received this bug
I'm seeing this with another process (amule). The process ends stuck at
100% cpu, can't be killed by root with -9. The process is sometimes in R
and sometimes in D state. This has happened to me with an up-to-date
Lucid (kernel 32-25) and a fresh Maverick install.
Next time this happens to me
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/651806/+attachment/1656201/+files/Dependencies.txt
** Attachment added: ProcMaps.txt
https://bugs.launchpad.net/bugs/651806/+attachment/1656202/+files/ProcMaps.txt
** Attachment added: ProcStatus.txt
Hi,
If you can reproduce this, please run
ps l BZR_PID
inserting the right process id there. The second word is a lower-case
l. That will tell us where it was in the kernel.
Generally speaking a process stuck for a long time in D would be a
kernel bug not an application bug.
--
Martin
