When selecting suspend from the panel, the screen goes black and after some time the screensaver appears. After a fresh boot, it works. However, after the machine was already several times in suspend mode it refuses to suspend and the screensaver appears instead.
/var/log/syslog: Feb 9 18:00:07 work-com kernel: [32590.891991] PM: Syncing filesystems ... done. Feb 9 18:00:07 work-com kernel: [32591.023833] PM: Preparing system for mem sleep Feb 9 18:00:07 work-com kernel: [32591.023847] Freezing user space processes ... Feb 9 18:00:07 work-com kernel: [32611.024278] Freezing of tasks failed after 20.00 seconds (1 tasks refusing to freeze, wq_busy=0): Feb 9 18:00:07 work-com kernel: [32611.024308] bluetoothd D ffffffff81805120 0 1604 1 0x00800004 Feb 9 18:00:07 work-com kernel: [32611.024315] ffff8800da6d5c08 0000000000000082 ffff8800d1545cc8 ffff88011fd12ab0 Feb 9 18:00:07 work-com kernel: [32611.024320] ffff8800da6d5fd8 ffff8800da6d5fd8 ffff8800da6d5fd8 0000000000012a40 Feb 9 18:00:07 work-com kernel: [32611.024326] ffff880118f10000 ffff8800da6cc560 ffff8800d1545c80 7fffffffffffffff Feb 9 18:00:07 work-com kernel: [32611.024331] Call Trace: Feb 9 18:00:07 work-com kernel: [32611.024340] [<ffffffff815eff1f>] schedule+0x3f/0x60 Feb 9 18:00:07 work-com kernel: [32611.024345] [<ffffffff815f0565>] schedule_timeout+0x2a5/0x320 Feb 9 18:00:07 work-com kernel: [32611.024349] [<ffffffff815efd5f>] wait_for_common+0xdf/0x180 Feb 9 18:00:07 work-com kernel: [32611.024355] [<ffffffff81057340>] ? try_to_wake_up+0x200/0x200 Feb 9 18:00:07 work-com kernel: [32611.024358] [<ffffffff815efedd>] wait_for_completion+0x1d/0x20 Feb 9 18:00:07 work-com kernel: [32611.024363] [<ffffffff810811c6>] kthread_stop+0x46/0x110 Feb 9 18:00:07 work-com kernel: [32611.024370] [<ffffffffa0eb5146>] bnep_del_connection+0x36/0x60 [bnep] Feb 9 18:00:07 work-com kernel: [32611.024375] [<ffffffffa0eb5569>] bnep_sock_ioctl+0x189/0x250 [bnep] Feb 9 18:00:07 work-com kernel: [32611.024379] [<ffffffff81130338>] ? handle_mm_fault+0x1f8/0x350 Feb 9 18:00:07 work-com kernel: [32611.024384] [<ffffffff81153bbf>] ? kmem_cache_free+0x2f/0x120 Feb 9 18:00:07 work-com kernel: [32611.024390] [<ffffffff814c7de0>] sock_do_ioctl+0x30/0x70 Feb 9 18:00:07 work-com kernel: [32611.024399] [<ffffffff814c8e69>] sock_ioctl+0x79/0x2f0 Feb 9 18:00:07 work-com kernel: [32611.024402] [<ffffffff811872ef>] ? mntput+0x1f/0x30 Feb 9 18:00:07 work-com kernel: [32611.024404] [<ffffffff81179e7a>] do_vfs_ioctl+0x8a/0x340 Feb 9 18:00:07 work-com kernel: [32611.024406] [<ffffffff8117a1c1>] sys_ioctl+0x91/0xa0 Feb 9 18:00:07 work-com kernel: [32611.024409] [<ffffffff815fa1c2>] system_call_fastpath+0x16/0x1b Feb 9 18:00:07 work-com kernel: [32611.024491] Feb 9 18:00:07 work-com kernel: [32611.024492] Restarting tasks ... done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/879604 Title: bluetooth malfunction after suspend/resume with trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/879604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
