Comment 8 for bug 554749

Some comment on the net suggested I look at dmesg, and I noticed the messages below there. (There were several identical copies, with ~120 delay in their timestamps.) It might help to know what Picard was doing when SSHFS locked up.

[ 1440.800052] INFO: task picard:2290 blocked for more than 120 seconds.
[ 1440.800056] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1440.800059] picard D 00000000ffffffff 0 2290 1 0x00000000
[ 1440.800065] ffff8800cfa41c78 0000000000000086 0000000000015b80 0000000000015b80
[ 1440.800071] ffff88010fe6df80 ffff8800cfa41fd8 0000000000015b80 ffff88010fe6dbc0
[ 1440.800076] 0000000000015b80 ffff8800cfa41fd8 0000000000015b80 ffff88010fe6df80
[ 1440.800081] Call Trace:
[ 1440.800091] [<ffffffff810f38d0>] ? sync_page+0x0/0x50
[ 1440.800096] [<ffffffff8153e697>] io_schedule+0x47/0x70
[ 1440.800100] [<ffffffff810f390d>] sync_page+0x3d/0x50
[ 1440.800104] [<ffffffff8153ed9a>] __wait_on_bit_lock+0x5a/0xc0
[ 1440.800108] [<ffffffff810f38a7>] __lock_page+0x67/0x70
[ 1440.800114] [<ffffffff81085340>] ? wake_bit_function+0x0/0x40
[ 1440.800118] [<ffffffff810f36de>] ? find_get_page+0x1e/0xa0
[ 1440.800121] [<ffffffff810f4f33>] find_lock_page+0x63/0x80
[ 1440.800125] [<ffffffff810f5192>] filemap_fault+0x182/0x460
[ 1440.800130] [<ffffffff811118b4>] __do_fault+0x54/0x500
[ 1440.800135] [<ffffffff81114df8>] handle_mm_fault+0x1a8/0x3c0
[ 1440.800140] [<ffffffff810397a9>] ? default_spin_lock_flags+0x9/0x10
[ 1440.800145] [<ffffffff8154334a>] do_page_fault+0x12a/0x3b0
[ 1440.800149] [<ffffffff81540ca5>] page_fault+0x25/0x30