FS#46940 - [gdm] does not start on random boots

Attached to Project: Arch Linux
Opened by Ales Katona (almindor) - Sunday, 01 November 2015, 15:51 GMT
Last edited by Jan Alexander Steffens (heftig) - Thursday, 05 November 2015, 00:02 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Boot hangs (not freezes just doesn't seem to start gdm) at random. 1/4 boots or so just end with systemd text messages, generally with no errors or errors which are present even in cases where boot works fine. Not sure if it's stuck at starting gdm or something else. Attached two boot logs via journalctl -b. If there are other logs to get please advise. The computer works ok when the boot hangs like this, I can go to a text tty, the disk is mounted rw and everything else seems to be working fine. It just doesn't start X/gdm.

Additional info:
* linux kernel 4.2.5-1
* gnome/gdm v3.18.0-1 using X (wayland is set to false due to nvidia)
* nvidia proprietary driver v355.11-4 (geforce gtx 660)
* journalctl -b two incidents attached

Steps to reproduce:
Reboot and hope for it to happen, didn't find a trigger for it yet.
   badboot.txt (102.8 KiB)
   badboot2.txt (105 KiB)
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Thursday, 05 November 2015, 00:02 GMT
Reason for closing:  None
Comment by Doug Newgard (Scimmia) - Sunday, 01 November 2015, 21:45 GMT
Sounds like a known race condition with the nvidia drivers.
https://wiki.archlinux.org/index.php/NVIDIA#Blackscreen_at_X_startup_with_new_driver

Edit: Could also be a wayland issue, try disabling it in GDM. There are a couple of bug reports about this already.
Comment by Ales Katona (almindor) - Monday, 02 November 2015, 02:01 GMT
Looking into the two options mentioned. I am already running gdm with wayland off.

Is there any upstream/bugrep about this nvidia-specific problem anywhere?
Comment by Ales Katona (almindor) - Tuesday, 03 November 2015, 16:06 GMT
Seems that the two workaround (load model and kernel param) don't fix this for me. NOTE: I'm NOT on optimus/2 cards. I disabled it in BIOS and use the nvidia exclusively.

Attached the latest case journalctl -b output. Is there any other log I should have a look at? I don't see any errors in the journalctl one.
   badboot3.txt (104.2 KiB)
Comment by Jan Alexander Steffens (heftig) - Tuesday, 03 November 2015, 16:25 GMT
Wayland isn't deactivated:
nov 03 09:02:22 SHODAN gnome-session-binary[522]: WARNING: Application 'gnome-shell-wayland.desktop' killed by signal 5
Comment by Ales Katona (almindor) - Tuesday, 03 November 2015, 17:35 GMT
Hmm turns out I have a .pacsave version of the config so I guess pacman overrode my disable...

Does it do it silently? Anyway disabled now and will retry to ensure it's caused by this.
Comment by Ales Katona (almindor) - Wednesday, 04 November 2015, 23:57 GMT
I didn't get this to happen since the config change, so it might be "fixed/workaround-ed". Feel free to close this bug, if it happens again and I'm 100% positive wayland is turned off I'll reopen with a new log.

Loading...