Prev: uniform cdrom: fix mutex unlocking in /proc/sys/dev/cdrom/info file
Next: vmscan: Update isolated page counters outside of main path in shrink_inactive_list()
From: Jan De Luyck on 14 Jun 2010 15:50 Hey Folks, I recently switched over to 2.6.34, and now I'm getting these: INFO: task rsync:20019 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. rsync D 000000000006a7c6 0 20019 20005 0x00000004 ffff88001dcb9b48 0000000000000082 0000000000004000 0000000000011bc0 ffff88001dcb9fd8 ffff88001dcb9fd8 ffff8800672d5730 0000000000011bc0 0000000000000000 ffffffff81101fac ffff8800672d5730 ffffffff8161b020 Call Trace: [<ffffffff81101fac>] ? ext4_check_dir_entry+0x38/0xfe [<ffffffff810b3e91>] ? ll_rw_block+0xe0/0xfe [<ffffffff812cdea5>] ? _raw_spin_lock_irqsave+0x18/0x34 [<ffffffff810a5710>] ? __wait_on_freeing_inode+0x83/0xa1 [<ffffffff810434b2>] ? wake_bit_function+0x0/0x23 [<ffffffff810a5758>] ? find_inode_fast+0x2a/0x4c [<ffffffff810a57a2>] ? ifind_fast+0x28/0x81 [<ffffffff810a6475>] ? iget_locked+0x30/0x151 [<ffffffff81105de8>] ? ext4_iget+0x26/0x704 [<ffffffff812cdc5e>] ? _raw_spin_unlock+0x10/0x2c [<ffffffff8110ec95>] ? ext4_lookup+0x83/0xda [<ffffffff8109baf5>] ? do_lookup+0xfb/0x1d9 [<ffffffff8109db7b>] ? link_path_walk+0x6cd/0xb25 [<ffffffff8109e12c>] ? path_walk+0x6a/0xe2 [<ffffffff8109e271>] ? do_path_lookup+0x20/0x41 [<ffffffff8109eb83>] ? user_path_at+0x48/0x7f [<ffffffff810a09b8>] ? filldir+0x0/0xa9 [<ffffffff81097363>] ? cp_new_stat+0xe9/0xfb [<ffffffff812cdecf>] ? _raw_spin_lock+0xe/0x24 [<ffffffff81097228>] ? vfs_fstatat+0x2c/0x57 [<ffffffff810973b6>] ? sys_newlstat+0x11/0x30 [<ffffffff81001f2b>] ? system_call_fastpath+0x16/0x1b This did not show up with any 2.6.33.x. Any fix to try? Kind regards Jan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |