[solved] system unresponsive after update and fails to boot into gnome

qbic2005 · 2016-10-24 17:08:38

Hello guys

Since my last update, my system is unresponsive and fails to boot 4/5 times.

If the system does not boot, last message on terminal is "Reached target graphical interface".
I'm unable to switch vt, so only rescue is hard reset from this state.
From Xorg.1.log comparison with Xorg.0.log (from the 1/5 good boot attempts), only difference is :

++ in Xorg.0.log at end of file
[ 23.524] (II) systemd-logind: got pause for 13:65

Same system if booted (1/5) becomes unresponsive randomly, between 5min and an hour of being operational.
With unresponsive I mean, usually in this order: interlacing desktop when moving mouse, keyboard input pauzes, mouse and keyboard input fails and eventually gnome halts completely, however TOP shows low CPU usage, mem is not the problem, interrupts count are not excessive.
Hardware is not the issue (windows runs just fine), DMESG does not shown anything strange either.

Both kernel and nvidia driver have been updated on last update

uname -a
Linux maximusvgene 4.8.4-1-ARCH #1 SMP PREEMPT Sat Oct 22 18:26:57 CEST 2016 x86_64 GNU/Linux

nvidia-smi
Mon Oct 24 18:55:52 2016       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 370.28                 Driver Version: 370.28                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 650 Ti  Off  | 0000:01:00.0     N/A |                  N/A |
| 22%   34C    P0    N/A /  N/A |    259MiB /   978MiB |     N/A      Default |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0                  Not Supported                                         |
+-----------------------------------------------------------------------------+

Tried to boot the previous kernel from grub, but it fails. I can try to uninstall nvidia and install nouveau ... but what then??? I can't live without the proprietary drivers ... already tried reinstalling nvidia+utils.

Does anybody have a clue what else I can do? (before reinstalling the entire g-z-a-c-h-a-b-a-n-g)
Any ideas welcome

thank you for reading

Last edited by qbic2005 (2016-10-30 18:24:09)

Head_on_a_Stick · 2016-10-24 17:41:33

Is there anything written to the journal after the failed boot?

Does the system boot reliably if you switch to the non-proprietary driver?

seth · 2016-10-24 21:08:28

What's your graphical DM and which kind of session do you run? Gnome on wayland? (No idea whether that already works at all with the nvidia blob, but there might be extra trouble)

qbic2005 · 2016-10-25 16:51:15

@Head_on_a_Stick : nothing to special that I can see.

