boot not possible after upgrade fom Kernel 4.9.0 to Kernel 4.9.3

AxJHerVQ · January 22, 2017, 6:48pm

Hello all,

after a upgrade from Kernel 4.9.0-2 to Kernel 4.9.3-1 it isn’t possible to boot the machine. Symptom is the following: at the konsole (e.g. tty1) it isn’t possible to do an input, it seems to be restarting over and over again.

Here a snippet from the journalctl logging:


Jan 22 17:58:17 willnixWlan kernel: microcode: microcode updated early to revision 0x20, date = 2016-03-16
Jan 22 17:58:17 willnixWlan kernel: Linux version 4.9.3-1-debug (geeko@buildhost) (gcc version 6.2.1 20161209 [gcc-6-branch revision 243481] (SUSE Linux) ) #1 SMP Thu Jan 12 11:32:53 UTC 2017 (2c7dfab)
Jan 22 17:58:17 willnixWlan kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.3-1-debug root=UUID=71d36153-187f-4df6-8391-c123cc4112d8 resume=/dev/disk/by-uuid/f0087c95-02f8-4e28-8952-56b8de9055a7 splash=silent quiet showopts
Jan 22 17:58:17 willnixWlan kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jan 22 17:58:17 willnixWlan kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jan 22 17:58:17 willnixWlan kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jan 22 17:58:17 willnixWlan kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jan 22 17:58:17 willnixWlan kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Jan 22 17:58:17 willnixWlan kernel: x86/fpu: Using 'eager' FPU context switches.
.
.
.
Jan 22 17:58:22 willnixWlan sddm[1712]: Initializing...
Jan 22 17:58:22 willnixWlan sddm[1712]: Starting...
Jan 22 17:58:22 willnixWlan sddm[1712]: Adding new display on vt 7 ...
Jan 22 17:58:22 willnixWlan sddm[1712]: Display server starting...
Jan 22 17:58:22 willnixWlan sddm[1712]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{cec6f767-8dfe-47bd-a6d9-1b2b931e7962} -background none -noreset -displayfd 18 vt7
Jan 22 17:58:22 willnixWlan kernel: IPv4: martian source 255.255.255.255 from 192.168.178.1, on dev wlp4s1
Jan 22 17:58:22 willnixWlan kernel: ll header: 00000000: ff ff ff ff ff ff 24 65 11 05 3f be 08 00        ......$e..?...
Jan 22 17:58:22 willnixWlan sddm[1712]: Running display setup script  "/etc/X11/xdm/Xsetup"
Jan 22 17:58:22 willnixWlan sddm[1712]: Display server started.
Jan 22 17:58:22 willnixWlan sddm[1712]: Socket server starting...
Jan 22 17:58:22 willnixWlan sddm[1712]: Socket server started.
Jan 22 17:58:22 willnixWlan sddm[1712]: Greeter starting...
Jan 22 17:58:22 willnixWlan sddm[1712]: Adding cookie to "/run/sddm/{cec6f767-8dfe-47bd-a6d9-1b2b931e7962}"
Jan 22 17:58:22 willnixWlan display-manager[1589]: Starting service sddm/usr/bin/xauth: (stdin):1:  bad "remove" command line
Jan 22 17:58:22 willnixWlan display-manager[1589]: /usr/bin/xauth: (stdin):2:  bad "add" command line
Jan 22 17:58:22 willnixWlan sddm[1712]: Display server stopped.
Jan 22 17:58:22 willnixWlan sddm[1712]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Jan 22 17:58:22 willnixWlan sddm[1712]: Socket server stopping...
Jan 22 17:58:22 willnixWlan sddm[1712]: Socket server stopped.
Jan 22 17:58:22 willnixWlan sddm[1712]: Removing display "" ...
Jan 22 17:58:22 willnixWlan sddm[1712]: Adding new display on vt 7 ...
Jan 22 17:58:22 willnixWlan sddm[1712]: Display server starting...
Jan 22 17:58:22 willnixWlan sddm[1712]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{9da189ea-cba2-4603-bf80-d6dec39d5dfb} -background none -noreset -displayfd 20 vt7
Jan 22 17:58:22 willnixWlan sddm-helper[1728]: [PAM] Starting...
Jan 22 17:58:22 willnixWlan sddm-helper[1728]: [PAM] Authenticating...
Jan 22 17:58:22 willnixWlan sddm-helper[1728]: [PAM] returning.
Jan 22 17:58:22 willnixWlan display-manager[1589]: ..done
Jan 22 17:58:22 willnixWlan systemd[1]: Started X Display Manager.
Jan 22 17:58:22 willnixWlan sddm[1712]: Running display setup script  "/etc/X11/xdm/Xsetup"
Jan 22 17:58:22 willnixWlan sddm[1712]: Display server started.
Jan 22 17:58:22 willnixWlan sddm[1712]: Socket server starting...
Jan 22 17:58:22 willnixWlan sddm[1712]: Socket server started.
Jan 22 17:58:22 willnixWlan sddm[1712]: Greeter starting...
Jan 22 17:58:22 willnixWlan sddm[1712]: Adding cookie to "/run/sddm/{9da189ea-cba2-4603-bf80-d6dec39d5dfb}"
Jan 22 17:58:22 willnixWlan display-manager[1589]: /usr/bin/xauth: (stdin):1:  bad "remove" command line
Jan 22 17:58:22 willnixWlan display-manager[1589]: /usr/bin/xauth: (stdin):2:  bad "add" command line
Jan 22 17:58:22 willnixWlan sddm[1712]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Jan 22 17:58:22 willnixWlan sddm[1712]: Display server stopped.
Jan 22 17:58:22 willnixWlan sddm[1712]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Jan 22 17:58:22 willnixWlan sddm[1712]: Socket server stopping...
Jan 22 17:58:22 willnixWlan sddm[1712]: Socket server stopped.
Jan 22 17:58:22 willnixWlan sddm[1712]: Removing display "" ...
Jan 22 17:58:22 willnixWlan sddm[1712]: Adding new display on vt 7 ...
.
.
.
Jan 22 17:58:32 willnixWlan systemd[1]: Stopped Remount Root and Kernel File Systems.
Jan 22 17:58:32 willnixWlan systemd[1]: Reached target Shutdown.
Jan 22 17:58:32 willnixWlan systemd[1]: Starting /etc/init.d/halt.local Compatibility...
Jan 22 17:58:32 willnixWlan systemd[1]: Started /etc/init.d/halt.local Compatibility.
Jan 22 17:58:32 willnixWlan systemd[1]: Reached target Final Step.
Jan 22 17:58:32 willnixWlan systemd[1]: Starting Reboot...
Jan 22 17:58:32 willnixWlan systemd[1]: Shutting down.
Jan 22 17:58:32 willnixWlan umount[3314]: umount: /var/log: target is busy
Jan 22 17:58:32 willnixWlan umount[3314]: (In some cases useful info about processes that
Jan 22 17:58:32 willnixWlan umount[3314]: use the device is found by lsof(8) or fuser(1).)
Jan 22 17:58:32 willnixWlan systemd[1]: Hardware watchdog 'iTCO_wdt', version 0
Jan 22 17:58:32 willnixWlan kernel: watchdog: watchdog0: watchdog did not stop!
Jan 22 17:58:32 willnixWlan systemd[1]: Set hardware watchdog to 10min.
Jan 22 17:58:32 willnixWlan systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Jan 22 17:58:32 willnixWlan haveged[648]: haveged: Stopping due to signal 15
Jan 22 17:58:32 willnixWlan haveged[648]: haveged starting up
Jan 22 17:58:32 willnixWlan systemd-journald[506]: Journal stopped

The only possibility to come to a running system is to fall back on the installation with teh previous kernel.

Any help is appreciated

keellambert · January 24, 2017, 6:48pm

Leap 42.2 or Tumbleweed or …?

32 or 64bit?

Fraser_Bell · January 25, 2017, 1:29am

Apparently, Tumbleweed, according to the thread title:

Post a reply to the thread: TUMBLEWEED boot not possible after upgrade fom Kernel 4.9.0 to Kernel 4.9.3
lol!

OrsoBruno · January 25, 2017, 10:30am

Hi, there are a couple of issues concerning booting with 4.9.x kernels whose fixes are in the pipeline and should land possibly in 4.9.6.
See these bug reports for details; https://bugzilla.kernel.org/show_bug.cgi?id=191121 https://bugzilla.suse.com/show_bug.cgi?id=1017783
Feel free to file a new bug report if you think your problem is different.
Or stick with 4.9.0 for the time being and wait for the fixes…

keellambert · January 25, 2017, 1:01pm

hi,

fwiw

updated to kernel 4.9.4 this morning on Tumbleweed 32bit os

needed to do a cold boot then all found to be ok

cheers

AxJHerVQ · January 26, 2017, 6:29pm

So I am running Tumbleweed on a 64 bit system:
(by hxtools sysinfo) [willnixWlan] openSUSE Tumbleweed 20170123 | Linux 4.9.0-2-default x86_64 | 4-thr Intel(R) Core™ i5-4460 CPU 3400MHz | Load: 0.26 Tasks: 641 | Mem: 1608/3896MB | Disk: 63/3794GB | Gfx: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] @ 1280x1024

Yesterday I tried to run the system with Kernel 4.9.3 after a cold boot, but no success

AxJHerVQ · January 30, 2017, 9:25pm

Today Kernel Version 4.9.6-1 was available, so I gave it a try. Unfortunately without success.

Jan 30 20:45:13 willnixWlan [RPM][25066]: install kernel-default-4.9.6-1.1.x86_64: success
Jan 30 20:45:13 willnixWlan [RPM][25066]: Transaction ID 588f97ba finished: 0
Jan 30 20:45:13 willnixWlan [RPM][10962]: Transaction ID 588f97c9 started
Jan 30 20:45:15 willnixWlan [RPM][10962]: install kernel-devel-4.9.6-1.1.noarch: success
Jan 30 20:45:15 willnixWlan [RPM][10962]: Transaction ID 588f97c9 finished: 0
Jan 30 20:45:15 willnixWlan [RPM][10970]: Transaction ID 588f97cb started
Jan 30 20:45:15 willnixWlan [RPM][10970]: install kernel-default-devel-4.9.6-1.1.x86_64: success
Jan 30 20:45:15 willnixWlan [RPM][10970]: Transaction ID 588f97cb finished: 0
Jan 30 20:45:15 willnixWlan [RPM][10976]: Transaction ID 588f97cb started
Jan 30 20:45:16 willnixWlan [RPM][10976]: install kernel-debug-devel-4.9.6-1.1.x86_64: success
Jan 30 20:45:16 willnixWlan [RPM][10976]: Transaction ID 588f97cb finished: 0
Jan 30 20:45:46 willnixWlan su[6387]: pam_unix(su:session): session closed for user root
Jan 30 20:45:49 willnixWlan org.kde.kwalletd5[2479]: slotServiceOwnerChanged  ":1.66" ,  ":1.66" ,  ""
Jan 30 20:45:58 willnixWlan polkitd[1085]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.35, object path /org/kde/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8)
Jan 30 20:45:58 willnixWlan org.kde.kwalletd5[2479]: slotServiceOwnerChanged  ":1.55" ,  ":1.55" ,  ""
Jan 30 20:45:58 willnixWlan dbus-daemon[2479]: Activating service name='org.kde.kdeconnect'
Jan 30 20:45:58 willnixWlan org.kde.kwalletd5[2479]: slotServiceOwnerChanged  ":1.61" ,  ":1.61" ,  ""
Jan 30 20:45:58 willnixWlan org.kde.kdeconnect[2479]: kdeconnect.core: KdeConnect daemon starting
Jan 30 20:45:59 willnixWlan org.kde.kdeconnect[2479]: kdeconnect.core: onStart
Jan 30 20:45:59 willnixWlan dbus-daemon[2479]: Successfully activated service 'org.kde.kdeconnect'
Jan 30 20:45:59 willnixWlan org.kde.kdeconnect[2479]: kdeconnect.core: KdeConnect daemon started
Jan 30 20:45:59 willnixWlan org.kde.kdeconnect[2479]: kdeconnect.core: Broadcasting identity packet
Jan 30 20:46:01 willnixWlan systemd-logind[1097]: System is powering down.

After that I rebooted the system:

-- Reboot --
Jan 30 20:46:43 willnixWlan kernel: microcode: microcode updated early to revision 0x20, date = 2016-03-16
Jan 30 20:46:43 willnixWlan kernel: Linux version 4.9.6-1-default (geeko@buildhost) (gcc version 6.2.1 20161209 [gcc-6-branch revision 243481] (SUSE Linux) ) #1 SMP PREEMPT Thu Jan 26 09:09:16 UTC 2017 (d1207ac)
Jan 30 20:46:43 willnixWlan kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.6-1-default root=UUID=71d36153-187f-4df6-8391-c123cc4112d8 resume=/dev/disk/by-uuid/f0087c95-02f8-4e28-8952-56b8de9055a7 splash=silent quiet showopts

The symptoms are the same, I recognize this pattern

Jan 30 20:46:49 willnixWlan root[1797]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Jan 30 20:46:49 willnixWlan root[1797]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Jan 30 20:46:49 willnixWlan sddm[1833]: Initializing...
Jan 30 20:46:49 willnixWlan sddm[1833]: Starting...
Jan 30 20:46:49 willnixWlan sddm[1833]: Adding new display on vt 7 ...
Jan 30 20:46:49 willnixWlan sddm[1833]: Display server starting...
Jan 30 20:46:49 willnixWlan sddm[1833]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{7b60acf8-00a1-43be-aa41-9a12e67efce1} -background none -noreset -displayfd 18 vt7
Jan 30 20:46:49 willnixWlan kernel: SFW2-INext-DROP-DEFLT IN=wlp4s1 OUT= MAC= SRC=fe80:0000:0000:0000:b248:7aff:febf:7199 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=301 TC=0 HOPLIMIT=255 FLOWLBL=664274 PROTO=UDP SPT=5353 DPT=5353 LEN=261 
Jan 30 20:46:50 willnixWlan sddm[1833]: Running display setup script  "/etc/X11/xdm/Xsetup"
Jan 30 20:46:50 willnixWlan sddm[1833]: Display server started.
Jan 30 20:46:50 willnixWlan sddm[1833]: Socket server starting...
Jan 30 20:46:50 willnixWlan sddm[1833]: Socket server started.
Jan 30 20:46:50 willnixWlan sddm[1833]: Greeter starting...
Jan 30 20:46:50 willnixWlan sddm[1833]: Adding cookie to "/run/sddm/{7b60acf8-00a1-43be-aa41-9a12e67efce1}"
Jan 30 20:46:50 willnixWlan display-manager[1733]: Starting service sddm/usr/bin/xauth: (stdin):1:  bad "remove" command line
Jan 30 20:46:50 willnixWlan display-manager[1733]: /usr/bin/xauth: (stdin):2:  bad "add" command line
Jan 30 20:46:50 willnixWlan sddm[1833]: Display server stopped.
Jan 30 20:46:50 willnixWlan sddm[1833]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Jan 30 20:46:50 willnixWlan sddm[1833]: Socket server stopping...
Jan 30 20:46:50 willnixWlan sddm[1833]: Socket server stopped.
Jan 30 20:46:50 willnixWlan sddm[1833]: Removing display "" ...
Jan 30 20:46:50 willnixWlan sddm[1833]: Adding new display on vt 7 ...
Jan 30 20:46:50 willnixWlan sddm[1833]: Display server starting...
Jan 30 20:46:50 willnixWlan sddm[1833]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{b6b08524-727f-41cc-ad6e-6b385f8a293c} -background none -noreset -displayfd 20 vt7
Jan 30 20:46:50 willnixWlan sddm-helper[1844]: [PAM] Starting...
Jan 30 20:46:50 willnixWlan sddm-helper[1844]: [PAM] Authenticating...
Jan 30 20:46:50 willnixWlan sddm-helper[1844]: [PAM] returning.
Jan 30 20:46:50 willnixWlan display-manager[1733]: ..done
Jan 30 20:46:50 willnixWlan systemd[1]: Started X Display Manager.
Jan 30 20:46:50 willnixWlan kernel: SFW2-INext-DROP-DEFLT IN=wlp4s1 OUT= MAC= SRC=fe80:0000:0000:0000:b248:7aff:febf:7199 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=188 TC=0 HOPLIMIT=255 FLOWLBL=664274 PROTO=UDP SPT=5353 DPT=5353 LEN=148 
Jan 30 20:46:50 willnixWlan sddm[1833]: Running display setup script  "/etc/X11/xdm/Xsetup"
Jan 30 20:46:50 willnixWlan sddm[1833]: Display server started.
Jan 30 20:46:50 willnixWlan sddm[1833]: Socket server starting...
Jan 30 20:46:50 willnixWlan sddm[1833]: Socket server started.
Jan 30 20:46:50 willnixWlan sddm[1833]: Greeter starting...
Jan 30 20:46:50 willnixWlan sddm[1833]: Adding cookie to "/run/sddm/{b6b08524-727f-41cc-ad6e-6b385f8a293c}"
Jan 30 20:46:50 willnixWlan display-manager[1733]: /usr/bin/xauth: (stdin):1:  bad "remove" command line
Jan 30 20:46:50 willnixWlan display-manager[1733]: /usr/bin/xauth: (stdin):2:  bad "add" command line
Jan 30 20:46:50 willnixWlan sddm[1833]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Jan 30 20:46:50 willnixWlan sddm[1833]: Display server stopped.
Jan 30 20:46:50 willnixWlan sddm[1833]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Jan 30 20:46:50 willnixWlan sddm[1833]: Socket server stopping...
Jan 30 20:46:50 willnixWlan sddm[1833]: Socket server stopped.
Jan 30 20:46:50 willnixWlan sddm[1833]: Removing display "" ...
Jan 30 20:46:50 willnixWlan sddm[1833]: Adding new display on vt 7 ...

OrsoBruno · January 31, 2017, 10:42am

Radeon graphics? If so, have a look at this https://forums.opensuse.org/showthread.php/522644-Will-not-boot-in-Kernel-4-9-5-1-ACPI-Error-flashing-screen-unresponsive?p=2810517#post2810517

zenarcher · January 31, 2017, 11:45am

Kernel 4.9.6-1 did finally fix the never ending reboot at GRUB issue I was having with the 4.9 kernel and my Toshiba laptop computer.

boenis · February 3, 2017, 8:40pm

Oh. I have the same problem:


Feb 03 09:31:08 stephan sddm[1783]: Adding new display on vt 7 ...
Feb 03 09:31:08 stephan sddm[1783]: Display server starting...
Feb 03 09:31:08 stephan sddm[1783]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{605b76f7-e75d-4c78-a776-c745790a1ab0} -backgrou
Feb 03 09:31:08 stephan systemd-coredump[1922]: Process 1916 (X) of user 0 dumped core.
Feb 03 09:31:08 stephan sddm-helper[1928]: [PAM] Starting...
Feb 03 09:31:08 stephan sddm-helper[1928]: [PAM] Authenticating...
Feb 03 09:31:08 stephan sddm-helper[1928]: [PAM] returning.
Feb 03 09:31:08 stephan systemd[1]: Started Process Core Dump (PID 1933/UID 0).
Feb 03 09:31:08 stephan sddm[1783]: Running display setup script  "/etc/X11/xdm/Xsetup"
Feb 03 09:31:08 stephan sddm[1783]: Display server started.
Feb 03 09:31:08 stephan sddm[1783]: Socket server starting...
Feb 03 09:31:08 stephan sddm[1783]: Socket server started.
Feb 03 09:31:08 stephan sddm[1783]: Greeter starting...
Feb 03 09:31:08 stephan sddm[1783]: Adding cookie to "/run/sddm/{605b76f7-e75d-4c78-a776-c745790a1ab0}"
Feb 03 09:31:08 stephan display-manager[1665]: /usr/bin/xauth: (stdin):1:  bad "remove" command line
Feb 03 09:31:08 stephan display-manager[1665]: /usr/bin/xauth: (stdin):2:  bad "add" command line
Feb 03 09:31:08 stephan sddm[1783]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Feb 03 09:31:08 stephan sddm[1783]: Display server stopped.
Feb 03 09:31:08 stephan sddm[1783]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Feb 03 09:31:08 stephan sddm[1783]: Socket server stopping...
Feb 03 09:31:08 stephan sddm[1783]: Socket server stopped.
Feb 03 09:31:08 stephan sddm[1783]: Removing display "" ...

My current workaround:

boot in init level 3
login as root
xinit
su - myusername
export DISPLAY=:0
startkde

AxJHerVQ · February 5, 2017, 1:23pm

No Radeon graphics, see komment #6

2fry · February 5, 2017, 7:33pm

I am having a similar problem. I just upgraded from SUSE 13.2 to Tumbleweed and it boots to the command line as follows:

   4.00281] sp5100_tco: I/O address 0x0cd6 already in use

Welcome to openSUSE Tumbleweed 20170203 - kernel 4.9.6-1-default (tty1).
linux-0dka login: _

Is this a graphics card problem?

gogalthorp · February 5, 2017, 8:37pm

AMD driver? Probably what driver where you using? The fglrx it should be removed the AMD drivers have changed and now are AMDGPU and proprietary AMDGPU-PRO the old fglrx driver is dead and won’t work in newer kernels

icearchery · February 6, 2017, 2:29am

Hi, I’m a newbie, but I think I had a similar problem, albeit, with a different graphics card.

You mention you are using Nvidia Geforce, are you using the nouveau driver or the nvidia one? Perhaps the problem lies there.

Jan 30 20:46:50 willnixWlan display-manager[1733]: /usr/bin/xauth: (stdin):1:  bad "remove" command line
Jan 30 20:46:50 willnixWlan display-manager[1733]: /usr/bin/xauth: (stdin):2:  bad "add" command line
Jan 30 20:46:50 willnixWlan sddm[1833]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Jan 30 20:46:50 willnixWlan sddm[1833]: Display server stopped.
Jan 30 20:46:50 willnixWlan sddm[1833]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Jan 30 20:46:50 willnixWlan sddm[1833]: Socket server stopping...
Jan 30 20:46:50 willnixWlan sddm[1833]: Socket server stopped.
Jan 30 20:46:50 willnixWlan sddm[1833]: Removing display "" ...
Jan 30 20:46:50 willnixWlan sddm[1833]: Adding new display on vt 7 ...

sddm seems to be acting up? Could it be so?

OrsoBruno · February 6, 2017, 10:26am

@Icearchery
@2fry

Please Gentlemen, the OP describes an Intel+Nvidia laptop, possibly an Optimus one in this thread: don’t mess up this thread with different issues and open your own thread describing your configuration in detail.
Thanks.

To the OP:
Can you boot to console (press “E” at the GRUB menu screen, look for a line beginning with “linuxefi” and append “3” without quotes, then press F10 to boot)?
If so, can you look at /var/log/Xorg.0.log for clues about what went wrong?
Is the Nvidia driver built and installed?
If not so, can you remove the nouveau driver from the blacklist and boot with that?
Does the workaround suggested in post #10 work?

boenis · February 6, 2017, 3:01pm

Problem solved:

Xorg-Repository added: http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_Tumbleweed
zypper dup

All works fine.

OrsoBruno · February 6, 2017, 3:19pm

Congratulations, an X server problem then? What packages were actually upgraded during this last zypper dup?

boenis · February 6, 2017, 3:36pm

Yes, quite an X server problem.

In the end, I’ve reinstalled the entire system based on the current Tumbleweed Network Install CD. The same problem. But now without working workaround.
So I’ve tryed the xorg repository.

These are the installed packages (according zypp history file):


