You are not logged in.
I switched over to Arch from Mac about 2 months ago. Still feeling my way a bit, but so far I'm loving it. I've just hit a problem that I'm not sure how to diagnose...
I have an Arch installation running Gnome 3 (gnome-shell 3.26.1+6+g78d58deb5-1) on a Thinkpad X1 Carbon (5th Gen) connected to a Thinkpad Thunderbolt 3 dock. I have two external monitors connected to the dock, one via HDMI, one via VGA. The whole setup works perfectly, except for one weird problem:
First thing in the day I wake the laptop from sleep (or hibernate, or whatever the correct term is...), log in to Gnome, connect the Thunderbolt 3 dock, and the screen goes black. The only way I've found to get out of it is a hard reboot. On reboot, everything works fine for the rest of the day, until the problem re-occurs first thing next morning.
I've looked at crash logs (using journalctl), and there are a lot of errors and failures from xhci_hcd, colord, gnome-shell, gsd-color, kernel and org.gnome.Shell.desktop leading up to a 'Connection to xwayland lost' message preceding my reboot. I'm not quite sure how to diagnose this problem... Could someone point me in the right direction?
Other possibly useful info: On connecting to new external displays, I've had both gnome-shell (Wayland) crashes, requiring a reboot, and entire system crashes (reboots on its own!). I didn't have time to look at the logs when this happened (was giving a presentation...), but this isn't ideal!
Thanks.
Offline
Happened again this morning, right on schedule. Any pointers really appreciated, even if it's just 'you're posting on the wrong forum'!
My journalctl output from this morning (immediately preceding reboot) contains 437 lines of this:
Oct 25 09:18:57 [COMPUTER_NAME] kernel: [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns
Oct 25 09:18:57 [COMPUTER_NAME] kernel: [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit
A bit of googling shows up some bug reports logged with both freedesktop and Ubuntu, but all seem to be tagged as fixed.
What's really confusing me here is the timing of it - it only happens first thing in the day!
Any pointers appreciated.
Offline
Have you tried completely shutting down the laptop at night and then cold booting in the morning? Maybe sleep or hibernate has a bug affecting you.
Offline
Thanks for the suggestion!
Restarting prior to first connection of the day does indeed solve the issue. Weird thing is that multiple sleep/wake cycles in the day *doesn't* cause the problem. Seems specifically related to first connection each day, which is really confusing me!
Trying to understand the underlying cause of this, rather than just a work-around.
Last edited by oscarbranson (2017-10-25 03:39:30)
Offline
1st things first: sleep or hibernate ("sleep to disk")? (In doubt paste a complete journal including such sleep/hibernation)
2nd: is it time-wrap related (can you try sleeping at ~23:50 and wake it up at ~00:10) or duration related (because the overnight sleep is probably the longest nap it takes)
3rd: dual boot installation (ie. also a windows installation?)
4th: "only way I've found to get out of it is a hard reboot" - did you try switching to another VT (ctrl+alt+f1/2/3/4/...) and can you start sshd and attempt to ssh into the notebook?
Offline
Thanks Seth!
1st things first: sleep or hibernate ("sleep to disk")? (In doubt paste a complete journal including such sleep/hibernation)
Suspend to RAM (systemctl suspend)
2nd: is it time-wrap related (can you try sleeping at ~23:50 and wake it up at ~00:10) or duration related (because the overnight sleep is probably the longest nap it takes)
I don't tend to be at work (where my dock is) around midnight... but will try to test this next week.
3rd: dual boot installation (ie. also a windows installation?)
Single boot Arch.
4th: "only way I've found to get out of it is a hard reboot" - did you try switching to another VT (ctrl+alt+f1/2/3/4/...) and can you start sshd and attempt to ssh into the notebook?
Unable to switch to another VT (doesn't respond to keypresses), don't have a second computer to be able to try the ssh... can try to find one if this is essential?
Last edited by oscarbranson (2017-10-26 01:41:47)
Offline
Not for your specific hardware but possibly related:
https://wiki.archlinux.org/index.php/De … lt_3_Docks
Thunderbolt has issues on Linux in my experience. You might be able to find a BIOS update for your system to fix it. Otherwise I would just shutdown instead of sleep.
Offline
Doing that at the dock should not be becessary - just send it to sleep across midnight (I guess you take it home?) and then keep it running (on AC so it doesn't run out of battery) to the next day. Also ensure to dump a complete dmesg after a critical S3 cycle, but of course before causing the crash.
What could happen is some decay in relevant volatile memory (usually not RAM but some dedicated GPU memory or so) during a longer S3
Offline
Moved to a new thread, as nature of problem has changed significantly.
Last edited by oscarbranson (2018-03-09 08:43:02)
Offline