Public bug reported:

Installed lucid (fully upgraded) in a new computer. There's a program
(amule) that consistently hangs up after some time (typically one or two
hours). When this happens, its window becomes unresponsive and any
attempts to kill it are fruitless. It also typically uses 100% cpu
according to top. Killing the window with xkill closes the windows but
the process remains.

I have this same setup in an older computer where this does not happen,
so I suspect that the new one being an i5 could have something to do.

$ ps l `pidof amule`
F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
0  1000  6156     1  20   0 141192 42252 coredu Dl   ?         14:23 amule

$ sudo kill -9 `pidof amule`; sleep 5s; ps l `pidof amule`
F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
0  1000  6156     1  20   0 141192 42252 coredu Dl   ?         14:23 amule

$ uname -a
Linux tacitus 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 16 19:48:22 UTC 2010 
i686 GNU/Linux

$ cat /proc/version_signature
Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7

I attach dmesg, but these extracted messages could have something to do:

[44749.526602] INFO: task amule:6177 blocked for more than 120 seconds.
[44749.526606] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[44749.526608] amule         D 00000b53     0  6177      1 0x00000008
[44749.526612]  f1817f18 00200086 f19be000 00000b53 00000000 c0848760 efd94f2c 
c0848760
[44749.526618]  74ba1350 00002783 c0848760 c0848760 efd94f2c c0848760 c0848760 
c10c7800
[44749.526622]  00000001 00002783 efd94c80 f1b68578 f1b6857c ffffffff f1817f44 
c058c1f6
[44749.526627] Call Trace:
[44749.526636]  [<c058c1f6>] __mutex_lock_slowpath+0xd6/0x140
[44749.526638]  [<c058c105>] mutex_lock+0x25/0x40
[44749.526644]  [<c0208b6c>] generic_file_llseek+0x2c/0x70
[44749.526647]  [<c0208b40>] ? generic_file_llseek+0x0/0x70
[44749.526650]  [<c02083b7>] vfs_llseek+0x37/0x50
[44749.526652]  [<c0208c0e>] sys_llseek+0x5e/0x90
[44749.526656]  [<c01033ec>] syscall_call+0x7/0xb

** Affects: ubuntu
     Importance: Undecided
         Status: New

-- 
Unresponsive process cannot be killed (sudo kill -9)
https://bugs.launchpad.net/bugs/665211
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to