daemon crashing and going defunct prevents suspend

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

The hung task warnings are a kernel issue

Hi Igor,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command from a Terminal (Applications->Accessories->Terminal) it will automatically gather and attach updated debug information to this report.

apport-collect -p linux 581581

Also, please be sure to take a look at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume . If you can provide any additional information outlined there it would be much appreciated.

Additionally, if you could try to reproduce this with the upstream mainline kernel that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

the issue happened again today and i was able to grab the apport info for gnome-settings-daemon using the current 10.04 kernel (the released one, not a development version).

unfortunately, i cannot test this issue using a livecd as this is a) my primary and only computer and b) it has no cd drive

however, i have installed the current mainline kernel and will let you know if the issue reoccurs there also. i'm attaching the apport report on gnome-settings-daemon as well as on my kernel

this happens using the mainline kernel as well. i couldn't get an apport report on the mainline kernel because apport apparently only works on ubuntu packages, but here is the report on gnome-settings-daemon while running the current mainline. i am not going to keep running the mainline (it causes udev to go crazy and use up 100% cpu) but i'm keeping it installed if you want me to test more stuff against it.

let me know if there is anything you need from me to help troubleshoot the issue. in the meantime, i am renaming gnome-settings-daemon as i keep almost frying my laptop in my bag.

i managed to get another instance of this same issue, but this time i've got kernel tracebacks. i would really like another workaround besides disabling gnome-settings-daemon, so please let me know what I can do to make the issue no longer 'incomplete'.

the tracebacks are attached. here is the output of `ps aux` when the errors occured. you can see from the timestamps in the logs that the suspend attempt took about 2 minutes before finally failing.

root@piglet:/usr/bin# ps aux | grep gnome-settings-daemon | grep -v grep
igor47 1935 0.0 0.4 464444 16012 ? Ssl May31 0:13 /usr/lib/gnome-settings-daemon/gnome-settings-daemon

here are tracebacks from syslog at the same time as the kern.log file above. they were slightly different, so i thought i'd include both.

again, please let me know if there's anything else i can do to help troubleshoot this issue. the lack of gnome-settings-daemon is a serious usability hindrance for me.

@igor -- i cannot tell from your report which mainline kernel you tested and found this also there. Could you retest with the current Maverick kernel and/or confirm you have tested with the v2.6.35-rc4 based kernels please. Thanks!

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.

Igor, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]