You are not logged in.

#1 2017-10-06 09:52:40

gmth
Member
Registered: 2015-09-15
Posts: 4

[SOLVED] Xorg only starts after a wayland session

Hi,

Since a week any Xorg DE/WM (tested KDE plasma5, gnome, i3wm) will not start , but instead freeze my laptop. When starting from a TTY, the freeze happens when the Xorg messages on the TTY are still visible. I cannot change TTYs, nor does my laptop respond to the power button: I have to long-press to force shutdown. REISUB didn't work, maybe because it is not compiled into the default kernel, or because I did something wrong.

However, when I first start Sway (Wayland, works fine), I can then successfully start any X DE/WM. I can do this in a different TTY with Sway still running, or I can close Sway and start a new session in the same TTY.
Xorg will then only freeze immediately after wakeup. At this point I cannot switch TTYs, but I can move the mouse.

The Xorg logs of a successfully started session and a freezing session are identical, except the "Loader magic".
I checked this by removing all timestamps and doing a 'diff' on the two.

Journalctl after login, starting a freezing Xorg session and pressing the power button to force shutdown:

Oct 06 10:32:40 thinkpad-arch login[382]: LOGIN ON tty1 BY thijs
Oct 06 10:32:40 thinkpad-arch systemd[731]: Listening on GnuPG network certificate management daemon.
Oct 06 10:32:40 thinkpad-arch systemd[731]: Listening on Sound System.
Oct 06 10:32:40 thinkpad-arch NetworkManager[339]: <info>  [1507278760.2760] device (wlp4s0): supplicant 
Oct 06 10:32:40 thinkpad-arch systemd[731]: Listening on D-Bus User Message Bus Socket.
Oct 06 10:32:40 thinkpad-arch systemd[731]: Reached target Sockets.
Oct 06 10:32:40 thinkpad-arch systemd[731]: Reached target Basic System.
Oct 06 10:32:40 thinkpad-arch systemd[731]: Starting Update XDG user dir configuration...
Oct 06 10:32:40 thinkpad-arch NetworkManager[339]: <info>  [1507278760.2811] device (wlp4s0): supplicant 
Oct 06 10:32:40 thinkpad-arch systemd[731]: Started Update XDG user dir configuration.
Oct 06 10:32:40 thinkpad-arch systemd[731]: Reached target Default.
Oct 06 10:32:40 thinkpad-arch systemd[731]: Startup finished in 30ms.
Oct 06 10:32:40 thinkpad-arch systemd[1]: Started User Manager for UID 1000.
Oct 06 10:33:37 thinkpad-arch NetworkManager[339]: <info>  [1507278817.3778] device (wlp4s0): supplicant 
Oct 06 10:34:17 thinkpad-arch dbus[286]: [system] Rejected send message, 0 matched rules; type="error", s
Oct 06 10:34:18 thinkpad-arch dbus[286]: [system] Rejected send message, 0 matched rules; type="error", s
Oct 06 10:34:18 thinkpad-arch dbus[286]: [system] Rejected send message, 0 matched rules; type="error", s
Oct 06 10:34:18 thinkpad-arch dbus[286]: [system] Rejected send message, 0 matched rules; type="error", s
Oct 06 10:34:18 thinkpad-arch dbus[286]: [system] Rejected send message, 0 matched rules; type="error", s
Oct 06 10:34:18 thinkpad-arch dbus[286]: [system] Rejected send message, 0 matched rules; type="error", s
Oct 06 10:34:18 thinkpad-arch dbus[286]: [system] Rejected send message, 0 matched rules; type="error", s
Oct 06 10:34:18 thinkpad-arch dbus[286]: [system] Rejected send message, 0 matched rules; type="error", s
Oct 06 10:34:18 thinkpad-arch dbus[286]: [system] Rejected send message, 0 matched rules; type="error", s
Oct 06 10:34:18 thinkpad-arch kernel: DMAR: DRHD: handling fault status reg 2
Oct 06 10:34:18 thinkpad-arch kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 8a1000 [fault
Oct 06 10:34:18 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:21 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:21 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:21 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:22 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:22 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:22 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:22 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:22 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:22 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:22 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:22 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:22 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:23 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:24 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:24 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f
Oct 06 10:34:24 thinkpad-arch kernel: [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for f

As far as I can see, none of these two help any further. Where can I find logs of what might be happening? Do any of you know what is going on, or what information would you need to find out?

Hardware:
Lenovo Thinkpad L450,
CPU: i5-5200
Intel integrated HD graphics 5500

Thanks!

Last edited by gmth (2017-10-06 10:51:28)

Offline

#2 2017-10-06 10:33:51

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,248

Re: [SOLVED] Xorg only starts after a wayland session

Oct 06 10:34:18 thinkpad-arch kernel: DMAR: DRHD: handling fault status reg 2
Oct 06 10:34:18 thinkpad-arch kernel: DMAR: [DMA Write] Request device [00:02.0] fault addr 8a1000 [fault

https://bbs.archlinux.org/viewtopic.php?id=230362

Although it is strange that this works from after a Wayland start. But maybe the freeze just happens later then. Either way likely to be an iommu issue.

Last edited by V1del (2017-10-06 10:35:04)

Offline

#3 2017-10-06 10:49:32

gmth
Member
Registered: 2015-09-15
Posts: 4

Re: [SOLVED] Xorg only starts after a wayland session

That did it!
I should have seen that, and I had looked at that post even.. Assumed that was part of me pressing the power button.
Thanks a bunch though, that  was way easier than I thought

Offline

Board footer

Powered by FluxBB