You are not logged in.
Pages: 1
Topic closed
I installed arch on a dell XPS 9350, and things mostly work well. The touchscreen was not working after suspend, so -- following the wiki -- I installed xf86-input-libinput instead of xf86-input-synaptics, hoping this would fix the issue.
Immediately, the laptop would not suspend, but seems to shut down completely. It suspended seamlessly before. When I close the lid, or call systemctl suspend, opening the lid or pressing the power button makes the laptop boot instead of resume. There were other reports of laptops shutting down a few seconds after resume, but this is instantaneous, so I suspect the laptop shuts down when suspend is called. There is no LED to indicate sleep, so I do not know if it is sleeping or shut off.
I'm really not sure how to go about figuring this out. I will try to revert to xf86-input-synaptics.
output of journalctl -b -1:
-- Logs begin at Sun 2015-12-27 22:23:03 PST, end at Wed 2016-01-13 21:53:25 PST. --
Jan 13 21:52:19 skvader systemd[467]: Reached target Paths.
Jan 13 21:52:19 skvader systemd[467]: Starting D-Bus User Message Bus Socket.
Jan 13 21:52:19 skvader systemd[467]: Reached target Timers.
Jan 13 21:52:19 skvader systemd[467]: Listening on D-Bus User Message Bus Socket.
Jan 13 21:52:19 skvader systemd[467]: Reached target Sockets.
Jan 13 21:52:19 skvader systemd[467]: Reached target Basic System.
Jan 13 21:52:19 skvader systemd[467]: Reached target Default.
Jan 13 21:52:19 skvader systemd[467]: Startup finished in 19ms.
Jan 13 21:52:19 skvader systemd[467]: Started D-Bus User Message Bus.
Jan 13 21:52:19 skvader dbus-daemon[484]: Activating service name='org.xfce.Xfconf'
Jan 13 21:52:19 skvader dbus-daemon[484]: Successfully activated service 'org.xfce.Xfconf'
Jan 13 21:52:20 skvader dbus-daemon[484]: Activating service name='org.freedesktop.thumbnails.Thumbnailer1'
Jan 13 21:52:20 skvader org.freedesktop.thumbnails.Thumbnailer1[484]: (tumblerd:525): tumbler-WARNING **: Failed to load plugin "tumbler-ffmpeg-thumbnailer.so": libffmpegthumbnailer.so.4: cannot open shared object file: No such file or directory
Jan 13 21:52:20 skvader org.freedesktop.thumbnails.Thumbnailer1[484]: (tumblerd:525): tumbler-WARNING **: Failed to load plugin "tumbler-odf-thumbnailer.so": libgsf-1.so.114: cannot open shared object file: No such file or directory
Jan 13 21:52:20 skvader org.freedesktop.thumbnails.Thumbnailer1[484]: (tumblerd:525): tumbler-WARNING **: Failed to load plugin "tumbler-poppler-thumbnailer.so": libpoppler-glib.so.8: cannot open shared object file: No such file or directory
Jan 13 21:52:20 skvader org.freedesktop.thumbnails.Thumbnailer1[484]: (tumblerd:525): tumbler-WARNING **: Failed to load plugin "tumbler-raw-thumbnailer.so": libopenrawgnome.so.1: cannot open shared object file: No such file or directory
Jan 13 21:52:20 skvader dbus-daemon[484]: Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Jan 13 21:52:20 skvader dbus-daemon[484]: Activating service name='org.freedesktop.Notifications'
Jan 13 21:52:20 skvader dbus-daemon[484]: Successfully activated service 'org.freedesktop.Notifications'
Jan 13 21:52:20 skvader dbus-daemon[484]: Activating service name='org.a11y.Bus'
Jan 13 21:52:20 skvader dbus-daemon[484]: Successfully activated service 'org.a11y.Bus'
Jan 13 21:52:20 skvader org.a11y.Bus[484]: Activating service name='org.a11y.atspi.Registry'
Jan 13 21:52:20 skvader org.a11y.Bus[484]: Successfully activated service 'org.a11y.atspi.Registry'
Jan 13 21:52:20 skvader org.a11y.atspi.Registry[576]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jan 13 21:52:20 skvader pkexec[588]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
Offline
Reverting to xf86-input-synaptics made no difference.
any tips would be appreciated.
Offline
The problem seems to have vanished, and I have not done anything that I can think of as related.
I tried booting into an older kernel (4.2) I have installed, which did not work, but afterwards booting into 4.4 suspend seems to be working fine. (I did not keep track, it might have taken another boot cycle after that).
I have no idea what caused the problem, and what made it go away, which is not a good state of affairs, but at least I can suspend now.
Offline
Maybe the problem has been sorted with the 4.4 kernel. But, 4.4 is in testing, so are you using the testing repo?
Moving to "Laptop Issues".
Offline
On my XPS 13 9350 I'm facing this problem: on resume action it start from boot. We can't know if it goes on sleep or shutdown for missing led status. I'm on kernel 4.4 from testing.
This is the output of 'journalctl -b -1':
gen 24 00:45:32 nagzul NetworkManager[510]: <info> NetworkManager state is now ASLEEP
gen 24 00:45:33 nagzul wpa_supplicant[986]: nl80211: deinit ifname=p2p-dev-wlp58s0 disabled_11b_rates=0
gen 24 00:45:33 nagzul NetworkManager[510]: <warn> Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.
gen 24 00:45:33 nagzul dbus[503]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
gen 24 00:45:33 nagzul gnome-session[1757]: Gjs-Message: JS LOG: An active wireless connection, in infrastructure mode, involves no access point?
gen 24 00:45:33 nagzul wpa_supplicant[986]: nl80211: deinit ifname=wlp58s0 disabled_11b_rates=0
gen 24 00:45:33 nagzul systemd[1]: Starting TLP suspend/resume...
gen 24 00:45:33 nagzul systemd[1]: Starting Network Manager Script Dispatcher Service...
gen 24 00:45:33 nagzul dbus[503]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
gen 24 00:45:33 nagzul systemd[1]: Started Network Manager Script Dispatcher Service.
gen 24 00:45:33 nagzul nm-dispatcher[5039]: Dispatching action 'down' for wlp58s0
gen 24 00:45:33 nagzul systemd[1]: Stopping Network Time Service...
gen 24 00:45:33 nagzul ntpd[674]: ntpd exiting on signal 15 (Terminated)
gen 24 00:45:33 nagzul ntpd[674]: 192.71.245.44 local addr 192.168.1.105 -> <null>
gen 24 00:45:33 nagzul ntpd[674]: 212.45.144.206 local addr 192.168.1.105 -> <null>
gen 24 00:45:33 nagzul ntpd[674]: 212.45.144.88 local addr 192.168.1.105 -> <null>
gen 24 00:45:33 nagzul ntpd[674]: 62.48.53.90 local addr 192.168.1.105 -> <null>
gen 24 00:45:33 nagzul tlp[5038]: Error: TLP power save is disabled. Set TLP_ENABLE=1 in /etc/default/tlp.
gen 24 00:45:33 nagzul systemd[1]: tlp-sleep.service: Main process exited, code=exited, status=1/FAILURE
gen 24 00:45:33 nagzul systemd[1]: Failed to start TLP suspend/resume.
gen 24 00:45:33 nagzul systemd[1]: tlp-sleep.service: Unit entered failed state.
gen 24 00:45:33 nagzul systemd[1]: tlp-sleep.service: Failed with result 'exit-code'.
gen 24 00:45:33 nagzul systemd[1]: Reached target Sleep.
gen 24 00:45:33 nagzul systemd[1]: Starting Suspend...
gen 24 00:45:33 nagzul systemd-sleep[5047]: Suspending system...
Offline
any hint!?
Offline
I have this problem on 4.5 as well.
Offline
This occurred last night on my FHD 9350 with 4.6.1-2-ARCH as well.
Currently running Arch on a Samsung Chromebook Pro (dual booted with ChromeOS), and various VPSes and Docker containers.
Offline
Same problem here. (using kernel backend for suspend, I've never had a problem with `systemctl suspend` or `systemctl hibernate` on systemd 229, and core/linux (4.5.x) and testing/linux (4.6.x) until today, when the kernel became core/linux (4.6.1-2))
iv597 - I just updated to 4.6.1-2-ARCH, and systemd 230 took effect during this upgrade, too. I have the non-FHD 9350.
diraimondo - This is essentially exactly what I'm getting. It's impossible to debug. My logs for -1 boot end with "Suspending system...", then my logs for 0 boot are simply a normal startup. The only indication that something went wrong is a journal fix when I mount my / partition.
I have a feeling that this is a systemd 230 issue. Only because I was running 4.6.1-1 out of the testing repositories for about a week before it made it to core. That said, testing is -1, and core is -2, which may have made the difference.
More than happy to provide any information I can, please let me know in this thread.
Edit: I've had the same experience as angelo. After maybe 3-4 reboots and leaving my machine shut down for a number of hours, it now appears to be suspending without incident. This is incredibly strange and I'll be keeping my eyes on the logs for anything untoward.
Last edited by big_billy (2016-06-09 07:17:33)
I use and troubleshoot Arch Linux on a Dell XPS 9350.
Offline
Edit: I've had the same experience as angelo. After maybe 3-4 reboots and leaving my machine shut down for a number of hours, it now appears to be suspending without incident. This is incredibly strange and I'll be keeping my eyes on the logs for anything untoward.
Precisely same issue with Skylake XPS 9350 (QHD model) with Ubuntu 16.04 LTS on Kernel 4.6.0
journalctl reported suspending but upon opening the lid the laptop started cold booting.
After shutting down the OS properly, I was able to suspend again.
Very strange problem and really hard to diagnose as logs are not helpful.
Offline
I've been having this issue intermittenly as I change kernel each week on the mainline rcs. Since moving to drm intel nightly I haven't seen this behavior, *crosses fingers*, yet. dell xps 13 9350. Today is day 3 and all suspends are working as normal.
Edit: spoke too soon, I am experiencing this once again.
Edit1: Ok, strange. Suspend works fine when on AC. Suspend experiences the sudden shutdown when on battery.
Last edited by frank604 (2016-06-10 13:59:22)
Offline
Similar issues as reported (Dell 7370 - Skylake) suspend stopped working today. Had a suspend error yesterday which I predict is what started this. I've had this happen a week ago or so in that suspend stopped working.
Both times I couldn't get it to properly suspend until I issued a shutdown, after which, suspend started working again.
Offline
Hi all,
Could this be related to the Intel Rapid Start Technology (IRST) those laptops have? This feature is supposed to copy you RAM on a "Special Partition" on the drive if you stay suspended for to long, and then shut down. On boot, it should just copy back your RAM from the Special Partition and resume as if nothing happened. It could be that something goes wrong if the BIOS does not find the suitable "Special Partition"...
Maybe there is a way to just disable this IRST in BIOS and see if the issue still occurs. Alternatively, one could want that IRST up and running. It needs a new partitioning scheme though... Here are posts where people set it up: http://ubuntuforums.org/showthread.php?t=2117166 or http://blog.adios.tw/2012/10/funtoo-lin … start.html.
Also, does anyone knows when the laptop goes from suspended to shut down? Is it something like "right after suspension"? Something like "one hour after suspension"? Something like "when battery is depleted"? Something completely random?
Offline
@kihanos, it does not fully suspend. System starts the suspend as in @diraimondo's post
gen 24 00:45:33 nagzul systemd[1]: Reached target Sleep.
gen 24 00:45:33 nagzul systemd[1]: Starting Suspend...
gen 24 00:45:33 nagzul systemd-sleep[5047]: Suspending system...
but never fully reaches a sleep state. Instead it acts as if forcing a power off.
Offline
@frank604
yeah sure, but that's also the output I get in journalctl after a normal suspension (and wake up)
juin 12 13:10:59 dromadouh systemd[1]: Reached target Sleep.
juin 12 13:10:59 dromadouh systemd[1]: Starting Suspend...
juin 12 13:10:59 dromadouh systemd-sleep[5297]: Suspending system...
juin 13 08:42:38 dromadouh kernel: PM: Syncing filesystems ... done.
juin 13 08:42:38 dromadouh kernel: PM: Preparing system for sleep (mem)
Note that the last two lines, although probably executed before going into S3, are only logged on wake up (so you never get them if you never wake up).
It could still be that the kernel finishes its suspension and leaves it to the firmware to go to sleep mode (and somewhat fails).
Offline
Anecdotally, I think that some systems might be plagued by firmware level issues. On the Dell 7370 I noticed that I have suspend issue a lot less after I updated to the most recent firmware (BIOS).
Offline
I actually had the same problem on XPS 13 and simply shutting down and turning it on again fixed the problem.
Offline
Could you please try, and report the results, for the potential fix listed in post #9 here:
https://bbs.archlinux.org/viewtopic.php?id=214023
Halocaridina
4X Intel(R) Xeon(R) CPU E7-8870 @ 2.40GHz; 256GiB; 11TB EXT4; SL6.8
2X Intel(R) Xeon(R) CPU E5-2680 @ 2.70GHz; 256GiB; 3.4TB EXT4; SL6.8
Thinkpad X250; Broadwell-ULT Core i5; 8GiB, 525GB Crucial_CT525MX3; Arch
Thinkpad T440S; Haswell-ULT Core i7; 12GiB, 512GB SanDisk X210; Arch
Offline
I'm facing the very same problem (Asus UX305CA Intel m3-6Y30 Skylake), but pretty randomly till this Monday. Every time I'm under the assumption that I put it to "sleep" it actually force shutdown. I have no clue what is behind it, but today after reading this post I tried to do the same from cli with systemctl (systemctl suspend) and that actually worked... since that it works properly even with the power button and lid closing. Yet again not sure why it works now and for how long it will last also not sure why it isn't working in the first place.
Offline
I didn't encounter this issue until a moment ago. I did an update using "sudo pacman -Syu" yesterday, but not sure whether it is a consequence of the update.
However, the system is restarted when resuming from suspension, ONLY IF my laptop (ASUS X550JX Intel i7-4720HQ) is connected to an external monitor.
UPDATE: It seems to be a problem resulted from the particular monitor, since everything works fine with another monitor. Still, I would like to figure out the cause.
Last edited by htcai (2018-05-31 18:35:01)
Offline
My Dell XPS 13 (9350) just recently is experiencing this exact issue. Still no clue why.
Offline
Stop necrobumping...
I'm not a mod tho
NZ - UTC+12, or UTC+13 (depends on DST) | HP ENVY x360 2-in-1 Laptop 15-EW0009TX
Offline
You can use the report button to report necrobumps .
That said I agree, if you want to actually look at your current system, make a new thread, describe the exact issues and check/post journal logs from a faulty sleep attempt.
Closing this old topic.
Offline
Pages: 1
Topic closed