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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720557 Title: System freeze on attempt to suspend Status in linux package in Ubuntu: Incomplete Bug description: 1. New install of 17.10 beta 2 on XPS 13 9350. Intel gpu and using wayland (enabled by default) 2. Select top right menu, hold alt, select suspend button I expect the laptop to suspend. Instead the screen goes blank. The laptop remained on (power button is light, fans are on). The laptop is unresponsive until hard reboot (holding down power button). A suspended state is never reached. The laptop previously suspended fine on 17.04. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/pcmC0D0p: david 1388 F...m pulseaudio /dev/snd/controlC0: david 1388 F.... pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Sep 30 12:18:05 2017 InstallationDate: Installed on 2017-09-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: Dell Inc. XPS 13 9350 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=a7e24755-5141-4ab1-a8d4-e4da5ebfe9ce ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
