I ran an upgrade from 42.2 to 42.3 using the full ISO put onto a USB stick, done on an ASUS X550C laptop with Intel I7 cpu and Intel graphics which ran KDE/Plasma. This laptop worked perfectly on 42.2 and would resume from hibernate without fail. The upgrade went without error and the laptop boot perfectly and it appears to hibernate without issue however when I attempt to resume it appears to load the image from the swap file (which is 10GB on an 8GB laptop) but when the unlock screen appears it is completely garbled although typing the password works and the screen unlocks the resultant KDE/Plasma screen is also garbled by which I mean parts of the screen show but in the wrong place and the panel which should at the bottom of the screen flashes. Eventually I have been able to get the logout option by CTRL/Alt/Del to allow logging out and back in again without a reboot and the desktop comes up fine. It would seem that there is an issue somewhere but not sure what.
Well as this laptop is not critical I decided to wipe root and do a fresh install keeping /home. Having just completed that and having done nothing more than boot the laptop successfully I did a hibernate which seemed to work fine but on resume I got the normal messages about loading the image and the a black screen with a mouse pointer on it but nothing would work not even the mouse, had to power off and reboot.
Seems like resume from hibernate is kaputt in 42.3 at least on my Intel laptop.
Jul 31 10:22:54 ASUSLEAP423 kernel: [drm] GPU HANG: ecode 7:0:0x85ffbffa, in plasmashell [1461], reason: Hang on render ring, action: reset
Jul 31 10:22:54 ASUSLEAP423 kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jul 31 10:22:54 ASUSLEAP423 kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jul 31 10:22:54 ASUSLEAP423 kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jul 31 10:22:54 ASUSLEAP423 kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jul 31 10:22:54 ASUSLEAP423 kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Jul 31 10:22:54 ASUSLEAP423 kernel: drm/i915: Resetting chip after gpu hang
Jul 31 10:23:05 ASUSLEAP423 kernel: drm/i915: Resetting chip after gpu hang
Jul 31 10:23:17 ASUSLEAP423 kernel: drm/i915: Resetting chip after gpu hang
Jul 31 10:23:28 ASUSLEAP423 kernel: drm/i915: Resetting chip after gpu hang
one problem is that the referred to crash dump has a length of 0.
Are you trying to find dump after reboot? /sys is virtual directory, its content is lost after reboot, so you need to copy it immediately after it is generated.
how cen I get that added to Leap 42.3 to see if it fixes the issue?
The issue with the dump is that I am unable to get into the laptop when reuming, the only way which works sometimes is ctrl-alt-del and hope it logs me off and on, but will that wipe the dump as well?
)