[root@ant-16 /]# journalctl -xe -p err..alert
Oct 24 21:17:45 maximusvgene ntpd[454]: unable to create socket on eno1 (4) for fe80::7064:b366:d2de:6931%2#123
Oct 24 21:18:00 maximusvgene gdm[461]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
-- Reboot --
Oct 24 21:21:02 maximusvgene kernel: sd 8:0:0:0: [sdc] No Caching mode page found
Oct 24 21:21:02 maximusvgene kernel: sd 8:0:0:0: [sdc] Assuming drive cache: write through
Oct 24 21:21:02 maximusvgene systemd[1]: [/usr/lib/systemd/system/dropbox@.service:3] Failed to add dependency on systemd-user-sessions, ignoring: Invalid argument
Oct 24 21:21:02 maximusvgene systemd-modules-load[205]: Failed to find module 'vboxdrv'
Oct 24 21:21:02 maximusvgene systemd-modules-load[205]: Failed to find module 'vboxnetadp'
Oct 24 21:21:02 maximusvgene systemd-modules-load[205]: Failed to find module 'vboxnetflt'
Oct 24 21:21:02 maximusvgene systemd-modules-load[205]: Failed to find module 'vboxpci'
Oct 24 21:21:02 maximusvgene systemd-modules-load[331]: Failed to find module 'vboxdrv'
Oct 24 21:21:02 maximusvgene systemd-modules-load[331]: Failed to find module 'vboxnetadp'
Oct 24 21:21:02 maximusvgene systemd-modules-load[331]: Failed to find module 'vboxnetflt'
Oct 24 21:21:02 maximusvgene systemd-modules-load[331]: Failed to find module 'vboxpci'
Oct 24 21:21:02 maximusvgene systemd[1]: Failed to start Setup Virtual Console.
-- Subject: Unit systemd-vconsole-setup.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-vconsole-setup.service has failed.
-- 
-- The result is failed.
Oct 24 21:21:02 maximusvgene systemd[1]: Failed to start Load Kernel Modules.
-- Subject: Unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-modules-load.service has failed.
-- 
-- The result is failed.
Oct 24 21:21:02 maximusvgene kernel: kvm: disabled by bios
Oct 24 21:21:03 maximusvgene kernel: kvm: disabled by bios
Oct 24 21:21:05 maximusvgene gnome-session-binary[474]: Unrecoverable failure in required component org.gnome.Shell.desktop
Oct 24 21:21:14 maximusvgene ntpd[436]: bind(25) AF_INET6 2a02:a03f:2cc3:8e00:787:daf5:7ccb:c3ed#123 flags 0x11 failed: Cannot assign requested address
Oct 24 21:21:14 maximusvgene ntpd[436]: unable to create socket on eno1 (6) for 2a02:a03f:2cc3:8e00:787:daf5:7ccb:c3ed#123
-- Reboot --
Oct 24 21:22:17 maximusvgene systemd[1]: [/usr/lib/systemd/system/dropbox@.service:3] Failed to add dependency on systemd-user-sessions, ignoring: Invalid argument
Oct 24 21:22:17 maximusvgene systemd-modules-load[196]: Failed to find module 'vboxdrv'
Oct 24 21:22:17 maximusvgene systemd-modules-load[196]: Failed to find module 'vboxnetadp'
Oct 24 21:22:17 maximusvgene systemd-modules-load[196]: Failed to find module 'vboxnetflt'
Oct 24 21:22:17 maximusvgene systemd-modules-load[196]: Failed to find module 'vboxpci'
Oct 24 21:22:21 maximusvgene gnome-session-binary[458]: Unrecoverable failure in required component org.gnome.Shell.desktop
-- Reboot --
Oct 24 21:59:22 maximusvgene systemd[1]: [/usr/lib/systemd/system/dropbox@.service:3] Failed to add dependency on systemd-user-sessions, ignoring: Invalid argument
Oct 24 21:59:22 maximusvgene systemd-modules-load[200]: Failed to find module 'vboxdrv'
Oct 24 21:59:22 maximusvgene systemd-modules-load[200]: Failed to find module 'vboxnetadp'
Oct 24 21:59:22 maximusvgene systemd-modules-load[200]: Failed to find module 'vboxnetflt'
Oct 24 21:59:22 maximusvgene systemd-modules-load[200]: Failed to find module 'vboxpci'
Oct 24 21:59:23 maximusvgene kernel: kvm: disabled by bios
Oct 24 21:59:25 maximusvgene gnome-session-binary[476]: Unrecoverable failure in required component org.gnome.Shell.desktop
Oct 24 21:59:28 maximusvgene ntpd[443]: bind(23) AF_INET6 fe80::7064:b366:d2de:6931%2#123 flags 0x11 failed: Cannot assign requested address
Oct 24 21:59:28 maximusvgene ntpd[443]: unable to create socket on eno1 (4) for fe80::7064:b366:d2de:6931%2#123
Oct 24 21:59:59 maximusvgene gdm[446]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
-- Reboot --
Oct 25 17:19:47 maximusvgene kernel: sd 8:0:0:0: [sdc] No Caching mode page found
Oct 25 17:19:47 maximusvgene kernel: sd 8:0:0:0: [sdc] Assuming drive cache: write through
Oct 25 17:19:47 maximusvgene systemd[1]: [/usr/lib/systemd/system/dropbox@.service:3] Failed to add dependency on systemd-user-sessions, ignoring: Invalid argument
Oct 25 17:19:47 maximusvgene systemd-modules-load[184]: Failed to find module 'vboxdrv'
Oct 25 17:19:47 maximusvgene systemd-modules-load[184]: Failed to find module 'vboxnetadp'
Oct 25 17:19:47 maximusvgene systemd-modules-load[184]: Failed to find module 'vboxnetflt'
Oct 25 17:19:47 maximusvgene systemd-modules-load[184]: Failed to find module 'vboxpci'
lines 2571-2631/2631 (END)

Full system.journal

