Comment 35 for bug 624877

Revision history for this message
Mike Conigliaro (mconigliaro) wrote :

I believe I'm being affected by the same bug, though I have a different stacktrace in my dmesg log:

[3187763.844945] INFO: task dpkg:25373 blocked for more than 120 seconds.
[3187763.844955] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[3187763.844960] dpkg D 0000000112ff6f6c 0 25373 25363 0x00000000
[3187763.844963] ffff880049f0de18 0000000000000286 0000000000000001 ffff880049f0dd98
[3187763.844966] ffff880049f0dd98 ffff880049f0dde0 ffff880044da89b0 ffff880049f0dfd8
[3187763.844968] ffff880044da8600 ffff880044da8600 ffff880044da8600 ffff880049f0dfd8
[3187763.844971] Call Trace:
[3187763.844979] [<ffffffff81204bcd>] log_wait_commit+0xcd/0x160
[3187763.844984] [<ffffffff81059fb0>] ? autoremove_wake_function+0x0/0x40
[3187763.844987] [<ffffffff81204c91>] ? log_start_commit+0x31/0x60
[3187763.844990] [<ffffffff811a4c3b>] ext3_sync_file+0xeb/0x100
[3187763.844994] [<ffffffff811157d9>] vfs_fsync_range+0x99/0xd0
[3187763.844996] [<ffffffff81115878>] vfs_fsync+0x18/0x20
[3187763.844998] [<ffffffff811158b9>] do_fsync+0x39/0x60
[3187763.845000] [<ffffffff8111590b>] sys_fsync+0xb/0x10
[3187763.845004] [<ffffffff81009ba8>] system_call_fastpath+0x16/0x1b
[3187763.845006] [<ffffffff81009b40>] ? system_call+0x0/0x52

dpkg doesn't hang forever for me. It usually just hangs for 15-20 minutes, then finishes like nothing ever happened. I'm not sure if it matters, but I'm on EC2.