Bug 1077883 - Unable to boot after upgrading from openSUSE Tumbleweed 20171220-0 -> 20180126-0
Unable to boot after upgrading from openSUSE Tumbleweed 20171220-0 -> 201801...
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Upgrade Problems
x86-64 SUSE Other
: P5 - None : Critical (vote)
: ---
Assigned To: E-mail List
Jiri Srain
Depends on:
  Show dependency treegraph
Reported: 2018-01-28 19:34 UTC by Dennis Irrgang
Modified: 2019-11-29 14:56 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

lshw output (49.07 KB, text/plain)
2018-01-28 19:36 UTC, Dennis Irrgang
Zypper output (94.10 KB, text/plain)
2018-01-28 19:37 UTC, Dennis Irrgang

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Irrgang 2018-01-28 19:34:53 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Build Identifier: 

After trying to upgrade my system after not having used it for a while I get stuck at grub2 during the "loading initial ramdisk" phase.

Booting in secure mode doesn't help either.

My system contains an Nvidia 1070 which has caused issues in the past.

I'm using the official Nvidia tumbleweed repo introduced here:

Reproducible: Always

Steps to Reproduce:
1. sudo zypper dup
2. Reboot
Actual Results:  
Freezes at "loading initial ramdisk".
Does not react to any input, HW reset button does not work and I need to hold the power button for the PC to shut down.

Expected Results:  
Comment 1 Dennis Irrgang 2018-01-28 19:36:42 UTC
Created attachment 757823 [details]
lshw output
Comment 2 Dennis Irrgang 2018-01-28 19:37:29 UTC
Created attachment 757824 [details]
Zypper output

Configured repositories, priorities and zypper dup output
Comment 3 Chenzi Cao 2018-01-30 09:55:04 UTC
Hi Kernel maintainers, I'm not sure whether it is right to assign it to you, please feel free to reassign whenever necessary, thank you!
Comment 4 Dennis Irrgang 2018-01-30 10:46:21 UTC
One more thing I tried:
I added kernel* to the locked packages in zypper and did a dup then - exact same behaviour. Next thing I wanted to do was upgrade the nvidia drivers seperately, but I didn't get around to it yet.
Comment 5 Borislav Petkov 2019-11-29 14:56:11 UTC
Looks forgotten. Feel free to reopen if still of interest.