I did some more testing: Scenario 1: 1. Boot and loggin 2. Close lid 3. Wait a second or two 4. Open lid and get a black screen 5. Laptop seems unresponsive but pressing power button once every couple of seconds finally gets me login screen.
Scenario 2: 1. Boot and loggin 2. Close lid 3. Wait a minute or more 4a. Open lid and get login that is unresponsive, press power button once to get responsive loggin 4b. Open lid and login With both scenarios once you are logged in you cant open any applications but terminal but the terminal will only run some commands like ls, if you try sudo tail -f -n40 /var/log/syslog it just hangs up and Ctrl C wont exit the command you have to close the terminal and reopen. I have syslog sections for before and after suspend freeze Here are some snippets: Oct 10 17:18:14 golumn systemd-sleep[1676]: 'SUSPEND' command timed out. Oct 10 17:18:14 golumn systemd-sleep[1677]: /lib/systemd/system-sleep/wpasupplicant failed with error code 254. Oct 10 17:18:14 golumn systemd-sleep[1676]: Suspending system... Oct 10 17:18:14 golumn kernel: [ 80.234679] PM: Syncing filesystems ... done. Oct 10 17:18:14 golumn kernel: [ 80.244854] PM: Preparing system for sleep (mem) Oct 10 17:18:34 golumn kernel: [ 80.247130] Freezing user space processes ... Oct 10 17:18:34 golumn kernel: [ 100.254362] Freezing of tasks failed after 20.004 seconds (9 tasks refusing to freeze, wq_busy=0): Oct 10 17:18:34 golumn kernel: [ 100.255894] whoopsie D 0 1186 1 0x00000004 Oct 10 17:18:34 golumn kernel: [ 100.255899] Call Trace: Oct 10 17:18:34 golumn kernel: [ 100.255908] __schedule+0x28b/0x890 Oct 10 17:18:34 golumn kernel: [ 100.255917] schedule+0x36/0x80 Oct 10 17:18:34 golumn kernel: [ 100.255924] schedule_preempt_disabled+0xe/0x10 Oct 10 17:18:34 golumn kernel: [ 100.255932] __mutex_lock.isra.2+0x190/0x4e0 Oct 10 17:18:34 golumn kernel: [ 100.255941] ? __kmalloc_node_track_caller+0x1ea/0x2a0 Oct 10 17:18:34 golumn kernel: [ 100.255950] __mutex_lock_slowpath+0x13/0x20 Oct 10 17:18:34 golumn kernel: [ 100.255957] ? __mutex_lock_slowpath+0x13/0x20 Oct 10 17:18:34 golumn kernel: [ 100.255965] mutex_lock+0x2f/0x40 Oct 10 17:18:34 golumn kernel: [ 100.255970] rtnetlink_rcv+0x19/0x30 Oct 10 17:18:34 golumn kernel: [ 100.255975] netlink_unicast+0x18e/0x220 Oct 10 17:18:34 golumn kernel: [ 100.255981] netlink_sendmsg+0x2c5/0x3c0 Oct 10 17:18:34 golumn kernel: [ 100.255991] sock_sendmsg+0x38/0x50 Oct 10 17:18:34 golumn kernel: [ 100.255995] SYSC_sendto+0x13f/0x180 Oct 10 17:18:34 golumn kernel: [ 100.256003] ? ktime_get_ts64+0x4e/0xe0 Oct 10 17:18:34 golumn kernel: [ 100.256009] SyS_sendto+0xe/0x10 Oct 10 17:18:34 golumn kernel: [ 100.256015] entry_SYSCALL_64_fastpath+0x1e/0xa9 Oct 10 17:18:34 golumn kernel: [ 100.256018] RIP: 0033:0x7fbef23a0bdf Oct 10 17:18:34 golumn kernel: [ 100.256020] RSP: 002b:00007ffce2581080 EFLAGS: 00000246 Oct 10 17:19:49 golumn dbus-daemon[1007]: Successfully activated service 'org.gnome.Nautilus' Oct 10 17:19:49 golumn nautilus[1814]: g_key_file_load_from_file: assertion 'file != NULL' failed Oct 10 17:19:49 golumn nautilus[1814]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” If you guys think this is not related how (what do I call it what package to register it under) do I log this because there are no crash reports in /var/crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720557 Title: System freeze on attempt to suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