I kicked virtualbox out of the installation after the problem emerged, trying to solve this. (clearly not in the right direction, so don't mind the vbox errors)

Last edited by qbic2005 (2016-10-25 17:02:23)

qbic2005 · 2016-10-25 16:54:44

@Seth: GDM, Gnome shell, wayland - euh, need to check, guess I do ... probably something pulled it in, cause I have no memory installing this manually.

yaourt -Ss wayland | grep installed
extra/wayland 1.12.0-1 [installed]
extra/wayland-protocols 1.7-1 [installed]
extra/xorg-server-xwayland 1.18.4-1 (xorg) [installed]
multilib/lib32-wayland 1.12.0-1 [installed]

But then again, it worked fine before the latest update (I follow updates weekly).

Any reason in particular why I should not run wayland with the latest nvidia drivers?

qbic2005 · 2016-10-25 17:10:27

Installed nouveau driver now and kicked nvidia out, system started without issue 3x in a row, yeah

So culprit is Nvidia ... or Wayland ... or both ??

Any suggestions on how to proceed (and get nvidia back onto the system)?

Last edited by qbic2005 (2016-10-25 18:18:03)

seth · 2016-10-25 18:47:06

Whether you got wayland installed doesn't matter, but since tehe last update, gnome defaults to use it. I could imagine that there're (still) trouble with nvidias approach on the topic. You may check the output of "xrandr -q" to see whether this is currently a wayland session and try the nvidia blob along a "gnome on xorg" session. Or stay with nouveau if you don't care.

qbic2005 · 2016-10-25 21:36:04

@Seth: I don't care about the wayland functionality, I would just like to have Nvidia driver up and running as this station is used for gaming, video and foto editing ... , pure graphical performance is the most important in this case.

Not sure what I should look for in this log, I don't see any ref to wayland:

xrandr -q
Screen 0: minimum 320 x 200, current 3440 x 1440, maximum 16384 x 16384
VGA-1 disconnected (normal left inverted right x axis y axis)
DVI-D-1 disconnected (normal left inverted right x axis y axis)
DVI-D-2 disconnected (normal left inverted right x axis y axis)
HDMI-1 connected primary 3440x1440+0+0 (normal left inverted right x axis y axis) 798mm x 335mm
   3440x1440     49.99*+  29.99  
   2560x1440     59.95  
   2560x1080     60.00  
   1720x1440     60.00  
   1920x1080     60.00    50.00    59.94  
   1920x1080i    60.00    50.00    59.94  
   1600x1200     60.00  
   1280x1024     75.02    60.02  
   1280x800      59.91  
   1152x864      75.00  
   1280x720      60.00    50.00    59.94  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       75.00    60.00    59.94  
   720x400       70.08

I found the wayland/weston installation guide, but it left me guessing on the uninstall part. But then I don't even know if this is the way to go ...
Can I just disable wayland in the current gnome or will it break other stuff?
I never played with wayland so I'm a bit lost on what is the right step forward.

Thank you for your help so far!!

Head_on_a_Stick · 2016-10-25 21:55:29

To use GNOME without Wayland, click on the cog-wheel icon next to the login box in the display manager (login) screen and select "GNOME on Xorg" (or so, I don't use GNOME).

qbic2005 · 2016-10-30 17:17:11

@Head_on_a_stick : cannot do as GDM does not load

I reinstalled the entire system, some minor other problems now, but NVIDIA + GDM + GNOME works fine

thank you for the help.

jasonwryan · 2016-10-30 17:24:35

Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.

Arch Linux

#1 2016-10-24 17:08:38

[solved] system unresponsive after update and fails to boot into gnome

#2 2016-10-24 17:41:33

Re: [solved] system unresponsive after update and fails to boot into gnome

#3 2016-10-24 21:08:28

Re: [solved] system unresponsive after update and fails to boot into gnome

#4 2016-10-25 16:51:15

Re: [solved] system unresponsive after update and fails to boot into gnome

#5 2016-10-25 16:54:44

Re: [solved] system unresponsive after update and fails to boot into gnome

#6 2016-10-25 17:10:27

Re: [solved] system unresponsive after update and fails to boot into gnome

#7 2016-10-25 18:47:06

Re: [solved] system unresponsive after update and fails to boot into gnome

#8 2016-10-25 21:36:04

Re: [solved] system unresponsive after update and fails to boot into gnome

#9 2016-10-25 21:55:29

Re: [solved] system unresponsive after update and fails to boot into gnome

#10 2016-10-30 17:17:11

Re: [solved] system unresponsive after update and fails to boot into gnome

#11 2016-10-30 17:24:35

Re: [solved] system unresponsive after update and fails to boot into gnome

Board footer