Comment # 3 on bug 1087525 from Takashi Iwai

Can be a problem of graphics driver.  What "worked" in the past lp150.5.x
package was a side-effect of the wrong kconfig, thus the amdgpu graphics driver
was gone from kernel-default.

Try to boot with "nomodeset" boot option.  This will suppress the amdgpu KMS
driver, so it'll remain in the VESA or EFI framebuffer.
Also, try to remove "quiet" boot option, too.

If the nomodeset boot option doesn't help, forget the test below.  It's
something else, and we need different analysis.

Or, if nomodeset worked, keep booting with nomodeset option, then after boot
up, go to Linux console (ctrl-alt-F1), and re-load amdgpu driver like
  modprobe -r amdgpu
  modprobe amdgpu modeset=1

This might or might not crash.  If it crashes, try alt-sysrq-S and alt-sysrq-B
to make system sync and rebooting by itself (with luck).  Then check the
previous kernel log via "journalctl -k -b-1" as root.  We might see some
messages.

If you have another machine on the network, you may set up netconsole to catch
the kernel messages remotely.  It may work better than the above.

And, if it's a crash (or kernel panic), at best, try to get the kernel messages
via kdump.

The next step would be to do the same like the above, reload of amdgpu, but one
more step in-between:
  modprobe -r amdgpu
  modprobe drm debug=0x0e
  modprobe amdgpu modeset=1

This will give more verbose information about graphics in the kernel messages.

Once when you get the kernel message showing some crash, please upload it to
Bugzilla.
And, also give the output of hwinfo, too.