Mesa-libglapi0
libICE6
libX11-data
libXau6
libXdmcp6
libdrm2
libepoxy0
libevdev2
libfontenc1
libmtdev1
libpciaccess0
libpixman-1-0
libva1
libwayland-egl1
libxshmfence1
luit
rgb
s2tc-32bit
sessreg
vaapi-dummy-driver
xbitmaps
xkeyboard-config
xorg-x11-fonts-core
xorg-x11-libX11-ccache
Mesa-libGLESv2-2
libSM6
iceauth
libX11-xcb1
libxcb1
libva-drm1
libkms1
libgbm1
libdrm_radeon1
libdrm_nouveau2
libdrm_amdgpu1
mkfontscale
libXfont2-2
libdrm_intel1
libva-egl1
xorg-x11-fonts
libxcb-xkb1
libxcb-xinerama0
libxcb-xfixes0
libxcb-util1
libxcb-sync1
libxcb-shm0
libxcb-shape0
libxcb-render0
libxcb-record0
libxcb-randr0
libxcb-present0
libxcb-keysyms1
libxcb-icccm4
libxcb-glx0
libxcb-dri3-0
libxcb-dri2-0
libxcb-dpms0
libxcb-damage0
libxcb-composite0
libX11-6
mkfontdir
Mesa
libxcb-image0
libxcb-render-util0
libvulkan_radeon
libvdpau_radeonsi
libvdpau_r600
libvdpau_r300
Mesa-libva
Mesa-libEGL1
xprop
xmodmap
libxkbfile1
libXt6
libXrender1
libXpm4
libXmuu1
libXfixes3
libXext6
libXdamage1
libXcomposite1
libxcb-cursor0
xkbcomp
setxkbmap
libXft2
xrdb
xhost
libXcursor1
xauth
tigervnc
libvdpau1
libva-x11-1
libXxf86vm1
libXxf86misc1
libXv1
libXtst6
libXss1
libXrandr2
libXmu6
libXinerama1
libXi6
libXfontcache1
libXRes1
xsetroot
Mesa-libGL1
xrandr
libXaw7
xset
xinit
xorg-x11-server
libva-glx1
libGLU1
xmessage
xconsole
xf86-video-vesa
xf86-video-r128
xf86-video-mach64
xf86-video-fbdev
xf86-video-ati
xf86-video-amdgpu
xf86-input-wacom
xf86-input-void
xf86-input-vmmouse
xf86-input-synaptics
xf86-input-mouse
xf86-input-libinput
xf86-input-keyboard
xf86-input-joystick
xf86-input-evdev
xdm
xorg-x11-driver-video
xorg-x11-driver-input
xorg-x11-essentials

OrsoBruno · February 6, 2017, 6:47pm

Maybe the newest sddm in the last few snapshots needs the newer xdm or xorg-x11-server that are available in the X11:/XOrg repo?
From your post #10 it seems related…

Feb 03 09:31:08 stephan sddm[1783]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{605b76f7-e75d-4c78-a776-c745790a1ab0} -backgrou
Feb 03 09:31:08 stephan systemd-coredump[1922]: Process 1916 (X) of user 0 dumped core.
Feb 03 09:31:08 stephan sddm-helper[1928]: [PAM] Starting…
Feb 03 09:31:08 stephan sddm-helper[1928]: [PAM] Authenticating…
Feb 03 09:31:08 stephan sddm-helper[1928]: [PAM] returning.
Feb 03 09:31:08 stephan systemd[1]: Started Process Core Dump (PID 1933/UID 0).
Feb 03 09:31:08 stephan sddm[1783]: Running display setup script “/etc/X11/xdm/Xsetup”

As a comparison, I’m running two Leap 42.2 Gnome instances (gdm, NOT sddm as display manager) here without problems, with the following packages:
#1 “default” repos


kernel-default         | package | 4.9.5-2.1.g9bb1a8a
xdm                    | package | 1.1.11-13.1
xorg-x11-server        | package | 7.6_1.18.3-7.1

#2 X11:/XOrg repo enabled


kernel-default         | package | 4.9.8-1.1.gaf90696
xdm                    | package | 1.1.11-201.1
xorg-x11-server        | package | 1.19.1-479.2

Both had problems booting with the 4.9.0 kernel but have been OK as soon as bpetkov published the patch that eventually landed in 4.9.4.
So maybe what we are dealing in this thread might NOT be related to the kernel and might be a display manager / Xserver issue…

AxJHerVQ · February 11, 2017, 4:49pm

Problem is now solved.
I installed the kernel-default-4.9.8-1.1.x86_64 and the NVIDIA Driver NVIDIA-Linux-x86_64-378.09
With this combination everything works fine again.