It's a year later, and I am now on different hardware and running Ubuntu 10.10. Imagine my surprise when this bug resurfaced to bite me again today:
[363033.049187] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze): [363033.049222] gnome-setting D 000000000164a060 0 1936 1 0x00800004 [363033.049229] ffff880232095ce8 0000000000000086 ffff880232095c78 0000000000015980 [363033.049234] ffff880232095fd8 0000000000015980 ffff880232095fd8 ffff88021f73adc0 [363033.049239] 0000000000015980 0000000000015980 ffff880232095fd8 0000000000015980 [363033.049244] Call Trace: [363033.049254] [<ffffffff8107fd60>] ? prepare_to_wait+0x60/0x90 [363033.049262] [<ffffffff812428a5>] request_wait_answer+0x85/0x240 [363033.049266] [<ffffffff8107fab0>] ? autoremove_wake_function+0x0/0x40 [363033.049270] [<ffffffff81242adc>] fuse_request_send+0x7c/0x90 [363033.049275] [<ffffffff8124b638>] fuse_statfs+0xe8/0x160 [363033.049281] [<ffffffff8117be1c>] vfs_statfs+0x7c/0xa0 [363033.049285] [<ffffffff8117bf10>] vfs_statfs_native+0x20/0xb0 [363033.049289] [<ffffffff8117c0b3>] sys_statfs+0x73/0xb0 [363033.049294] [<ffffffff811240fe>] ? remove_vma+0x6e/0x90 [363033.049299] [<ffffffff81126549>] ? do_munmap+0x309/0x3a0 [363033.049306] [<ffffffff8100a0f2>] system_call_fastpath+0x16/0x1b
gnome-settings-daemon is in state Ds -- I cannot kill it, and I cannot suspend my new laptop. It would be nice to squash this bug once and for all, as it appears extremely resilient.
It's a year later, and I am now on different hardware and running Ubuntu 10.10. Imagine my surprise when this bug resurfaced to bite me again today:
[363033.049187] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze): d60>] ? prepare_ to_wait+ 0x60/0x90 8a5>] request_ wait_answer+ 0x85/0x240 ab0>] ? autoremove_ wake_function+ 0x0/0x40 adc>] fuse_request_ send+0x7c/ 0x90 638>] fuse_statfs+ 0xe8/0x160 e1c>] vfs_statfs+ 0x7c/0xa0 f10>] vfs_statfs_ native+ 0x20/0xb0 0b3>] sys_statfs+ 0x73/0xb0 0fe>] ? remove_ vma+0x6e/ 0x90 549>] ? do_munmap+ 0x309/0x3a0 0f2>] system_ call_fastpath+ 0x16/0x1b
[363033.049222] gnome-setting D 000000000164a060 0 1936 1 0x00800004
[363033.049229] ffff880232095ce8 0000000000000086 ffff880232095c78 0000000000015980
[363033.049234] ffff880232095fd8 0000000000015980 ffff880232095fd8 ffff88021f73adc0
[363033.049239] 0000000000015980 0000000000015980 ffff880232095fd8 0000000000015980
[363033.049244] Call Trace:
[363033.049254] [<ffffffff8107f
[363033.049262] [<ffffffff81242
[363033.049266] [<ffffffff8107f
[363033.049270] [<ffffffff81242
[363033.049275] [<ffffffff8124b
[363033.049281] [<ffffffff8117b
[363033.049285] [<ffffffff8117b
[363033.049289] [<ffffffff8117c
[363033.049294] [<ffffffff81124
[363033.049299] [<ffffffff81126
[363033.049306] [<ffffffff8100a
gnome-settings- daemon is in state Ds -- I cannot kill it, and I cannot suspend my new laptop. It would be nice to squash this bug once and for all, as it appears extremely resilient.